共用方式為

Could not load package because of error 0xC0011002. Failed to open package file due to error 0x80070005 "Access is denied."

  • 發行項

Came across this error while executing a SSIS package through a SQL Agent Job on a SQL Server 2008 server.The job is running under a windows security account and the SSIS package is stored on file system of the server.

The exact error message received was as shown below.

Executed as user: Domain\User. Microsoft (R) SQL Server Execute Package Utility  Version 10.50.1600.1 for 64-bit  Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started:  11:11:37 PM  Error: 2011-01-03 23:11:37.14     Code: 0xC0011007     Source: {1BDBB290-5831-476E-97F5-78DA45F876F4}      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-01-03 23:11:37.14     Code: 0xC0011002     Source: {1BDBB290-5831-476E-97F5-78DA45F876F4}      Description: Failed to open package file "C:\SSIS\MyPackage.dtsx" due to error 0x80070005 "Access is denied.".  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 "D:\SSIS\MyPackage.dtsx" because of error 0xC0011002. Description: Failed to open package file "D:\SSIS\MyPackage.dtsx" due to error 0x80070005 "Access is denied." .  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: {1BDBB290-5831-476E-97F5-78DA45F876F4}  Started:  11:11:37 PM  Finished: 11:11:37 PM  Elapsed:  0.031 seconds.  Process Exit Code 4.  .  NOTE: The step was retried the requested number of times (5) without succeeding.  The step failed.

 

Since the error message is talking about access, verified whether the security account with which SQL Agent Service is running has access to the server folder in which SSIS package is stored. Noticed that the security account doesn't have the access and the job started working after giving the read & write permission on the folder.

Let me know if this has helped you.

Comments

  • Anonymous
    February 28, 2012
    Hi Ramoji, I have the same error... gave full Control access to the network login that Integration Services service uses. Still, I'm getting the same error... I feel that this is probably something silly that I'm missing... what else can it be? Please let me know Thanks

  • Anonymous
    October 26, 2015
    I found it is necessary to go Services on the machine hosting SQL Server.  Go to both the SQL Server and SQL Server Agent services.  Right click and properties.  There will be a tab called "Log On".  On this tab, select "this account".  The best practice is to select a previously created service account.  This account should have permissions to run both of these services and should have folder permissions in the folder where the SSIS package is stored, if it is stored on the file system.  Be sure to stop and start the services so that the changes to the Log On account take affect.  When the SSIS package is called, it will have all the permissions need to run.