Why is my SSIS package failing after upgrading windows 2008 R2 to 2012R2

IT LOG 1 Reputation point
2020-12-22T16:47:47.377+00:00

Just recently updated a web server that was running on Windows Server 2008R2 to Windows Server 2012R2.

Everything in the IIS/website seems to be still running perfectly fine, apart from the uploading of .ACCDB files to a SQL server via a SSIS package.

the package is throwing up an error with the below;

SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "sampleconnection" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.

any ideas ?

Visual Studio
Visual Studio
A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.
4,581 questions
SQL Server Integration Services
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,451 questions

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Michael Taylor 47,716 Reputation points
    2020-12-22T17:01:53.507+00:00

    Is it an HTTPS site? Are you configured to use only TLS 1.2? If so then SSIS won't work properly without a registry change to have its .NET 4 runtime enable the newer TLS protocol as documented here.

    What happens when you use the connection manager to test the call?

    If not done already then create a script task that uses the connection and calls AcquireConnection. Wrap that in a try-catch and capture the actual error coming out.

    Also make sure that any firewall rules allows communication with the new web server you set up.

    0 comments
  2. Monalv-MSFT 5,891 Reputation points
    2020-12-23T01:41:43.467+00:00

    Hi @IT LOG ,

    SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "sampleconnection" failed with error code 0xC0202009.

    1. May I know if you can share the components in your ssis package?
    2. Could you please check if the connection manager "sampleconnection" exists?
      If it exists, then please check if you set the connection manager correctly.
    3. Please check the value of Run64BitRunTime and then set it to the opposite value(True->False or False->True).
      If we set Run64BitRunTime as False will find and use the 32 bit provider;
      If we set Run64BitRunTime as True will find and use the 64 bit provider.
      Please refer to Using SSIS (SQL Server Integration Services) with a properly configured Informix OLEDB driver may yield SSIS Error Code 0xC0202009.

    Best Regards,
    Mona

    ----------

    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
    Hot issues in November--What can I do if my transaction log is full?
    Hot issues in November--How to convert Profiler trace into a SQL Server table?