Hi, Guys. Recently, i upgraded my SSIS 2005 project to SSIS 2008 via SQL Server 2008 SSIS package upgrade wizard. Then the package validation error occured when i debug the upgraded project in BIDS. Here is the error's detailed information: The connection "xxxx" is not found. This error is thrown by Connections Collection when the specific connection element is not found. In my project, all the packages share single configuration file and the SuppressConfigurationWarnings property is set to TRUE. The unfound connection is not exist in the current package but refered by the other package. The whole project runs fine in SSIS 2005. So, is this error the bug the SSIS 2008? I've also installed SQL Server 2008 SP1. How can i resolve this problem? Any help is appreciated. Thanks in advance! Best Regards.

What configuration mode are you using? Since you are using only one configuration file, I think you have to add all the connection managers mentioned in the config file in all the packages.Nitesh Rai- Please mark the post as answered if it answers your question

SSIS throws this error when your Package config file contains a configuration element which is not used by the package.. for example Config file is having a Configured valued of a variable but this variable is not used in that particular package. If you are sure that you anit using this element you can ignore the warning. Rahul Kumar, MCTS, India, http://sqlserversolutions.blogspot.com/

If there is a single Configuration file being used for all the connectiong managers, this can be a situation often faced. This means that every package that uses this Configuration file needs to have all the configuration values (Connection Strings, Variables, Log Providers) which exist in the Config file. e.g. If you are storing information for ConnectionManager1, ConnectionManager2, Variable1.. and son on collectively in the config file, then you need to set up all these in every single package of youra, no matter whether the package uses them or not. It is always advisable to use one configuration file per connection-manager. You might have to maintain many configuration files based on the number of connection managers you use, but that will save you from facing such situations. Alternatively, you can create a Package Template, add all these configuration objects to it and bind a single configuration file to it. Next time you need to add a new package, you can use this template and everything gets taken care of. This might, however, need you to redesign your existing packages. To know more about Package Templates, refer this link. Hope this helps. Cheers!! Muqadder.

I think you can ignore this.Please mark the post as answered to help others to choose the best. chandra sekhar pathivada | www.calsql.com (SQL Server Community Website)

Hi, Rai, I am using XML Configuration File mode. In the SSIS 2005 version project, I only add the required connection managers per package and the project runs fine. Does SSIS 2008 forced the developer to add every connection managers in each package even if the package doesn't need the connection? If so, I think the design is a bit unreasonable. Are there any other solutions? Best Regards.

Hi Sherawat, I can't ignore that since it is not a warning but a "Package Validation Error" in a information window. Best Regards.

Hi Muqadder, Thank you for your suggestions. Now it puzzles me a lot whether the feature that each package must contain all the connection managers mentioned in the configuration file is the particular feature in SQL Server 2008 since In my SSIS 2005 version project, the package runs fine only containing the necessary connection managers. The two solutions you advised might cost much time since there're lots of packages in the project and I also want to complete the upgrade with least change to the previous version. Best Regards.

The approach invloving use of Package Templates is a clean one, but as you said, needs time and effort. Since you are already tight with schedule, I'd suggest you make sure all the configuration components are available in all packages. For connection managers, you can simply copy and paste the connection managers across various packages. If there are variables involved in configuraion file as well, you'll manually have to create them with in each package, with exact same names everywhere. Or, you can use multiple configuration files and simply update your packages to use the ones needed. I haven't come across any config related issues with SQL server 2005, but I can confirm this behavior in SQL Server 2008. Hope this helps. Cheers!! Muqadder.

I'm having the same problem, over a year later. I posted to another board about it, but I can't seem to figure out how to resolve it. http://social.technet.microsoft.com/Forums/en-US/sqlintegrationservices/thread/fdfeef7b-7296-46e7-8a2d-f50022a41836 This used to work perfectly in SQL Server 2005. It is a problem in SSIS 2008 R2. I found this article, which explains the issue: [url]http://support.microsoft.com/kb/2142496[/url] The article gives the example of one package calling another package, where the child package doesn't have all the file connections that the parent connection has. However, this is just an example. ANY configuration table where there is a FilePath entry in it that is not defined as a connection is a problem. If this is the case, if you have 200 packages, every one of those packages must be defined as connections in every package. That seems silly, and it wasn't that way in 2005. The article says you upgrade to the latest SP/CU, it should fix the problem. Based on the article, I have patched the server to now be SQL Server 2008 R2 x86 SP1 CU2 (@@VERSION now shows Microsoft SQL Server 2008 R2 (SP1) - 10.50.2772.0). However, this doesn't solve the problem, as I continue to get the error "The connection "SSIS_Address.dtsx" is not found. This error is thrown by Connections collection when the specific connection element is not found." I get one for each FilePath in the SSIS_Configurations table, as there are no other packages referenced in my package. I'm at a loss. I believe I did everything that was required, and I'm stuck. This worked perfectly in SSIS in SQL Server 2005.

If you have confirmed this behavior in the specific version of SQL server, I'd suggest to submit a Connect item on Microsoft's connect website here: https://connect.microsoft.com/SQLServer/Feedback Include as much details as you can so that the Product development team can try and replicate the issue before providing a feedback on your submission. Hope this helsp. Cheers! Muqadder.

Attempting to set missing ConnectionManagers from a config file will cause the package to error. Attempting to set missing variables only causes a warning. Because of this behavior we have adopted a different approach to setting ConnectionManagers. Firstly we only ever use the config file to set variables. To set a ConnectionManager we first set two variables for Server and Catalog from the config file, we then set the ConnectionManager using an Expression. We have been using this method for some three years now whithout any problems. Tim