Connecting to Microsoft Dynamics 365 for Sales Version 9.0


Dynamics NAV 2016 and later versions use a native integration with Dynamics 365 for Sales for a smooth experience. But our friends in the Dynamics 365 for Sales team have announced a new customer-driven update that will be come with version 9.0. The target of this update was to be available before the end of January 2018, which took place already in many regions gradually.

We new from earlier that this might require an update for Dynamics NAV, just as we saw when the platform updated to version 8.2 last year, ass described in an earlier blog post.

If you test if the integration setup would be still valid on the new platform, the first try to test the connection results in the following error:

If you're curious enough, you can debug the code behind the test connection logic and find it breaking on table 5330 in Dynamics NAV 2017:

And then here:

The underlying change is that Dynamics 365 for Sales now requires TLS 1.2, which is not the default in older builds. For more information, see this blog post: TLS 1.2 support at Microsoft

All the detailed investigation and collaboration between the Dynamics 365 for Sales team and we in the Dynamics NAV team persuaded us that we must publish an Out Of Band fix for Dynamics NAV as soon as possible, because we do not want our customers and partners to be waiting until the next cumulative updates.

We're happy to announce that the OOB fixes are finished and tested successfully, and you can proceed and download them directly here:

CRM Online connection failures in NAV 2016 and 2017 after TLS 1.2 update

Dynamics NAV 2016 hotfix links:

Download the NAV 2016 AT package
Download the NAV 2016 AU package
Download the NAV 2016 BE package
Download the NAV 2016 CH package
Download the NAV 2016 CZ package
Download the NAV 2016 DE package
Download the NAV 2016 DK package
Download the NAV 2016 ES package
Download the NAV 2016 FI package
Download the NAV 2016 FR package
Download the NAV 2016 GB package
Download the NAV 2016 IN package
Download the NAV 2016 IS package
Download the NAV 2016 IT package
Download the NAV 2016 NS package
Download the NAV 2016 NL package
Download the NAV 2016 NO package
Download the NAV 2016 NZ package
Download the NAV 2016 RU package
Download the NAV 2016 SE package
Download the NAV 2016 W1 package

Dynamics NAV 2017 hotfix links:

Download the NAV 2017 AT package
Download the NAV 2017 AU package
Download the NAV 2017 BE package
Download the NAV 2017 CH package
Download the NAV 2017 CZ package
Download the NAV 2017 DE package
Download the NAV 2017 DK package
Download the NAV 2017 ES package
Download the NAV 2017 FI package
Download the NAV 2017 FR package
Download the NAV 2017 GB package
Download the NAV 2017 IS package
Download the NAV 2017 IT package
Download the NAV 2017 NA package
Download the NAV 2017 NL package
Download the NAV 2017 NO package
Download the NAV 2017 NZ package
Download the NAV 2017 RU package
Download the NAV 2017 SE package
Download the NAV 2017 W1 package

Dynamics NAV 2018

Dynamics NAV 2018 is not affected by this platform issue, but we suggest deploying latest CU as a best practice. For more information, see Integrating Microsoft Dynamics for Sales in Microsoft Dynamics NAV.

 

These postings are provided "AS IS" with no warranties and confer no rights. You assume all risk for your use.

Abdelrahman Erlebach
Microsoft Dynamics Germany

Duilio Tacconi
Microsoft Dynamics Italy

Jamie Weisenberger
Microsoft Dynamics USA

Special thanks to:
Niels-Henrik Sejthen, Ivan Koletic, Stan Pesotskiy from Microsoft Dynamics NAV Developement Team.
Also special thanks to Gülden Bilgütay from Dynamics CRM Team Germany.

Comments (7)

  1. Peter says:

    Will this also upgrade the Data Exchange Framework to use TLS 1.2 or is it only the CRM integration?

    1. dtacconi says:

      Only CRM Integration related. If you have issue with DEF, please file in a Support Request to CSS – if you have not already done -. 🙂

      1. Peter says:

        I’m unable to setup DES with Tradeshift – it does not work in NAV2017CU14 or older CUs, but it works fine in NAV2018RTM and DevPreview. If nobody reported it already, then apparently nobody uses it.

  2. Jacco Slok says:

    Thank you for this update, this is really helpfull and solved my issue today.

    1. Abdelrahman Erlebach says:

      Thank you for the Feedbacks Jacco, we are always here to help 🙂

  3. Rick says:

    Thanks for this post. Sadly after updating the Server it still doesnt work. Exactly the same message.
    I installed NAV 2018 to exclude any PC issues/firewall/network issues and it works fine there.

    Is there anything I need to do besides reinstalling the server and instances + updating the DLL file? I even updated the Client and im clueless…

    1. Abdelrahman Erlebach says:

      Hi Rick,

      We sugegst always to uninstall before installing the OOB Fix, sometimes copying does not go well, and you end up with a mixture between older and newer files, please do uninstall first, then a clean installation and it will work, we tested it more than once, otherwise feel free to contact the support team via support case.

      Happy to hear from you.

Skip to main content