Connection Problem

I created a package with two oledb connections in the connection manager....which was running perfectly...later i deleted these connections and added two new connections....and applied these to task with the new connection..

Now i run the package i come up with the following error...connection not found

Error 1 Error loading test.dtsx: The connection "SQL-DEV.sql_dev" is not found. This error is thrown by Connections collection when the specific connection element is not found. c:\documents and settings\myname\desktop\integration services project\ssis\test.dtsx 1 1

when i double click the error it goes to xml code...i dont know what need to be done...please help

Did you name the "new" connections the same as the old connections?|||No i didnt name them with the same name as the old once but the New connections are just the same as old connections...selecting server and database..|||Is "SQL-DEV.sql_dev" the name of a new connection or one of the ones you deleted?|||

Hi Sureshv,

The problem is the Connection Managers, for whatever reason, were not completely deleted. Their metadata is still stored inside the XML source for the SSIS files.

Naming the new Connection Managers the same as the old Connection Managers will not impact this error - Connection Managers are identified by GUIDs in SSIS. If you can identify the GUID of the deleted Connection Managers (perhaps by process of elimination), and comment them out inside the metadata, the package will stop throwing the error.

Hope this helps,
Andy

|||Andy,
ALL GUI screens represent a connection manager by its name, not GUID. This is precisely why I asked the question that I did. I imagined a scenario where the metadata was not cleaned up properly and when Sureshv picked the connection manager [name] in the drop down box, it was associated with a [now] defunct GUID, hence the resulting error.

In the end I think we can agree the likely culprit is bad metadata.|||

Hi Phil,

Thanks. I've seen some tasks respond differently to this scenario. Some of them pick up the changes automatically and some don't. I've also seen metadata corruption make this completely unpredicatable.

Yep - we agree this is the culprit. It's no fun to clean up a large package with corrupt metadat either - good luck Sureshv.

Andy

|||

In general when you delete a connection manager that is being used by a task; that task keeps pointing to the deleted connection manager GUID; untill you open the task and chose a diffrent one.

To the Original poster, make sure you revist all the tasks that were using those connection managers and refresh the connection metadata. If the package has logging enable and it was using one of the deleted CM; you have to refresh it as well.

|||i dont find the old connection name with in connection managers in the xml...So what do i do? i am afraid i will break my package...any more solutions?|||Did you check and correct the package logging?|||i did not set any package logging for this package..sqlsql