Post reply

Exporting an SSIS Package

  • May 15, 2014 at 9:43 am

    #293309

    Hi We use sql2008r2

    The other day a collegeue asked for a copy of dataload package that we use in SSIS. I right clicked the package and selected 'EXPORT' and exported it to the file system on the server.

    I then copied the file to the users drive.

    Since then I have noticed that the package doesn't run.

    Does 'Exporting' it remove the package off the server - because I can still see it there, but just wondered if the export has done something 'funky' with the package. Maybe a coincidence that it has stopped working but often in sql these things are related.

    By the way, I have just imported it back where it said the package already exists and do i wish to overwrite it - to which i said yes. From that I presume the export process did not remove the package - but may it have corrupted the original package or something similar ?

    Any advice on this would be appreciated.

    Thanks

  • May 15, 2014 at 10:10 am

    #1713920

    PearlJammer1 (5/15/2014)

    Hi We use sql2008r2

    The other day a collegeue asked for a copy of dataload package that we use in SSIS. I right clicked the package and selected 'EXPORT' and exported it to the file system on the server.

    I then copied the file to the users drive.

    Since then I have noticed that the package doesn't run.

    Does 'Exporting' it remove the package off the server - because I can still see it there, but just wondered if the export has done something 'funky' with the package. Maybe a coincidence that it has stopped working but often in sql these things are related.

    By the way, I have just imported it back where it said the package already exists and do i wish to overwrite it - to which i said yes. From that I presume the export process did not remove the package - but may it have corrupted the original package or something similar ?

    Any advice on this would be appreciated.

    Thanks

    I think it's a coincidence - I haven't heard of this problem before.

    What error message do you get when the package attempts to run?

  • May 15, 2014 at 10:55 am

    #1713948

    PearlJammer1 (5/15/2014)

    Hi We use sql2008r2

    The other day a collegeue asked for a copy of dataload package that we use in SSIS. I right clicked the package and selected 'EXPORT' and exported it to the file system on the server.

    I then copied the file to the users drive.

    Since then I have noticed that the package doesn't run.

    Does 'Exporting' it remove the package off the server - because I can still see it there, but just wondered if the export has done something 'funky' with the package. Maybe a coincidence that it has stopped working but often in sql these things are related.

    By the way, I have just imported it back where it said the package already exists and do i wish to overwrite it - to which i said yes. From that I presume the export process did not remove the package - but may it have corrupted the original package or something similar ?

    Any advice on this would be appreciated.

    Thanks

    Came across this problem few years back, ended up with removing it and importing it again from the source control. Since that worked, I did not look any further.

    😎

  • May 15, 2014 at 1:50 pm

    #1714018

    The error message is very vague. It just says it failed to execute a stored proc that the package calls. I can't be more specific at the time of posting this as I'm not at work now. When I get back in, and if the re-import of the package hasn't fixed it, I'll post the full error message.

    Thanks for the help thus far guys.

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

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