Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
atuljadhavnetafim
Starting Member
25 Posts |
 Posted - 2014-12-30 : 06:59:37
|
| Dear Expert, I am getting error while I schedule ssis package, but if I run it manually it is working file, but not work thru shedualplease helpMessageExecuted as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 4:28:32 PM Error: 2014-12-30 16:28:32.44 Code: 0xC0011007 Source: {6334C520-29E2-47D0-88C8-78188123294B} 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: 2014-12-30 16:28:32.44 Code: 0xC0011002 Source: {6334C520-29E2-47D0-88C8-78188123294B} Description: Failed to open package file "\\NINHL007\12 Dec-14\Collection_auto_Uploade.dtsx" due to error 0x80070005 "Access is denied.". This occurs when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of specifying an incorrect file name when calling LoadPackage or the specified XML file has an incorrect format. End Error Could not load package "\\NINHL007\12 Dec-14\Collection_auto_Uploade.dtsx" because of error 0xC0011002. Description: Failed to open package file "\\NINHL007\12 Dec-14\Collection_auto_Uploade.dtsx" due to error 0x80070005 "Access is denied.". This occurs when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of specifying an incorrect file name when calling LoadPackage or the specified XML file has an incorrect format. Source: {6334C520-29E2-47D0-88C8-78188123294B} Started: 4:28:32 PM Finished: 4:28:32 PM Elapsed: 0.078 seconds. The package could not be found. The step failed.Atul JadhavAtul Jadhav |
|
|
gbritton
Master Smack Fu Yak Hacker
2780 Posts |
Posted - 2014-12-30 : 09:46:47
|
| "Access is denied." is your problem. Be sure that the account running the job has access to the network share. Note that it is typical to define an proxy for SSIS Package Execution in SQL Server Agent and the proxy would use a domain account with appropriate access rights. |
 |
|
|
|
|
|
eror while execute SSIS package thru shedule