Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

SSIS Connection not found in package

I'm kind of new to SSIS programming, and I'm having some problems deploying an SSIS package.

This package runs correctly on my PC, does everything it needs to do ... but when I deploy it cannot find the connection strings.

Here is the error:

Code: 0xC001000E Source: Description: The connection "{DA7CD38D-F6AA-4B06-8014-58BEE5684364}" is not found. This error is thrown by Connections collection when the specific connection element is not found. End Error

Error: 2012-08-09 00:21:06.25 Code: 0xC001000E Source: Package Description: The connection "{DA7CD38D-F6AA-4B06-8014-58BEE5684364}" is not found. This error is thrown by Connections collection when the specific connection element is not found. End Error

Error: 2012-08-09 00:21:06.25 Code: 0xC001000E Source: Package Description: The connection "{DA7CD38D-F6AA-4B06-8014-58BEE5684364}" is not found. This error is thrown by Connections collection when the specific connection element is not found. End Error

Error: 2012-08-09 00:21:06.25 Code: 0xC00291EB Source: Execute SQL Task Execute SQL Task Description: Connection manager "{DA7CD38D-F6AA-4B06-8014-58BEE5684364}" does not exist. End Error

Error: 2012-08-09 00:21:06.25 Code: 0xC0024107 Source: Execute SQL Task Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 00:21:04 Finished: 00:21:06 Elapsed: 1.888 seconds. The package execution failed. The step failed.

like image 433
Schewns Avatar asked Aug 08 '12 23:08

Schewns


People also ask

How do I find the connection manager in SSIS?

In SQL Server Data Tools (SSDT), open the Integration Services project. In Solution Explorer, right-click Connection Managers, and click New Connection Manager. In the Add SSIS Connection Manager dialog box, select the type of connection manager, and then click Add.


1 Answers

I'm a little late to the party, but I ran across this thread while experiencing the same errors and found a different resolution.

When creating an SSIS 2012 package, in the Solution Explorer window you will see the Connection Managers folder at the project level. This seems like the most logical place to create a connection, and should be used when creating a connection that can be used by any package in the project. It is included at the project level, and not the package level.

When running my dtsx package using dtexec, I received the same errors shown above. This is because the connection is not included in the package (just the project). My solution was to go into the package designer, and then in the Connection Manager window, right click the project level connection (which is shown using the "(project)" prefix) and choose "Convert to Package Connection". This will embed the connection in the actual dtsx package. This alleviated my problem.

like image 196
jhughes Avatar answered Sep 22 '22 11:09

jhughes