Load SSIS package with XML code only

  • Hi SSC,

    I made a copy of an SSIS package XML. I saved it to notepad with a ".DTSX" extension. I am trying to load that file into SSIS but I keep getting errors. Here are my steps...

    1) Add existing package as file system.
    2) Select the ".DTSX" file.
    3) Error says that the file is not well formed, but I pulled the XML from an existing package that is in production.

    Any help would be greatly appreciated.

    Everyone has a plan until they get punched in the mouth. --Mike Tyson

  • Lord Slaagh - Tuesday, July 3, 2018 8:52 AM

    Hi SSC,

    I made a copy of an SSIS package XML. I saved it to notepad with a ".DTSX" extension. I am trying to load that file into SSIS but I keep getting errors. Here are my steps...

    1) Add existing package as file system.
    2) Select the ".DTSX" file.
    3) Error says that the file is not well formed, but I pulled the XML from an existing package that is in production.

    Any help would be greatly appreciated.

    Why can't you take an exact file copy of the deployed package?

    Nonetheless, what you are doing sounds like it should work. I wonder whether the package contains any extended characters which are being corrupted in transit.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • Hi Phil,

    I am waiting on access to TFS, so yeah, it would be great if I could just grab the package itself. They only provided me with the XML. It's due Friday, of course 🙂

    Thanks

    Everyone has a plan until they get punched in the mouth. --Mike Tyson

  • Lord Slaagh - Tuesday, July 3, 2018 9:05 AM

    Hi Phil,

    I am waiting on access to TFS, so yeah, it would be great if I could just grab the package itself. They only provided me with the XML. It's due Friday, of course 🙂

    Thanks

    I see. I think the first thing I would do is compare the XML provided with that from a simple package that works & look for anomalies.

    Use a graphical XML editor if you can ... it makes navigating XML files much less of a chore.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply