When opining a DTSX file with a SSIS (SQL Server Integration Services) package, the following message appeared:
Error 1
Error loading XXX.dtsx: The connection "{XXX}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
However, none of the executables inside the package showed a red error sign and thus the big question was: WTF?
It turns out that the package was configured to use SQL Server Logging and the connection used for this log was removed!
So if you ever came across this error have a look at the package Logging or Configurations.
A pertinent post related to a practical problem. Thanks Tex!
ReplyDeleteThis saved my day, thanks alot!
ReplyDeleteGreat tip - thanks! :)
ReplyDeleteOh ya, thanks!!!
ReplyDeleteI really hate the logging providers, they don't log anything especially useful and then do this kind of thing to us when we want to change the name of a connection.
If only Microsoft would have included some context for the offending connection...hey I can dream can't I?
Thank You very much! Saved me hours of work....I was ready to re-write the entire package :)
ReplyDeleteIn my case, it was a disabled componenet which was using an old connection. It may be helpful.
ReplyDeleteFor me, I hadn't selected the connection for the Logging - it was my first time trying and there was no error when I saved it. Thanks for the post!
ReplyDeleteThanks. You saved me!
ReplyDeleteYou sir, are a superstar. Other pages have sent me into changing GUIDs in the raw XML etc. while the actual solution was so straightforward. Thanks!
ReplyDeleteThanks, that was an awkward one.
ReplyDelete