SSIS Connection not found in package

Question

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 ..

Answer 1

I had same issue in my case, the cause was connection was not embedded and incompatibility of Oracle Client.

SOLUTION:

My Environment:SQL SERVER 2014 64bit Oracle Client 32 bit

1. For include/embed Connection

   • open package
   • right click on connection
   • select "Convert to project" option

2. for SQL SSIS Catalog/Job schedule set the configuration follow steps in picture

   • Right on 'SQL JOB->Step" or "SSIS Catalog-->Package-->Execute" and select "Properties"
   • Select Configuration-->Advanced tab
   • Checked 32-bit runtime

I tried to post detail step by step pictures, but Stack Overflow does not allow that due to reputation. Hope I later will update this post.

Answer 2

It seems that your ssis package is pointing to some other connection which might have been deleted or renamed .Try opening the SSIS compoenents and point to the correct connection which are there in your connection manager .

It happens when we copy the SSIS package components to create a new package or because of renaming the connections or there may be still components which are using the old connection defined in you xml config file( In your case try checking the Execute SQL Task which is throwing error ) .If you are using XML for configuration try deploying the new one.

Answer 3

Package works fine on Friday, check in to TFS and go home. Open it on Monday, getting errors everywhere. "connection manager variable $project._connectionstring was not found in the variables collection".

I rtclick-edit the connection and test connectivity, works no prob;em. The ConnMnger is in the Connection Managers list in the solution. When open the TARGET object connected to this connection manager, and click on MAPPINGS, the error above pops up. There is no reference to connection manager variables anywhere in the mapping.

Turns out, to correct this you must right click on the connection manager in the Connection Manager window and choose PARAMETERIZE. Fill in the options as necessar -

PROPERTY: ConnectionString Use Exisgint Parameter: $Project::ConnMgrName_ConnectionString OR Create New PArameter: follow the options

Once this connection manager is parameterized, everything works. Even though the Conn Manger existed in the Conn Manger tab, the Conn Mgr is already listed in the Solution Explorer AND worked no problem 2 days prior.

Odd. Whatever. Microsoft being Microsoft. SQL Server being SQL Server. Choose your poison.

Hope this helps the next person save some time.

Answer 4

In my case i found out that the problem was a Log Provider previously configured point to an old connection not used anymore. To solve the problem click the Package Explorer Tab then click Log Providers and delete the outdated Log Provider. I hope this helps someone.

Answer 5

In my case, one of the event handler task was pointing to old connection which was deleted, deleting the unused event handler task fixed the problem. I end up opening the package in XML format to understand that the problem is with event handler task!

Answer 6

I had the same problem.

I use project level connection managers and my packages run correctly in SSDT but when I deployed them and execute them through a job with sql server agent, I get "Connection not found" errors.

So I deploy the project and then the problem was solved, when you use project level connection managers but just deploy a single package from that project, and you call package through sql server agent, it could not recognize your connection managers so you should determine package level connection managers or you should first deploy your project.