FIX: Error message when you run a SQL Server 2008 Integration Services package that uses a configuration table in SQL Server Business Intelligence Development Studio: “The connection "<Connection Name>" is not found”
- In Microsoft SQL Server 2008, you create a SQL Server Integration Services (SSIS) package.
- You use the SQL Server configuration type to create a configuration table for the package.
- In the configuration table, there is an invalid package path in the PackagePath column. For example, a package path does not exist. The package path can be for a connection manager, for an event handler, or for a log provider.
Error at Package: The connection "Connection Name" is not found. This error is thrown by Connections collection when the specific connection element is not found.
This issue is likely to occur when you use a shared configuration table in multiple packages. In these packages, the configuration filter values in the configuration table are the same for each package. For example, an object, such as a connection manager, does not exist in all packages. Therefore, you experience this issue when you run packages that do not have this object in SQL Server BIDS.
Note This issue does not occur in SQL Server 2005 Integration Services.
SQL Server 2008 Service Pack 1Important You must install this fix if you are running SQL Server 2008 Service Pack 1.
The fix for this issue was first released in Cumulative Update 5 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
Do not use the same configuration filter in a shared configuration table for multiple packages. Specify a different configuration filter for each package so that package objects are referenced for only one package in the configuration table.
Add a dummy object to the problematic package so that the package path for the object exists in the package.
For example, an SSIS package that is named “Pkg1” contains a connection manager that is named “CM1.” Another SSIS package that is named “Pkg2” contains a connection manager that is named “CM2.” In this scenario, these packages share the same configuration filter in a shared configuration table. To avoid this issue, add a dummy connection manager that is named “CM2” to “Pkg1.” Then, add a dummy connection manager that is named “CM1” to “Pkg2.”
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
Article ID: 974559 - Last Review: 10/10/2011 21:44:00 - Revision: 3.0
- kbsurveynew kbfix kbqfe kbexpertiseadvanced KB974559