Thursday, October 25, 2007

SSIS Error while loading a package: "The connection xxx is not found"

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.

10 comments:

  1. A pertinent post related to a practical problem. Thanks Tex!

    ReplyDelete
  2. This saved my day, thanks alot!

    ReplyDelete
  3. Great tip - thanks! :)

    ReplyDelete
  4. Oh ya, thanks!!!

    I 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?

    ReplyDelete
  5. Thank You very much! Saved me hours of work....I was ready to re-write the entire package :)

    ReplyDelete
  6. In my case, it was a disabled componenet which was using an old connection. It may be helpful.

    ReplyDelete
  7. For 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!

    ReplyDelete
  8. Thanks. You saved me!

    ReplyDelete
  9. You 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!

    ReplyDelete
  10. Thanks, that was an awkward one.

    ReplyDelete