Hello, I have a SSIS package that is making one database connection (dbMAIN). I am using the XML File Configuration to specify dbMAIN's properties (server, database, password, etc).The problem is that the File Configuration contains entries for multiple databases (dbMAIN, dbTEST, dbSTAGING, etc)When the SSIS is run through dtexec.exe, I get this error:Error: 2007-04-10 16:52:23.39 Code: 0xC001000E Source: TEST Description: The connection "DDMAIN" is not found. This error is thrown by Connections collection when the specific connection element is not found.End ErrorI do not want it to give me an error. The XML File must house all our database connections. What can I do?`Le

I'm not entirely sure about the scenario you're describing, but I do notice that in the text you call the connection "dbMain", but in the error the connection being sought is "DDMAIN". Is this problematic?Are you using an XML file as a Package Configuration? Why wouldn't you just have separate files for each database? That error doesn't look like it's related to reading a Package Configuration.

We have over 70 SSIS packages, all using different database connections across a several dozen databases, most of them using two main databases. As we move these to test/staging/live (different servers, different database names, different usernames, different passwords), it makes more sense to have a single file Configuration file, otherwise it will be a nightmare to go through and make changes to each file every single time we create a new environment.The problem does indeed come from the file configuration. Just create a connection string in your file configuration and run it, and you will see the error too.`Le~Le

We had a similar problem with XML config files. We ended up switching to database configurations. And we set the connection string for the configuration database via the command line.

TheLe wrote: We have over 70 SSIS packages, all using different database connections across a several dozen databases, most of them using two main databases. As we move these to test/staging/live (different servers, different database names, different usernames, different passwords), it makes more sense to have a single file Configuration file, otherwise it will be a nightmare to go through and make changes to each file every single time we create a new environment.The problem does indeed come from the file configuration. Just create a connection string in your file configuration and run it, and you will see the error too.`Le~Le Personally I always espouse the notion of having one file per configuration rather than one file for all configurations because it solves the problem you are having. I don't see much difference between making a single change toN files or makingN changes to a single file. I also suggest that you store the ConnectionString property which encompasses all of the properties that you are currently storing. That will mean you only have to change one thing for each connection manager. Are you running the RTM version of SSIS? I believe (but cannot be 100% certain) that there was a behaviour change in SP1. If yourunning a package on RTM then entries in the XML configuration file that refer to properties not present in the package will cause errors - in SP1 they will raise warnings. Also, you can suppress these warnings by setting SuppressConfigurationWarnings=TRUE. [To be honest, I thought that this wsa the behaviour in RTM as well but seeig as you are getting these errors that would appear to not be the case] You should also read this: http://sqljunkies.com/WebLog/knight_reign/search.aspx?q=suppressconfigurationwarnings&p=1 Hope that helps. -Jamie

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/