Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Microsoft.XRM.SDK.dll ...
Microsoft Dynamics CRM (Archived)

Microsoft.XRM.SDK.dll Upgrade.

(0) ShareShare
ReportReport
Posted on by Deepak Jangra 1,415

Hi All,

I need some help from you all that we are using Dynamics CRM 2016 Update 8.1 and received a mail from the Microsoft contains below message:

We have detected an issue on your CRM online instance that we need your help to resolve. This may help improve your organization's CRM Online service performance and overall experience.


Description of the issue: Access Control Service shutdown

and reason i think is below

  • If you are using Microsoft.XRM.SDK.dll either through a custom application, custom portal, or a third-party product (ADX Studio, AttachmentExtractor, Scribe, KingswaySoft, custom SSIS connector, etc.) 

So i need to update Microsoft.XRM.SDK.dll to newer version but my query is suppose if i update the dll in my visual studio project and then update the assembly and all the steps using plugin registration tool in development instance and after that if i make a managed solution with assembly only and publish that to production instance then that approach will fix that issue or not. Or i need to follow some other approach to update sdk dll on production instance to fix the issue.

Thanks 

Deepak

*This post is locked for comments

  • Suggested answer
    MattB-MSFT Profile Picture
    MattB-MSFT on at
    RE: Microsoft.XRM.SDK.dll Upgrade.

    The steps for doing that are covered in this blog post: blogs.msdn.microsoft.com/.../update-dynamics-crm-client-sdk-version-to-avoid-calls-to-acs

  • MSCRM learner Profile Picture
    MSCRM learner 170 on at
    RE: Microsoft.XRM.SDK.dll Upgrade.

    Thank you so much MattB-MSFT.

    In your comment, in the last paragraph, it suggests that it is not required to update the build (means solution here) but need to update only the Microsoft.Xrm.SDK.DLL at client side. Please let me know if I understood it correctly or not. Also please let me know at which place I need to update the dll.

    Also I want to know how to handle this thing in terms of online CRM instance. i.e. updating of the sdk dlls.

    Thanks in advance

  • Suggested answer
    MattB-MSFT Profile Picture
    MattB-MSFT on at
    RE: Microsoft.XRM.SDK.dll Upgrade.

    When you build a plugin, you are creating a reference to the Microsoft.Xrm.SDK.dll (that is impacted by this change), your plugins do not directly include those assemblies, they just refer to them.  We handle the correct mapping based on the server version.  

    You do not need different builds for each server, you should build your plugins using the oldest version of the assemblies that you want to support. 

    Now, in the case of building clients ( anything that connects to the platform from the outside ), you should use the most current SDK's available.  In this case, we are requiring folks to update the Microsoft.Xrm.SDK.DLL to pick up the new authentication and security components.

    MattB.

  • MSCRM learner Profile Picture
    MSCRM learner 170 on at
    RE: Microsoft.XRM.SDK.dll Upgrade.

    Hi MattB-MSFT, prt33k,

    Continued to the discussion of upgrading dlls in C# plugin and then the plugin is referred in CRM solution, I have a question.  

    I already have lots of customers having installed CRM solution which I need to upgrade now for the C# plugin (updating dll to 8.2). So it is required to update the MSCRM solution at one place and then import the upgrade solution to all the customers so that all of them will then have the latest SDK dll in the plugin in the solution. 

    But is this the correct way ? I doubt.

    As you both said "You do not need to update your plugin's  they are already taken care of on the server.".  In my case the CRM servers are different as per the different customers so do I need to follow the process above (highlighted in bold ) or is there any other way to handle this ?

    Thanks in advance.

  • Anne Pessoa Profile Picture
    Anne Pessoa on at
    RE: Microsoft.XRM.SDK.dll Upgrade.

    Hi, do you use outlook maybe?

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Microsoft.XRM.SDK.dll Upgrade.

    As a follow up to this question, we are getting a similar message and cannot seem to find what is using an old version of the Microsoft.Xrm.SDK.DLL  file. Microsoft is telling us that certain users in CRM are accessing versions 7.1.0000.0000 and 7.1.1.1095, but none of our integrations (for example we use Scribe to transfer data from our main database to CRM in a daily integration) are using these versions of the DLL file - we can't seem to track where it might be. Any suggestions?

    Thanks!

    Bryan

  • prt33k Profile Picture
    prt33k 6,907 on at
    RE: Microsoft.XRM.SDK.dll Upgrade.

    Existing code will work however the reference need to be update (as per point 2 and the link you shared)

    Yes, I did that is one of our component which uses the old DLL - changing reference made it work :)

    I do agree that there is work involved in upgrading the code but the current CrmServiceClient is more mature in sense on connectionString. The connectionstring should have the authentication like we have in SQL connectionstring.

    Though no doubt it was easier...

  • Lukasz Kowalski-Glikman Profile Picture
    Lukasz Kowalski-Gli... on at
    RE: Microsoft.XRM.SDK.dll Upgrade.

    Thank @prt33k

    Just to clarify:

    1. Plugins will still work no matter what

    2. Xrm.Client will keep working, at least until MS decides to shut down the CRM 2011 endpoint (*)

    3. "Existing code will work." Are you sure? That's not what I understood from here: blogs.msdn.microsoft.com/.../dynamics-365-sdk-backwards-compatibility

    Additional question - do you know any way to actually test this? Or is it just wait for shutdown and pray it works...?

    ----

    * I understand the need to switch to CrmServiceClient, but that involves code modifications, which is not always easy in legacy applications. Also (at least in the past) it had issues with IFD authentication under some scenarios and isn't as nice as the old CrmConnection as to figure out the CRM type on it's own - you have to specify it (AD, IFD, Online, etc.) ..  which is kind of a step back. In CrmConnection you just provided the URL, user name, password and didn't need to worry about anything.

  • Suggested answer
    prt33k Profile Picture
    prt33k 6,907 on at
    RE: Microsoft.XRM.SDK.dll Upgrade.

    1. Yes, Plugin are run at server so the reference are taken care of.

    2. Any external application - you need to change the references of dll. No need to change code, that will work.

    3. No, Existing code will work.

    4. Xrm.Client is no longer being shipped with SDK. Also CrmServiceClient can transition from SOAP to WebAPI and also support new feature. So better to move to CrmServiceClient.

  • Lukasz Kowalski-Glikman Profile Picture
    Lukasz Kowalski-Gli... on at
    RE: Microsoft.XRM.SDK.dll Upgrade.

    Hi @MattB-MSFT,

    Since you seem to be informed, could you please answer the following questions:

    1. Will all plugins continue to work? Even if they were build against the CRM 2011 SDK.

    2. Suppose I have an external application using the CRM 2013 SDK. Do I only need to update the Microsoft.Xrm.Sdk.dll assembly? Will connections obtained using the  CrmConnection class in Microsoft.Xrm.Client.dll keep working or do I need to modify the code using Microsoft.Xrm.Tooling.*.dll?

    3. Everything using the CRM 2015 SDK needs to be updated to the latest Dynamics 365 SDK?

    4. In case 3. - can I keep using the CrmConnection class in Microsoft.Xrm.Client.dll or do I need to switch to Microsoft.Xrm.Tooling.*.dll?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Tip: Become a User Group leader!

Join the ranks of valued community UG leaders

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,321 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans