Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSMS Job\SSIS due to error 0x80070003 "The system cannot find the path specified." Expand / Collapse
Author
Message
Posted Wednesday, October 26, 2011 8:51 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Today @ 12:24 AM
Points: 74, Visits: 301
Hi All,

I am logging on to a production M$ 2003 server using a domain administrator account xxxx\administrator. Then starting BIDS and have created a .dtsx package. The package uses a lookup to compare hearings in different Database tables and exports the differences. It runs fine in BIDS.

I then log into SSMS 08 with the same domain account and setup the following;

Security
--------
LOGIN: xxxx\administrator, SERVER ROLES:public, sysadmin, MAPPED: the 2 db's and MSDB sqlAgentoperator, sqlagentuser, slqagentreader

Credential
----------
Admin: Identity, xxxx\administrator with correct password

Proxy
----------
myproxy: Admin with subsystem SSIS packages selected

Jobs
-----------
Hearing job: Owner:xxxx\administrator, only 1 step 'check hearing type',
Edit step: name ' check hearing type', type SQL SISS Package, Run As 'myproxy'
Package Source: File System
Pacakge: C:\Documents and Settings\administrator.xxxxx\My Documents\Visual Studio 2008\Projects\Integration Services Project1\Integration Services Project1\Package2.dtsx



So I have logged in, created and running the package with the same domain administrator account, given it the SQL permissions. Created a credential for a proxy and told the package to use the proxy account to run as. But the package still doesn't run.

Full Error Message:

Executed as user: xxxxx\Administrator. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 1:23:01 PM Error: 2011-10-27 13:23:01.26 Code: 0xC0011007 Source: {883AAF08-4C73-4B47-900B-6B0A3E89C348} Description: Unable to load the package as XML because of package does not have a valid XML format. A specific XML parser error will be posted. End Error Error: 2011-10-27 13:23:01.26 Code: 0xC0011002 Source: {883AAF08-4C73-4B47-900B-6B0A3E89C348} Description: Failed to open package file "C:\Documents and Settings\administrator.SERVER1\My Documents\Visual Studio 2008\Projects\Integration Services Project1\Integration Services Project1\Package2.dtsx" due to error 0x80070003 "The system cannot find the path specified.". This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format. End Error Could not load package "C:\Documents and Settings\administrator.SERVER1\My Documents\Visual Studio 2008\Projects\Integration Services Project1\Integration Services Project1\Package2.dtsx" because of error 0xC0011002. Description: Failed to open package file "C:\Documents and Settings\administrator.SERVER1\My Documents\Visual Studio 2008\Projects\Integration Services Project1\Integration Services Project1\Package2.dtsx" due to error 0x80070003 "The system cannot find the path specified.". This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format. Source: {883AAF08-4C73-4B47-900B-6B0A3E89C348} Started: 1:23:01 PM Finished: 1:23:01 PM Elapsed: 0.031 seconds. The package could not be found. The step failed.

Any help would be very much appreciated

I have been browsing the net all day and haven't found anything I have missed, but there must be something.
Post #1196718
Posted Thursday, October 27, 2011 6:00 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Today @ 12:24 AM
Points: 74, Visits: 301
Problem is solved :) if anyone is intrested....

I found that I had to enable deployment from the package properties and build. Then use the deployment tool to deploy the packages to the SQL server MSDB or file system. Then I can use the SQL server agent for most of the jobs and they run fine. There is only one job thats uses a flat file on the server so i have to use a local admin account for that job.
Post #1197273
Posted Tuesday, December 25, 2012 9:32 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, May 8, 2014 2:40 AM
Points: 52, Visits: 136
Hi I need one help from u, I am also gettign error while executing package from cmd. Could you please help?
I am getting below two error

1.Unable to load the package as XML because of package doesnt have valid xml format.
2.Failed to open package file due to 0x80070003 error.
Post #1400135
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse