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 |
|
Bex
Aged Yak Warrior
580 Posts |
 Posted - 2009-08-28 : 10:02:27
|
| Hi thereI have created a package on my local machine, and enabled package configurations, and created a dtsConfig file.I gave a colleague a copy of the package and config file, and he installed on his sql server (msdb). The package is called by a job, so we changed the job to reference his server, and to use the config file. We also changed the connection strings in the config file.However, when the job runs, it fails (as it is still trying to connect to my machine). I then deployed the package to my box, performed the same steps, but then deleted the config file from the directory I specified. I expected it to fail. However, it didn't, and therefore, it is not using the config file.Is there something else that I need to configure to ensure the package uses the config file??? I didn't recall having these same issues before...... but its been a while since I have used SSISThanks in advanceHearty head pats |
|
|
Bex
Aged Yak Warrior
580 Posts |
Posted - 2009-08-28 : 12:21:54
|
| Ok, resolved. He manually changed the connection names in the package. Doh!Hearty head pats |
 |
|
|
|
|
|
Working with SSIS configuration files