I have a shared configuration file used by multiple packages. It contains
connection strings for connection managers.

When I open up my project I get the following error for most packages:

There were errors while the package was being loaded.
The package might be corrupted.
See the Error List for details.

The project error list contains multiple listings of:

Error loading PackageName.dtsx: The connection "ConnectionName" is not
found. This error is thrown by Connection collection when the specific
connection is not found.

In each case, the connection is one that is referred to in the shared
configuration file but is not used in the package. I got rid of the errors by
laboriously including every connection manager in the config file in every
package. I also had to close and reopen the solution to get a clean build.

However I have the feeling that I didn't need to do this when I last worked
with this solution (a week or so ago). So I'm wondering is this expected
behaviour? Is it really necessary to create every connection referenced in
the config file in every package that uses the config file?

If so, life would be a lot easier if BIDS warned instead of erroring in this
situation.
If not, my solution must have got screwy. Any suggestions on how to repair it?

David

(And before you ask, this has nothing to do with package protection levels -
I'm already using EncryptSensitiveWithPassword.)

Hello David,

I think this is the expected behaviour. The configuration file tries to
get applied up fromt of the package and it will try to do what is in the
file. You could split of "Common" connections into their own file and "Specific"
connections to another.


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com