SSIS Package failing with "Failed to acquire connection" error

We have an SSIS package that is launched from a web service. In the Dev environment, everything works fine, but in the QA environment I get the following error when trying to run the package: "Failed to acquire connection [ConnectionName]. Connection may not be configured c开发者_Python百科orrectly or you may not have the right permissions on this connection."

The connection uses SQL login, not integrated. The login itself has the appropriate privileges. The SSIS package is located on the file system, not on SQL server. I've used DTCPing and everything checks out fine between the SQL server and the Utility server. Unfortunately I know very little about SSIS itself, and am a bit of a loss as to what could be the problem. Any suggestions would be greatly appreciated.

I finally resolved the problem and it was related to my MSDTC settings. While MSDTC had been enabled, I had to enable the following settings:

• Network DTC Access
• Allow Remote Client
• Allow Inbound/Outbound
• Enable TIP

When using a "foreach loop" Container in a SSIS package, we had this error after processing 3K+ files... By setting the connection property RetainSameConnection to TRUE, we were able to move more than 32K files with no further issues.

I had a similar issue. I was setting up a job to execute a SSIS package that I previously added to the SSIS catalogue on that server.

I solved it by going to the Job Step > Configuration > Connection Managers> For each connection I had to specify the Password and set RetainSameConnection = True.

I'm not sure that the RetainSameConnection is necesarry

I had a similar issue, but it was my own human error (tough week). I copy/pasted the Connections Strings into the Description column instead of the Value column in the Environment Properties. After moving them to the right (Value) column, my issue (naturally) had been solved.

In our project scenario, windows service complied as 32 bit version but the package was designed with 64 bit version.

on deployment server, when windows service runs expects to have 32 bit library in GAC which was not installed. After investigation 64 bit installed only.

When windows service run, mentioned error comes up.

Possible solution is to complied the windows service into 64 bit only and verify.

Hope this finding may help you.

Happy programming.