Sign in
 
Home20122008 R2200820052000LibraryForums
SQL Server >
> 
> 
Trouble Opening a SSIS 2005 Package to Convert it to 2008

Respondida Trouble Opening a SSIS 2005 Package to Convert it to 2008

  • Wednesday, March 20, 2013 2:44 PM
     
     
    Sign In to Vote
    0

    When I try to open this dtsx file in VS2005, I get the error below.

    When I look at 1748, Column 1026 it seems like there is missing XML code so I am not sure what is going on. The package is at the root on the D: drive, so there is not a long path name that could be causing the this....

    We are trying to convert these packages to 2008, but cannot even open them in a 2005 format. I get the same thing when I tried to open the file in VS2008.  Here is the thing is it possible to do this if we just have the dtsx file and not the whole solution?  I have opened built packages before so this seems somewhat different as far as what is going on....

    The other strange thing is when I open the other packages that I have the same issue the Line number is different but it is close to the same column number, like 1027.

    I have also tried creating a solution and then adding the packages, but I get the same result.....

    Any help would be appreciated

    TITLE: Microsoft Visual Studio
    ------------------------------

    Failed to load XML from package file "D:\xxxxxxLoad_FinalizeClientLoad.dtsx" due to error 0xC00CE556 "Invalid at the top level of the document. Line 1748, Column 1026".  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.


    ------------------------------
    ADDITIONAL INFORMATION:

    Failed to load XML from package file "D:\xxxxxLoad_FinalizeClientLoad.dtsx" due to error 0xC00CE556 "Invalid at the top level of the document. Line 1748, Column 1026".  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.
     ({EFF0A7D3-0C24-40CB-85C9-C56D1C186785})

    ------------------------------
    BUTTONS:

    OK
    ------------------------------

    DBA Developer

     

All Replies

  • Thursday, March 21, 2013 7:40 PM
    Moderator
     
     Answered
    Sign In to Vote
    0

    It is a file corruption.

    You need to find a spare copy of the package and try opening it or have the package extracted from the SSIS store anew to open.

    Besides, it is basically a plain text XML (the .dtsx file), so you can open it in a XML editor and have it inspected.

    My suspicion is somehow the package was built on a system having different Unicode settings.

    Arthur My Blog