none
unable to load package

    Question

  • I have created an SSIS package in BI dev studio which i can debug and run fine. I have saved the dtsx file to a production server which calls it using dtexec as part of a batch script (we are migrating from foxpro). I am getting the following error that i dont understand.

    I dont know if this is relevant but i cant execute packages by double clicking them as DTexecui is not installed (not sure why as i have installed the client tools and integration server). Hardware is Dell poweredge 2850 dual xeon 2gb ram with win 2k sp4 and sql 2005 sp1.

    Microsoft (R) SQL Server Execute Package Utility
    Version 9.00.1399.06 for 32-bit
    Copyright (C) Microsoft Corp 1984-2005. All rights reserved.

    Started:  12:29:19
    Error: 2006-07-06 12:29:20.75
       Code: 0xC0011007
       Source: {B06EB426-BBE8-4E09-87FC-32ED753A142F}
       Description: Unable to load the package as XML because of package does not ha
    ve a valid XML format. A specific XML parser error will be posted.
    End Error
    Error: 2006-07-06 12:29:20.79
       Code: 0xC0011002
       Source: {B06EB426-BBE8-4E09-87FC-32ED753A142F}
       Description: Failed to open package file "\\SERVER_A\Scripts\CLIENT\Package.dtsx" due to error 0x800C0006 "The system cannot locate the object 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 "\\\\SERVER_A\Scripts\CLIENT\Package.dtsx" because of error 0xC0011002.
    Description: Failed to open package file \\SERVER_A\Scripts\CLIENT\Package.dtsx" due to error 0x800C0006 "The system cannot locate the object specified.".  This hap
    pens when loading a package and the file cannot be opened or loaded correctly in
    to the XML document. This can be the result of either providing an incorrect fil
    e name was specified when calling LoadPackage or the XML file was specified and
    has an incorrect format.
    Source: {B06EB426-BBE8-4E09-87FC-32ED753A142F}
    Started:  12:29:19
    Finished: 12:29:20
    Elapsed:  1.719 seconds


     

     

    Thursday, July 06, 2006 11:56 AM

Answers

  • I think i solved this. For me, it was due to an issue with the path not being recognised correctly. I am using a batch file to call the ssis package and it only worked using a mapped drive instead of a fully qualified UNC path. It may be different for other people as i am using dos variables so have a fiddle.
    Tuesday, August 08, 2006 9:43 AM

All replies

  •  We are having the same problem:

     

    My team is using SqlServer 2005 SSIS to develop  package for Consolidated Views. This works fine on my machine in Visual Studio when they run it as a script from command prompt from their desktop. However, when they move this package to ETL box, the package runs fine Visual Studio environment but fails when run from the script with the errors: 

    Started:  12:57:45 PM
    Error: 2006-08-04 12:57:45.87
       Code: 0xC0011007
       Source: {519D338B-8874-40A8-A385-0D53E868A57C}

    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: 2006-08-04 12:57:45.87
       Code: 0xC0011002
       Source: {519D338B-8874-40A8-A385-0D53E868A57C}

    Description: Failed to open package file "C:\SM_BI_EXTRACTS_SHARED\Shared\Int
    egrated Views\Integrated Views\CV_Product.dtsx" due to error 0x800C0006 "The system cannot locate the object specified.".  This happens when loading a package a nd 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:\SM_BI_EXTRACTS_SHARED\Shared\Integrated Views\Integrated Views\CV_Product.dtsx" because of error 0xC0011002.

    Description: Failed to open package file "C:\SM_BI_EXTRACTS_SHARED\Shared\Integr
    ated Views\Integrated Views\CV_Product.dtsx" due to error 0x800C0006 "The system  cannot locate the object 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: {519D338B-8874-40A8-A385-0D53E868A57C}
    Started:  12:57:45 PM
    Finished: 12:57:45 PM
    Elapsed:  0.016 seconds

    C:\SM_BI_EXTRACTS_SHARED\Shared>rem "C:\Program Files\Microsoft SQL Server\90\DT
    S\Binn\dtexec" /f "C:\SM_BI_EXTRACTS_SHARED\Shared\SSIS\IntegratedViews\Integrat
    edViews\CV_Sales_Rep.dtsx"

    C:\SM_BI_EXTRACTS_SHARED\Shared>rem "C:\Program Files\Microsoft SQL Server\90\DT
    S\Binn\dtexec" /f "C:\SM_BI_EXTRACTS_SHARED\Shared\SSIS\IntegratedViews\Integrat
    edViews\CV_Sales.dtsx"

    Can someone help us understand the problem? We are new to SSIS. We also want to know exactly what needs to be on the Server that will be running our SSIS ETL programs (that is, what components of SSIS -- SQL Server 2K5 is already loaded).

    We are using SQL 2005 on Dell Servers running Win 2003, with the latest service packs. Microsoft SQL Server Integration Services Designer Version 9.00.2047.00

    Friday, August 04, 2006 7:03 PM
  • I think i solved this. For me, it was due to an issue with the path not being recognised correctly. I am using a batch file to call the ssis package and it only worked using a mapped drive instead of a fully qualified UNC path. It may be different for other people as i am using dos variables so have a fiddle.
    Tuesday, August 08, 2006 9:43 AM
  • Thanks for the solution it was a path error for me too

     

     

     

    Thursday, October 04, 2007 2:44 PM
  • Hi!

    I am having the same problem as you had. Can you please tell me what is mapped drive and qualified UNC path??  Because I have created the package and that package reference the file that is stored on share ( \\Uspgh-fhrsr-p5.alae.tageo.com\sms_test. ) So, to access those file in connection manger what path should I give??? can you please tell me difference between mapped drive and UNC path?

     

    THanks,

    Monday, May 03, 2010 9:03 PM
  • Hi,

    Thank you, I had the same issue and correcting the /FILE path solved it.

    I run a SSIS 2005 package now stored on the file system, using the SQL Server Agent of a SQL Server 2008 Database Engine instance and using the SQL Server 2005 Integration Services DTexec and forgot the .dtsx when passing from /SQL to /FILE mode.

    a+, =)
    -=Clement=-

    Configuration :
    Database Engine : SQL Server 2008 (v10.50.1734)
    SSIS Engine : SQL Server 2005
    SSIS 2005 packages stored on file system

    Tuesday, November 02, 2010 11:10 AM
  • Clement,

     

    I am having the same issue, what is the / path you solved, can you help me out with this ?

     

    Thanks,

    Surya

    • Proposed as answer by sampathkumar.A Thursday, September 15, 2011 11:03 AM
    • Unproposed as answer by sampathkumar.A Thursday, September 15, 2011 11:03 AM
    Thursday, June 16, 2011 3:02 PM
  • You should be an admin to run the command or use run as 'sa' option
    Thursday, September 15, 2011 11:08 AM
  • ufffffffffffffff...........it was really a path problem.......it works fine now...thanks a looooot
    Tuesday, May 08, 2012 10:58 AM
  • It can get a little more complicated when you run SSIS jobs as a proxy account. The credential the proxy runs under (which will be a Windows user) needs to have read and execute access to the file share/folder where the package is stored.

    Ken

    Thursday, April 11, 2013 8:37 PM
  • Fully qualify your file path!  This was the problem for me, too.  Do not give the mapped directory (X:\...), be sure to give the full directory (\\servername\folder\file). 

    Thank you for your post.

    • Proposed as answer by Bofed Wednesday, February 19, 2014 7:32 PM
    • Unproposed as answer by Bofed Wednesday, February 19, 2014 7:32 PM
    Wednesday, August 21, 2013 10:18 PM
  • Hi Guy's,

    I got an error when I setup Schedule SSIS Package,

    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-02-19 13:13:18.34     Code: 0xC0011002     Source: {A7553897-7A9A-4BE2-ACDC-310B7A935C64}      Description: Failed to open package file "C:\Users\Abe\Desktop\Dispatch20140117\bin\Package.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 "C:\Users\Abe\Desktop\Dispatch20140117\bin\Package.dtsx" because of error 0xC0011002.  Description: Failed to open package file "C:\Users\Abe\Desktop\Dispatch20140117\bin\Package.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: {A7553897-7A9A-4BE2-ACDC-310B7A935C64}  Started:  1:13:18 PM  Finished: 1:13:18 PM  Elapsed:  0.016 seconds.  The package could not be found.  The step failed.,00:00:00,0,0,,,,0

    Wednesday, February 19, 2014 7:34 PM