Post reply

Orphaned Connection

  • January 5, 2007 at 2:42 pm

    #116758

    Hello,

    I am getting the following error when I execute a package that I have created:

     

    Error: 0xC001000E at : The connection "{CFD8CC1C-8406-4245-BFD4-365B49081523}" is not found. This error is thrown by Connections collection when the specific connection element is not found.

     

    I am assuming this is from a connection that I have since deleted in my connections manager.  The connections in my connection manager are all being utilized, and all connections are set in my individual tasks.  I am assuming I no longer need the old conneciton that the error is referencing, but am not sure how to delete it.

    Doeas anyone know how to get rid of this "Phantom" conneciton?

    aroney

  • January 7, 2007 at 10:44 pm

    #681698

    Check the following thread... it may resolve your issue too...

    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=255347&SiteID=1

     

    MohammedU
    Microsoft SQL Server MVP

  • January 8, 2007 at 9:09 am

    #681803

    Thank you for the link.  Unfortunately, I don't believe this will solve my issue.  The reason being is that my SSIS project/solution is currently on my local client (which isn't running integration services).  I have not deployed the project anywhere yet, so I don't think accounts for the Integration Service is my issue (although I have definitely noted that it may be beneficial to run SSIS under the same account as SQL).

    So, I am still stuck.  Any other ideas?

    Thanks in advance for your help!

  • January 8, 2007 at 9:49 am

    #681817

    I think you'll have to check properties of each task in your package. One of the tasks is still referring to the old connection. Wherever you see that guid show up in a task you'll have to select the new connection.

    Hope that helps!!!

    MarkA

  • January 12, 2007 at 8:21 am

    #682922

    I have the  same issue. I did get rid of a connection initially (updating an old package)

    The connection "{D24743FC-89E4-44F0-A972-4154EE287E71}" is not found. This error is thrown by Connections collection when the specific connection element is not found.

    All task are pointing to valid connections. Package explorer does not list this connection either.

    My package completes successfully but throws this error. It almost feels like a SSIS bug.

    Any ideas?

    Asim.

     

  • January 12, 2007 at 9:07 am

    #682953

    Asim,

    I was feeling much like this was a bug too.  Based on MarkA's post, I did a more thorough inventory of my transformations (this is a complete ETL layer so there are many of them).  I found one transformation that I actually disabled way back when, that was still referencing the old connection.  Fixed the connection in that transformation, and things are all better now.

    HTH.

  • January 12, 2007 at 9:55 am

    #682969

    Well, I'm looking, but can't find anything.

    Even if there is a disabled task, There should be a way to look up the offending task by the GUID in the error message.

     

    Asim.

     

  • January 7, 2008 at 11:45 pm

    #765587

    In design mode, click on the Package Explorer tab

    Open the Log Providers node

    You should delete the log file that is causing this problem.

  • February 27, 2008 at 9:01 am

    #782591

    I had the same issue. I was able to resolve it by changing the connection (id) property in the Control Flow tab on the Preparation SQL Task node.

    I am not sure this will work for you but it may be worth a look.

  • April 16, 2008 at 7:25 am

    #803068

    I just had this exact same thing happen and here is how I resolved it... Of course this revolves around logging but it sounds like this is common enough to post.

    First I removed all of the logging of the package (error popped up after I configured logging). And by that I 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.

  • August 4, 2009 at 10:13 am

    #1034383

    I had to edit the xml. I deleted the connection first and there remained some remants of the XML referring to that connection.

  • April 18, 2012 at 4:33 am

    #1475239

    It is a ssis bug some times it happens. try to create new one i think that will work.

Viewing 12 posts - 1 through 11 (of 11 total)

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