You’re offline. This is a read only version of the page.
Hi There,
We're experiencing an issue currently with enabling TLS 1.2 in Dynamics CRM 2011 on premise and specifically with our asynchronous servers.
We have some workflows that make calls to an external API which has now forced TLS 1.2 on it. We've made the suggested change to the registry on the asynchronous servers and the CRM web application server, but the calls are still failing due to incorrect TLS. Has anyone else experienced this issue and is there a different procedure for enabling it on the asynchronous servers as opposed to the web servers?
Many thanks
Dan
*This post is locked for comments
I have the same question (0)
I have searched for this issue but most of time changing .Net Framework 4.6.2+ solved most of problems but I think some services or workflows still using old framework that might be reason for incorrect TLS. You can use following links they are useful to understand TLS issues.
https://support.microsoft.com/en-us/help/4051700
cloudblogs.microsoft.com/.../tls-1-2-support-at-microsoft
https://www.microsoft.com/en-us/download/details.aspx?id=55266
www.crminnovation.com/.../tls-transport-layer-security-wake-call
Share
Report
All responses (
Answers (
4
