CRM Integration Requires Updated SDK File

If you use our integration with Dynamics CRM, you might have noticed a Microsoft.Xrm.Sdk.dll that is installed on the server and on the client computers. This is part of the integration, both when you use the integrated connection and the Connector.

We have seen a pattern where this file is the wrong version for some reason. A symptom of this is that you see an error with the cryptic message "Metadata contains a reference that cannot be resolved." This error displays when you set up the integration, and the solution is to update the Microsoft.Xrm.Sdk.dll file.

You can get the right version by downloading the Microsoft Dynamics CRM 2015 SDK, unpack the  download package, and then copy Microsoft.Xrm.Sdk.dll to the following locations:

  • C:\Program Files\Microsoft Dynamics NAV\90\Service\
  • C:\Program Files (x86)\Microsoft Dynamics NAV\90\RoleTailored Client\

If you use the Connector, you must also update Microsoft.Xrm.Sdk.dll in that folder.

As stated above, if your Dynamics NAV solution has this issue, you will see the error message when you first set up the integration with Dynamics CRM. In other words, if you didn't see the error at that point in time, then there is no action for you, and the integration with Dynamics CRM will continue to work as before.

Comments (11)

  1. Guna Kanagatnam says:

    Still I’m getting the same error when tried integrate with NAV 2016 and CRM2016 On premise. please find the error message below,

    Microsoft Dynamics NAV

    The connection setup cannot be validated. Verify the settings and try again.
    Detailed error description: Metadata contains a reference that cannot be resolved: ‘’..


  2. Arthur says:

    Similar here, replaced Microsoft.Xrm.Sdk.dll from CRM 2015 SDK to both NAV folders, the new Microsoft.Xrm.Sdk.dll is several KB larger than the original in NAV folders. Still have the message: Validation Results
    The connection setup cannot be validated. Verify the settings and try again.
    Detailed error description: Metadata contains a reference that cannot be resolved: ‘’..

  3. That error message might have been caused from several reasons.
    We need to investigate from the NAV and the CRM side that everything is set up properly.
    Please open a Service Request to proceed with the investigation. If the issue is related to a bug, then the case will be archived as free of charge at the end.

  4. Guna Kanagatnam says:

    CRM2015(on premise with IFD) and NAV2016 integration just work fine.


  5. Samuel says:

    Hello Guna, Have you been able to solve the problem. I have tried the CRM 2016 SDK file. After copying to my NAV and CRM folder, The Nav Server shuts down repeatedly when I try to enable the connection. Please i would appreciate any help

    1. Sokratis Papachristos says:

      Dear Samuel,
      The workaround described above, describes how to update the proper dlls on the NAV side.(no need to update your CRM files)
      Please revert your files as they were before and update the dlls as described on the above file paths.
      If the issue persists, please create a Service Request to proceed with proper investigation.
      Best Regards

      1. Samuel says:

        Thank you Sokratis, I reversed the integration and started from scratch, no longer shutting down when I use SDK 2015. however, the integration isn’t working. I hope it isn’t because it’s on-premise

  6. Samuel says:

    Hi everyone,
    I get this error on CRM 2016 IFD and NAV 2016
    “an attempt was made to change an old version of a crm connection setup record. the record should first be reread from the database. this is a programming error. identification fields and values: primary key=” “

  7. RV Anandan says:

    I got the same issue today while trying to setup NAV 2016 (on-premise) Connector to Dynamics 365 Sales Online instance. Tried to resolve by replacing DLL’s.. No success…

  8. Quenneth Surban says:

    I’m still getting the same error. How do I resolve this and connect to NAV and CRM?

    1. Pallea says:

      Comon guys.. You are commenting on a blog text that is 11 months old..and there are at least 10 new releases after this one.

      You can get help on either Partnersource,, mibuso or microsoft Customer or partnersource website.

Skip to main content