Post reply

Exact copy of SSIS package fails

  • September 20, 2010 at 5:04 am

    #229418

    Hello, I have taken a copy of an existing working ssis package and deployed that copy to another directory on the same machine. All the parameters/variables remain the same but the package fails when it is executed with the error:

    [Execute SQL Task] Error: Failed to acquire connection "CONN". Connection may not be configured correctly or you may not have the right permissions on this connection. Login failed for user 'sa'.

    I've ensured that I am running the package under the same account and I test the all connection in connection manager and it connects fine. I also have package configurations enabled and have modified the connection of the configuration file to point to the new directory.

    I can connect to the database in management studio using the exact same sql server login credentials with no issues, so why wont the copied ssis package accept the same credentials?

    any suggestions

    thanks

  • September 20, 2010 at 8:25 am

    #1224060

    ok, found the cause of the problem...Thanks

  • September 20, 2010 at 8:27 am

    #1224065

    Just for curiosity: what was the issue? (and how did you solve it?)

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • September 20, 2010 at 10:10 am

    #1224164

    Not sure if this was your solution, or not, but when copying packages, it's a good idea to reset the GUIDs in the new copy of the package to refresh everything ... it also is good to manually check connections within the package, as they may have linked to an older/changed GUID, causing the connection to fail. Finally, verifying/setting the ProtectionLevel of the package is a good check, too, if someone else may be running the package (depending on your setup and environment).

  • September 21, 2010 at 6:41 am

    #1224742

    Turns out the password in the configuration file was being wiped every time the package was executed. I just removed the configuration and setup a new one and it worked normally.

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

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