10 May’19

Dynamics 365, Dynamics CRMHow to fix connectivity issues between SSDT, Report Authoring Extension and Dynamics 365

Microsoft has mandated TLS1.2 for Dynamics 364 v9.0, which is why we may face issue while connecting to the CRM online instance from visual studio for creating new report via fetch XML. This post will help developer to solve the connectivity issue for connecting with latest Dynamics 365 v9.0 using SQL Server Data Tools and FetchXml Authoring Extension.

Issues:

  • Not able to login Plugin registration tool (keeps popping up for Credentials)

 

 

 

 

 

 

 

 

 

 

  • Not able to see custom entities in Plugin Registration tool
  • Connection to CRM from Custom Web Application and Console fails
  • Able to retrieve data in dataset in Report RDL but unable to preview

 

 

 

 

 

Root Cause:

This issue occurs because of the latest update in the Microsoft TSL(Transport Layer Security) Protocol in SDK assemblies. Microsoft has allowed TSL connection 1.0 and 1.1 for the browsers or client to connect to the CRM org.

The Microsoft TLS 1.0 implementation has no known security issues but because of the potential security vulnerabilities for future downgrade attacks and TSL vulnerabilities, Microsoft has discontinued the support for TLS 1.0 and 1.1 in Microsoft Office 365. Now Microsoft supports only TSL 1.2 or above.

If you are connecting your org with the old version of plugin registration tool , then you may face this issue.

 

What is TSL ?

Transport Layer Security (TLS) is a cryptographic protocol used to establish a secure communications channel between two systems. It is used to authenticate one or both systems, and protect the confidentiality and integrity of information that passes between systems.

 

HOW TO IDENTIFY:

Use fiddler to check the your server request TSL Version.

  • Install fiddler https://www.telerik.com/download/fiddler
  • Go to Fiddler Setup -> Tools -> Options

 

 

 

 

 

  • Click on highlighted text after “Protocols” label and add ;tls1.2 text at the end and click “OK”:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

  • Run the report again. It should work as expected.

This is how we can fix the connectivity issues between SSDT, Report Authoring Extension and Dynamics 365.

Written by

Team Member

CloudFronts

Leave a Reply

Your email address will not be published. Required fields are marked *

Want to streamline your business processes?

  • This field is for validation purposes and should be left unchanged.

Recent Articles

  • Expenses in PSA for Fixed Bid and T&M contracts

    23 August’ 2019

    Problem Definition: One of my clients decided to use Expense module in PSA and to his surprise he could see the amount v...

    Read more
  • Setup Dockers

    23 August’ 2019

    Docker is an independent container platform that enables organizations to seamlessly build, share and run any applicatio...

    Read more
  • Qualify Lead in D365 CE: Select which entity records should be created

    20 August’ 2019

    Wave 2019 Updates brought some really sought-after features. Another one which I would like to bring up is the Lead Qual...

    Read more
  • Early Opt-in for October 2019 Wave 2 Updates

    20 August’ 2019

    August 2, 2019 was when the Wave 2 Updates were to be out. And here we are! By now, you should have gotten the option to...

    Read more
  • Setting Unified Interface App Icons

    20 August’ 2019

    Default App Icons for typical D365 environment look like these.But here’s what you can do to change these to put...

    Read more
  • We respect your privacy.
  • This field is for validation purposes and should be left unchanged.