Sql – SSIS Connection not found in package

sqlsql serverssis

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.

Best Answer

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.

Related Solutions

Sql-server – Cannot Connect to Server – A network-related or instance-specific error

I found the following techniques helpful:

Make sure your database engine is configured to accept remote connections:
- Start > All Programs > SQL Server 2005 > Configuration Tools > SQL Server Surface Area Configuration
- Click on Surface Area Configuration for Services and Connections
- Select the instance that is having a problem > Database Engine > Remote Connections
- Enable local and remote connections
- Restart instance
You may need to create an exception on the firewall for the SQL Server instance and port you are using:
- Start > Run > Firewall.cpl
- Click on exceptions tab
- Add sqlservr.exe (typically located in C:\Program Files (x86)\Microsoft SQL Server\MSSQL.x\MSSQL\Bin, check your installs for the actual folder path) and port (default is 1433)
- Check your connection string as well
- From FIX : ERROR : Could not open a connection to SQL Server:
Check if your SQL server services is up and running properly:
- Go to All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL Server Configuration Manager > SQL Server Services
- Check to make sure SQL Server service status is Running.
In addition, ensure that your remote server is in the same network. Run sqlcmd -L to ascertain if your server is included in your network list.
Enable TCP/IP in SQL Server Configuration

When two or more SQL Servers are connected across network they do all communication using TCP/IP. The default port of SQL Server installation is 1433. This port can be changed through SQL Server Configuration Manager. TCP/IP should be enabled for SQL Server to be connected.
- Go to All Programs >> Microsoft SQL Server 2008 >> Configuration Tools >> SQL Server Configuration Manager >> Select TCP/IP
- Right Click on TCP/IP >> Click on Enable
You must restart SQL Server Services for all the changes to take effect. Right click and go to menu properties to select location where default port of SQL Server can be changed.

Javascript – RequireJS: How to exclude certain paths when building to single file

Setting the paths to "empty:" in my r.js config worked. Example:

// This is a RequireJS config file
(function(){
    return {

        // Name of input file (without the .js extention)
        "name": "main",

        // Directory containing input file
        "baseUrl": "static/",

        // Look in this file for the require.config() call and extract it
        "mainConfigFile": "static/main.js",

        "paths": {
            // Don't attempt to include dependencies whose path begins with webapp/
            "webapp": "empty:",

            // Ditto for the following 3rd-party libraries
            "jquery": "empty:",
            "fuelux": "empty:",
            "backbone": "empty:",
            "underscore": "empty:"
        },

        "optimize": "uglify2",
    };
})()

Best Answer

Related Solutions

Sql-server – Cannot Connect to Server – A network-related or instance-specific error

Javascript – RequireJS: How to exclude certain paths when building to single file

Related Topic