Consider the following scenario.
- 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.
In this scenario, when you run the package in SQL Server Business Intelligence Development Studio (BIDS), you receive the following error message:
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:
Cumulative update package 5 for SQL Server 2008 Service Pack 1
Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
To work around this issue, use one of the following methods:Method 1
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.Method 2
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.”
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
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:
New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates