Execute Package in JOB gives error
Hi, I created and simple package of something like.. select * from table.. when i ran the package in BIDS, dtsx... the package runs fine. the file exist in the path. but job says file not found :( when i run the package thru job, i am getting error. "Execution of job 'FF test' failed. See the history log for details." Histroy Log Message Executed as user: DEDOM001\nshanmug. Microsoft (R) SQL Server Execute Package Utility Version 10.0.4000.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 5:21:12 PM Error: 2011-10-04 17:21:13.24 Code: 0xC0011007 Source: {925A5E5C-80FB-4B14-9FBC-2433D7905CBD} 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-04 17:21:13.24 Code: 0xC0011002 Source: {925A5E5C-80FB-4B14-9FBC-2433D7905CBD} Description: Failed to open package file "C:\Package1.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:\Package1.dtsx" because of error 0xC0011002. Description: Failed to open package file "C:\Package1.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: {925A5E5C-80FB-4B14-9FBC-2433D7905CBD} Started: 5:21:12 PM Finished: 5:21:13 PM Elapsed: 0.39 seconds. The package could not be found. The step failed. Kindly let me know how to debug this error and fix the issue.. i am facing this for the past 2 days.. :(ShanmugaRaj
October 4th, 2011 11:41am

Means you have one SSIS version in dev and another in prod. E.g. the package was developed in SSIS 2008 and attempted to run by SSIS 2005Arthur My Blog
Free Windows Admin Tool Kit Click here and download it now
October 4th, 2011 12:06pm

Nope.. both in the same SSIS version 2008ShanmugaRaj
October 4th, 2011 12:08pm

Then you have a permission or a path (access issue)Arthur My Blog
Free Windows Admin Tool Kit Click here and download it now
October 4th, 2011 12:14pm

you need to set permission on the package path to sql server agent account, or if you want to use any special account to run the package you need to create a proxy account.http://www.rad.pasfu.com
October 4th, 2011 9:05pm

I am able to access all the files in the path.. the access issue is not there... earlier it was working fine.. suddenly some thing happened and now i am not able to run any job. what will be the issue.. how to debug this ?ShanmugaRaj
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2011 1:23am

Maybe you have access but not the account of sql server agent or the proxy if you use one. Please check, if something has changed with that accounts. I recommend to use a proxy which has all needed permissions
October 5th, 2011 5:12am

I am completely agree with Christa, the issue is not related to YOUR account, this is related to SQL SERVER AGENT ACCOUNT. create a proxy account with YOUR account or any account who has appropriate privilege and run job under that account. this is a link about how to create proxy account to run sql server job for ssis: http://www.sqlservercentral.com/articles/Integration+Services+%28SSIS%29/69441/http://www.rad.pasfu.com
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2011 6:17am

Maybe you have access but not the account of sql server agent or the proxy if you use one. Please check, if something has changed with that accounts. I recommend to use a proxy which has all needed permissions
October 5th, 2011 11:58am

I am completely agree with Christa, the issue is not related to YOUR account, this is related to SQL SERVER AGENT ACCOUNT. create a proxy account with YOUR account or any account who has appropriate privilege and run job under that account. this is a link about how to create proxy account to run sql server job for ssis: http://www.sqlservercentral.com/articles/Integration+Services+%28SSIS%29/69441/http://www.rad.pasfu.com
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2011 1:03pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics