TLS Issue with SSIS package while accessing OData Source like Dynamics AX Online

This post has been republished via RSS; it originally appeared at: SQL Server Support articles.

First published on MSDN on Jan 16, 2018


I have come across an interesting scenario recently while working on one of the customer issues. The SSIS package fails during the execution, even though the Test Connection and Preview Data in the OData Source Task succeeds while connecting to the Dynamics AX OData Source.

Here is the error message we got:

[OData Source [2]] Error: Cannot acquire a managed connection from the run-time connection manager.

[SSIS.Pipeline] Error: OData Source failed validation and returned error code 0xC020801F .



Let me give you a quick background of the issue. The SSIS 2014 Package fails during the execution while connecting to Dynamics AX Online OData Source with the below error:



The Fiddler trace looks like below





You can clearly see that HTTPS Handshake failed while trying to access the OData Source URL.



We can resolve this using the below steps:

1. Install Microsoft .NET 4.6 and above on your computer ( https://technet.microsoft.com/en-us/library/security/2960358.aspx ).


2. Enforce TLS 1.2 on your machine through registry settings. In an elevated command prompt run the following commands:

• reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v SchUseStrongCrypto /t REG_DWORD /d 1 /reg:64


• reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v SchUseStrongCrypto /t REG_DWORD /d 1 /reg:32

If you have performed the above action plan and you are still experiencing the issue, then please contact the Microsoft CSS team for further investigation.



Author: Mounika Narayana Reddy – Support Engineer, SQL Server BI Developer team, Microsoft

Reviewer: Krishnakumar Rukmangathan – Support Escalation Engineer, SQL Server BI Developer team, Microsoft