Error loading Load_CTL_Staging_Initial (1).dtsx:The connection "{c27271c5-2084-45ce-bea8-1105274f4fb4}" is not found.

Question

Error loading Load_CTL_Staging_Initial (1).dtsx:The connection "{c27271c5-2084-45ce-bea8-1105274f4fb4}" is not found.

Welsh Corgi

SSC Guru

Points: 116520
More actions
August 7, 2012 at 10:02 am

#279926

All of a sudden I'm getting the following error:
Error1Error loading Load_CTL_Staging_Initial (1).dtsx:
The connection "{c27271c5-2084-45ce-bea8-1105274f4fb4}" is not found.
This error is thrown by Connections collection when the specific connection element is not found.
C:\SSIS\Debug\Load_CTL_Staging_Initial (1).dtsx11
It occurs 123 times.
The package performs the load sucessfully. I just get the error when it loads.
Any ideas on how I can isolate and eliminate the error?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 1

I found that the problem was in the Event Handler for each task.

I had copied the task form another package. I changed the connection on each task as is required but I forgot about the event handler tasks.

Hopefully after I change each connection I will be all clear but the message is very cryptic.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 2

I changed the connect for each execute SQL Task associated with each Event Handler and I'm still getting 43 errors.

How can I isolate the source of the problem?

Perhaps I could edit the package in notepad and search for the GUID and identify the objects?

Any ideas or thoughts would be greatly appreciated.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 3

Welsh Corgi (8/7/2012)
I changed the connect for each execute SQL Task associated with each Event Handler and I'm still getting 43 errors.
How can I isolate the source of the problem?
Perhaps I could edit the package in notepad and search for the GUID and identify the objects?
Any ideas or thoughts would be greatly appreciated.

I hate this, there is guid that needs to be changed and there is a way to change it but since I haven't worked with SSIS for almost two years now I can't remember how to fix this. And it is a fairly easy fix. I ran into this myself when doing copy/paste when building SSIS packages.

I'll have to do some more research.

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 4

Also, it may help if you post the error message you are still getting.

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 5

Lynn Pettis (8/7/2012)
Also, it may help if you post the error message you are still getting.

I was still getting the same error. The only thing that changed was the number of errors that I got.

The error was identical.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 6

I tried editing the XML FIle in notepad & replacing the GUID with a valid one but I got an error that the connect was not valid.

I had to delete every Execute SQL Server Task on each Error Handler Event.

After that I did not get any errors.

So then I copied the same task from another package and I changed the connection from a GUID to a valid connection name.

LESSON LEARNED. If you copy a task that has an Event Handler associated with it.

Change the Connection before you copy & paste, otherwise you propagate the error.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 7

Glad you were able to fix it as I still haven't found what I was looking for.