We have several SSIS packages that have been running fine.ÃÂ The last time they changed were on 01/30/2009.ÃÂ
We're using package configurations pointing to a SQL server table (sql 2005).ÃÂ The packages run from one clustered computer, which has a default instance of sql server enterprice on 64-bit machine, the connection is to another clustered box, which has a named instance of sql server.ÃÂ All of a sudden we started getting "Error loading dtsx: The connection is not found. This error is thrown by Connections collection when the specific connection element is not found."
The server team swears nothing has changed.ÃÂ I'm at a loss.ÃÂ When I open the package on the server in BIDS, still get same error.ÃÂ I keep having to re-add the connection and save.ÃÂ If I re-open it gives the same errors all over again.ÃÂ All our SSIS packages are stored on the file system, protection-level is "don't save sensitive".
Table entry for this connection is:ÃÂ ConfiguredValue = "Data Source=HQESQL4\HQESQL4;Initial Catalog=ETL temp rep;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto Translate=False;", PackagePath = "\Package.Connections[ETL temp rep 4 Database].Properties[ConnectionString]"
View Complete Post