unable to load package
I have created an SSISpackage 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 dualxeon 2gb ramwith win 2k sp4 and sql 2005 sp1.
Microsoft (R) SQL Server Execute Package UtilityVersion 9.00.1399.06 for 32-bitCopyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 12:29:19Error: 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 have a valid XML format. A specific XML parser error will be posted.End ErrorError: 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 correctlyinto 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 ErrorCould 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" dueto 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 andhas an incorrect format.Source: {B06EB426-BBE8-4E09-87FC-32ED753A142F}Started: 12:29:19Finished: 12:29:20Elapsed: 1.719 seconds
July 6th, 2006 2:56pm
We are having the same problem:
Myteam is usingSqlServer 2005 SSIS to develop package for Consolidated Views. This works fine on my machine in Visual Studio whenthey run it as a script from command prompt from their desktop. However,when they move this package toETL box, the package runs fine Visual Studio environment but fails when run from the script with the errors:
Started: 12:57:45 PMError: 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\Integrated 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 canbe 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\Integrated Views\Integrated Views\CV_Product.dtsx" due to error 0x800C0006 "The systemcannot 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 bethe 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 PMFinished: 12:57:45 PMElapsed: 0.016 seconds
C:\SM_BI_EXTRACTS_SHARED\Shared>rem "C:\Program Files\Microsoft SQL Server\90\DTS\Binn\dtexec" /f "C:\SM_BI_EXTRACTS_SHARED\Shared\SSIS\IntegratedViews\IntegratedViews\CV_Sales_Rep.dtsx"
C:\SM_BI_EXTRACTS_SHARED\Shared>rem "C:\Program Files\Microsoft SQL Server\90\DTS\Binn\dtexec" /f "C:\SM_BI_EXTRACTS_SHARED\Shared\SSIS\IntegratedViews\IntegratedViews\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
Free Windows Admin Tool Kit Click here and download it now
August 4th, 2006 10:03pm
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.
August 8th, 2006 12:43pm
Thanks for the solution it was a path error for me too
Free Windows Admin Tool Kit Click here and download it now
October 4th, 2007 5:44pm
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,
May 4th, 2010 12:03am
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
Free Windows Admin Tool Kit Click here and download it now
November 2nd, 2010 7:14am
Clement,
I am having the same issue, what is the / path you solved, can you help me out with this ?
Thanks,
Surya
June 16th, 2011 11:05am