Deployment Issue....
Hi , i am getting the following error when deploying my package to production. I didnt get a correct explanation regarding my issue. Code to Execute: 'cmd.exe /c \\' + @server + '\ssis2008$\DTExec.exe ' --had to create a share because didn't like long names ie "program files" + ' /FILE "\\' + @server + '\ssis_greatice\jobfiles\SSIS_GREAT_ICE_Verify_Connections.dtsx" ' + ' /ConfigFile "\\' + @server + '\ssis_greatice\jobfiles\SSIS_GREAT_ICE_Verify_Connections_' + @environment + '.dtsConfig" ' Error Code: 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: 2:12:27 PM Error: 2012-01-20 14:12:27.11 Code: 0xC0011007 Source: {CEA3661D-B0E6-46DF-971E-CED3CAEDBF1B} 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: 2012-01-20 14:12:27.11 Code: 0xC0011004 Source: {CEA3661D-B0E6-46DF-971E-CED3CAEDBF1B} Description: Failed to load XML from package file "\\CRPPDBP02B\ssis_greatice\jobfiles\SSIS_GREAT_ICE_Dim_All_Users.dtsx" due to error 0xC00CE556 "Invalid at the top level of the document. Line 2927, Column 94". This happens when loading a package and the file cannot be opened or loaded correctly into an XML document. This can be the result of either providing an incorrect file name to the LoadPackage method or the XML file specified having an incorrect format. End Error Could not load package "\\CRPPDBP02B\ssis_greatice\jobfiles\SSIS_GREAT_ICE_Dim_All_Users.dtsx" because of error 0xC00CE556. Description: Failed to load XML from package file "\\CRPPDBP02B\ssis_greatice\jobfiles\SSIS_GREAT_ICE_Dim_All_Users.dtsx" due to error 0xC00CE556 "Invalid at the top level of the document. Line 2927, Column 94". This happens when loading a package and the file cannot be opened or loaded correctly into an XML document. This can be the result of either providing an incorrect file name to the LoadPackage method or the XML file specified having an incorrect format. Source: {CEA3661D-B0E6-46DF-971E-CED3CAEDBF1B} Started: 2:12:27 PM Finished: 2:12:27 PM Elapsed: 0.032 seconds Mark as answer if the post help you... Regards, Indraneel A
January 20th, 2012 10:28pm

You need to check if user running SSIS package has access to file: \\CRPPDBP02B\ssis_greatice\jobfiles\SSIS_GREAT_ICE_Dim_All_Users.dtsx
Free Windows Admin Tool Kit Click here and download it now
January 20th, 2012 10:41pm

do we need to give full access to that service account. Currently it is configured as Everyone ReadWriteExecute........ I think everyone means it includes service also.Mark as answer if the post help you... Regards, Indraneel A
January 20th, 2012 10:45pm

I got a similar error message when I was not able to open the package. When I tried to open the package as xml it was just blank. The package might have been corrupted. Try to open the package and see if the top xml element is there. Regards Murali
Free Windows Admin Tool Kit Click here and download it now
January 23rd, 2012 12:13am

I faced a similar issue today but I was able to find a solution. First off, the error is generic and it could possibly arise in more than one situations. However, in my case the issue was simply that I was intentionally using the 32-bit version of DTExec in a job but as you can imagine a 64-bit SQL Agent will by default use the 64-bit Cmd.exe (from C:\WINDOWS\system32). Remember that on a 64-bit machine by default (at least in most scenarios) Windows would invoke the 64-bit version of a utility if it exists. Basically, the error "Unable to load the package as XML because of package does not have a valid XML format", in my case, occured because I was trying to execute 32-bit DTExec using a 64-bit Cmd.exe! So, what's the solution. Just use the 32-bit Cmd.exe (from C:\WINDOWS\SysWOW64). For those new to 32 vs 64 bit directories on Windows see this helpful article: http://www.samlogic.net/articles/32-64-bit-windows-folder-x86-syswow64.htm In your case, the situation might be REVERSE. Make sure the Cmd and DTExec match at the bit level. Amar
February 18th, 2012 8:20pm

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

Other recent topics Other recent topics