SSIS Connection not found in package

Question

I\'m kind of new to SSIS programming, and I\'m having some problems deploying an SSIS package.

This package runs correctly on my PC, does everything it needs to do ..

Answer 1

In my case, I could solve this in an easier way. I opened the x.dtsConfig archive, and for an unknown reason this archive was not in the standard format, so ssis could not recognize the configurations. Fortunately, I had backed up the archive previously, so I just had to copy it to the original folder, and everything was working again.

Answer 2

This happened for me: SSIS-package not created by me started at some point behaving unexpectedly, like giving that Connection not found -error and my task was to fix it though. When I looked at Job Step Properties under SQL Agent jobs, it showed no Configurations in use and Data sources were exact they should be. But, error message pointed to something different. Then I opened .dtsx file in question and noticed that there IS package conf. set and in that package conf. file is connection name set wrong. So my advice is to compare .dtsx and .dtsConfig -files side by side.

Answer 3

This solution worked for me:

Go to SQL Server Management Studio, Right click on the failing step and select Properties -> Logging -> Remove the Log Provider, and then re-add it

Answer 4

Thank you for posting this issue.

One resolution: open the package in XML form through windows explorer, locate the GUID for the connection manager that cant be found. In my case, it was a bonked EventHandler connection that was corrupted. This same connection manager was used in the control flow but somehow was not corrupted there, so it was not obvious to the user via the UI. Since the XML pointed to an event handler connection manager, I opened the event handler tab in the UI and it immediately displayed the wonderful RED X on the source and targets that were referencing the corrupted connection manager ID. I repointed it to the correct manager, rebuilt the pkg and saved. Good to go.

The key was opening the pkg in XML format and locating the GUID in the code to see where it was failing. If I was not able to find a valid reference to it in the UI, I was going to either rename the XML connection to another known GUID within the XML and then go into the UI and repoint it again, or delete it altogether.

Good luck.

Answer 5

i had the same issue and niether of the above resoved it. It turns out there was an old sql task that was disabled on the bottom right corner of my ssis that i really had to look for to find. Once i deleted this all was well

Answer 6

What i did to solve this problem was simple. I had to rename my SQL Server so that it would respond to the (localhos) tag. After that i changed all the connections on the SSIS and i rebuild the solution...it worked. hope it helps you