Good morning, I've always had relatively good luck with deploying packages using Deployment Manifest. Recently I've started having an issue though... Manifest does not change the paths to config files inside the package but deploys config files to the right location. I have to open dtsx file in XML editor and modify the paths manually. Does anyone know what's causing this? Any suggestions on how to fix this?

Couple options depending on how you execute the packages. Normally I just set the config file location in the SQL Agent job that executes the package or pass the config file in the call to DTExec. Or you could use an environment variable to specify the config file path - works well if you use a common config file for multiple packages.Chuck

But the manifest file when opened launches a wizard where you can specify the new location for the configuration?Arthur My Blog

Arthur, I do specify new location and everything is deployed there just fine. Deployment works except paths inside dtsx files are not being changed to a new location.

The deployment utility is nothing more complex that a way to copy the files. It doesn't open up your dtsx files and correct paths.Chuck

Chuck, I've been doing this for at least 5 years and it did change paths to a new location until now. That's why I'm asking this question to see if anybody ran into this issue....

This is odd, were any patches applied? And what if you try to deploy a previously well working manifest?Arthur My Blog

I did apply some patches not long time ago. Unfortunately previous manifests do not contain up-to-date files. At this point I'm willing to try Environmental Variable to store the path to config files.

There is now an utility available in CodePlex which can be used to batch update SSIS Package Configuration File paths without using BIDS or manually editing the package XML: http://ssisconfigeditor.codeplex.com/

Deb, Thank you for your response. This utility can definitely be used in certain deployment situations. We found a solution to my initial problem. Config files were checked in with the project and appeared in Misc folder in Visual Studio. When we removed config files from the project, and rebuit the manifest, config paths started changing during deployment...