Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
im1dermike
Posting Yak Master
222 Posts |
 Posted - 2009-07-21 : 08:42:41
|
| I have dozens of packages I've created on a test machine which manipulate database objects that work fine. When I move them to another machine, I get login errors. After some investigating, I have found that the OLEDB connection manager objects in my SSIS package does not retain the password.How can I get the packages to retain the password when I move them to another machine without having to manually re-entering them each time? |
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
|
|
im1dermike
Posting Yak Master
222 Posts |
Posted - 2009-07-21 : 12:39:37
|
| Thanks a lot, Rick.I reviewed both links. In the first link, the first answer is very involved and it will take forever to execute all of those steps for 3 dozen packages.The second answer regarding the Deployment Utility seemed much more appealing. I just tried to do it, though, and got the following message when I tried to execute a package on the new machine:[Execute SQL Task] Error: Failed to acquire connection "DestinationConnection". Connection may not be configured correctly or you may not have the right permissions on this connection. I manually entered and saved the password again and it worked so that method does not retain the password.Am I to understand that the first option is the only one that allows you to move the packages from one machine to another successfully? |
 |
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2009-07-22 : 03:51:07
|
| No, the configuration file should allow you to deploy the package to the second machine. Once you have deployed the package (via the manifest file - you have to complete this step), you should then be able to just load it back into a store on your second machine without issues if you want to open it in BIDS. |
|
|
|
im1dermike
Posting Yak Master
222 Posts |
Posted - 2009-07-22 : 11:55:05
|
| Rick: I tried using the deployment utility. I built the project, copied the deployment bin into the 2nd machine, and then ran the manifest file. I get the same error I was getting when I just copied and pasted it where it's missing the connection password... |
|
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2009-07-23 : 03:49:46
|
| Thats strange as it should work, when you create the config file, are you dsefinitely ticking the connection object at the top level? |
|
|
|
im1dermike
Posting Yak Master
222 Posts |
Posted - 2009-07-23 : 09:02:22
|
| Rick: I'm not talking about config file method. I'm talking about the easier deployment utility method. I believe the config file method works, but it's like 50 times more involved than the deployment utility method especially when I'm dealing with 3 dozen packages. This is why I'm trying to see if the deployment utility method works. This is the method I'm talking about when I say I can't get it to work. |
|
|
|
|
|
|
|
|
Issue moving packages