The connection "" is not found. This error is thrown by Connections collection when the specific connection element is not found
I've got a package which reads a text file into a table and updates another. I set upconfigurations so that I could import it into the SSIS store on both my dev and live servers. Now, I'm getting this error. I tried removing the configs and am still getting it. I've been through each step and everything looks okay. Does anyone have any idea (a) what's wrong, (b) how to localise the error or (c) get any additional information? Or do I just have to recreate the package from scratch? TITLE: Package Validation Error------------------------------ Package Validation Error ------------------------------ADDITIONAL INFORMATION: Error at PartnerLinkFlatFileImporter: The connection "" is not found. This error is thrown by Connections collection when the specific connection element is not found. Error at PartnerLinkFlatFileImporter [Log provider "SSIS log provider for SQL Server"]: The connection manager "" is not found. A component failed to find the connection manager in the Connections collection. (Microsoft.DataTransformationServices.VsIntegration) ------------------------------BUTTONS: OK------------------------------
May 1st, 2007 11:43am
Did you build this package, or did a wizard such as the import/export wizard?Also, if you open up the .dtsx file in Notepad (or your favorite text editor) you can search for:"DTS:ConnectionManager"When you find that section, look for the DTS: Property titled, "ObjectName". Do you have something listed there, or is it blank? Keep searching through all of your connection managers if you have more than one. See if there is one listed there with an empty ObjectName property.
May 1st, 2007 11:52am
Thanks for your help. It turned out that I when I added a SQL Server logging provider (to help solve another problem) I didn't add the connection string name to the Configuration column. Oh well! Another afternoon to learn another simple thing!
May 1st, 2007 12:34pm
Thanks!! I had exactly the same sit. Your solution caused me to recheck this config setting and it was right on track.
June 1st, 2007 1:46pm
October 2nd, 2007 10:38am
I just had this exact same thing happen and here is how I resolved it... First I removed all of the logging of the package (error popped up after I configured logging). And by thatI mean everything having to do with logging, un-checking all of the containers for the logging, deleting the logs for the container and making sure no events are being logged. Save the package, exit Studio and reopen the package. When I came back in the error was gone now to handle the logging. When creating the logging options make sure to specify a configuration for the provider when enabling logging this helps ensure that the connection is present when you complete the logging steps. btw the first thing I did was to open the .dtsx file in my fav. xlm editor and search for "" in the DTS:Connections or anything else that would point me in the right direction and all looked great. The error only went away when I did the steps that I outlined. Hope this helps.
April 16th, 2008 9:13am
Phil Brammer wrote: Did you build this package, or did a wizard such as the import/export wizard?what difference between build this package or did a wizard such as the import/export wizard ?
September 18th, 2008 8:14pm
Hi Guys!I've been struggeling with the same problem for the most of the day now, and reading your posts led me in the right direction - hence I wanted to share my findings.In my case the problem was not related to the logging-definition, but to the configuration-file that referenced an "old" connection manager. Opening up the configuration-file in notepad, and removing the xml-node in question solved the problem!Regards,Yonzo
January 20th, 2009 6:46am
A year later - I was having the same issue, and this post helped me! I had to reconfigure my connection in my logging task. No errors now!
January 7th, 2010 4:50pm
Saved me too, an orphaned connection in the config. Thanks!
February 5th, 2010 1:25pm
Here we are three years later and still finding the answer! Thank youDerek M. Kennard
August 20th, 2010 10:34am
Hi there, can someone answer me this. I have the same issue, the reason I have it is because I have A) renamed the connection managers to be something more meaninful than they were before, and B) to have more of the information inside a dtsconfig file. Are we saying that if we do this task, we have to manually open the code in notepad and removed the old entries? Is this not dangerous to do this? Should SSIS be able to handle this? I am not sure you should have to do this manual task just by renaming connection managers? Your answers would be appreciated. Many Thanks in advance
October 19th, 2010 11:05am
Thanks, it helped me today though this post is 3 years old :)
January 11th, 2011 11:31am
This helped, thank you very much, Alex
December 2nd, 2011 2:40am
5 years later and I had the same issue. Did not think to look for this as a first step, but found this post right away on a Bing search.
August 8th, 2012 9:16am