Cannot resolve a package path

I have a parent package - Main.dtsx that calls a number of child packages. I also use configuration packages as I must deploy the application across multiple environments.

Main.dtsx contains a single Ccnfiguration file - Child_Packages.dtsConfig. This contains the connection strings for all the child packages.

Each child package contains a single configuration file - Main.dtsConfig that contains a superset of OLE DB connections. That is no single child package uses all of the connections contained in main.dtsConfig.

Each child package will execute independently without error. However, when called from Main.dtsx, I get the following errors:

Error: 2007-08-15 15:44:22.93
Code: 0xC001000E
Source: UserSecurity
Description: The connection "CRM" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error
Warning: 2007-08-15 15:44:22.93
Code: 0x8001F02F
Source: UserSecurity
Description: Cannot resolve a package path to an object in the package ".Connections[CRM].Properties[ConnectionString]". Verify that the package path is valid.
End Warning
Warning: 2007-08-15 15:44:22.94
Code: 0x80012017
Source: UserSecurity
Description: The package path referenced an object that cannot be found: "\Package.Connections[CRM].Properties[ConnectionString]". This occurs when an attempt is made to resolve a package path to an object that cannot be found.
End Warning

I have seen discussions that suggest that these errors occur where the connection in the config file is not found in the child package. Is there any way of suppressing this ?

Are there any simpler methods that allow me to change connections in each environment?

I suspect I will end up having to tailor config files for each child package, but I live in hope.

Michael M.

Duh! The main cause of this error is the fact that the child packages do not contain all of the connections that are in Main.dtsConfig.

But it is a pain to have to add connections that you don't use to each package.

And it is pain that you can't use the Deployment utility because it crashes attempting to copy the same config files over.

|||

You can use individual configuration files if you want; that way each package uses only the config files that really requires. BTW, I think, a package does not fail because the configuration file has an entry that is not used by that package; rather you see a warning.

|||

Regarding: BTW, I think, a package does not fail...

What caused this error?

Code Snippet

Error: 2007-08-15 15:44:22.93
Code: 0xC001000E
Source: UserSecurity
Description: The connection "CRM" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error

As to writing individual config files, this is creates unneccessary work, IMHO. Other ETL packages can use a single config file.

The best solution would be to build a tool that updates the .dtsx files in each environment and then we don't need config files at all.