Hi, I'm sitting down again to see if I can get configuration files to work. To test, I've set up a simple package that reads a flat file and writes to a table. I've enabled configurations by clicking the checkbox in the configurations window. I am using an xml file on the local server, and there is an absolute path defined to the file. I also added a password to the xml file so the connection will work. To this point, everything works. However, when I go into the configuration file and edit it to point to another server, it doesn't pick it up! That is, when I run my package, it still writes the data to the old server. It's like it's completely ignoring the configuration file and just using the OLE DB connection manager instead. However, if I delete the OLE DB conn mgr, the package doesn't work. Please help... this is where I got stuck before. Thank you

Which property are you applying the configuration to?If you are using BIDS to run the package, look in the progress tab to see if you spot any warning message about the configurationBTW, do not expect the package to work if you delete the connection manager. Package configurations alter property values of existing objects. This tutorial shows some package configuration basics:http://technet.microsoft.com/en-us/library/ms167153.aspx

I will tell you exactly: Configurations > Connection Managers > myserver.database.login > Properties > Connection String All of the above are checked boxes in the Package Configuration Wizard. But it still ignores any changes I make in the configuration file.

Sadie,Package configuration works well. The only thing I can think of causing this issue is that, for some reason, the package is failing on getting access to the file. In those cases, SSIS generates a warning in the log (if package logging OnWarining is enable) or in the progress tab of BIDS. The warning is generated and the the values provided at design time are used.

Someone correct me if I'm wrong here... When in BIDS, configuration values are "updated" at load time - when you open the package in Visual Studio. If you make changes to a configuration file while you have BIDS open, you'd need to close the solution and reopen it in BIDS for the new updated connections from the configuration file to show up. Right?You can check your connection values by selecting the connection manager in BIDS that should be affected by your configuration and look at the Properties pane.

Jamie Pick wrote: Someone correct me if I'm wrong here... When in BIDS, configuration values are "updated" at load time - when you open the package in Visual Studio. If you make changes to a configuration file while you have BIDS open, you'd need to close the solution and reopen it in BIDS for the new updated connections from the configuration file to show up. Right?You can check your connection values by selecting the connection manager in BIDS that should be affected by your configuration and look at the Properties pane. Yes and no. If you debug the package, without restarting BIDS, it will pick up the new configuration values.

Yes and no. If you debug the package, without restarting BIDS, it will pick up the new configuration values.Ahh yes, thanks for clarifying. I was thinking of my experience with indirect configurations and envrionment variables.

Phil, Its your Junior... As of my knowlege, When we change some thing in the package the metadata won't update instantly at all time. So that only its suggested to recreate the connection or the best way is to use the "load with update" option.Also, In my past 2 projects, I was using the XML config file and never met with an issue like the one discussed here.

Manikandan S wrote: Phil, Its your Junior... As of my knowlege, When we change some thing in the package the metadata won't update instantly at all time. So that only its suggested to recreate the connection or the best way is to use the "load with update" option. We're not talking about metadata, we're talking about configurations. Big difference. Manikandan S wrote: Also, In my past 2 projects, I was using the XML config file and never met with an issue like the one discussed here. Yep, me either, but it requires a few things to fall in place for them to work flawlessly. Permissions, absolute file paths, no expressions set on properties being exposed by configurations, etc...

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