Microsoft.XRM.SDK.dll Upgrade.

(0) Share

Report

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

I have the same question (0)

All responses (14)

Answers (0)

Suggested answer

MattB-MSFT on at

Like (0)

Report

You do not need to update your plugin's they are already taken care of on the server.

You will get this if we detect you using a Service Endpoint that is configured for ACS Auth or your using an SDK Client to connect to CRM using older versions of the Microsoft.Xrm.SDK.dll ( think SDK Clients here / external apps ).

if you have those, it could be as simple as replacing the Microsoft.Xrm.SDK.dll with the version from the 8.2.x SDK.

Was this reply helpful? Yes No
Anne Pessoa 14 on at

Like (0)

Report

Hi Matt,

I got the same alert as Deepak and we have CRM 2016 Online and ADX Studio (V7) which makes uses for the Microsoft.Xrm.Client, we are updating the Microsoft.Xrm.Sdk.dll to the latest one, but do we need to remove the Microsoft.Xrm.Client?

Removing the Microsoft.Xrm.Client generates loads of errors in our ADX solution.. If we just add the Microsoft.Xrm.Tooling.Connector and use the CrmServiceClient to connect to CRM, and keep using the Microsoft.Xrm.Client for other actions like caching (Microsoft.Xrm.Client.Caching.ObjectCacheManager) or GetRelatedEntities, will we be ok on the 01/07 (day after the service update)?

I know we probably will need to remove the Microsoft.Xrm.Client for the Dynamics 365 upgrade, but we will then be able to apply in DEV first and work from there.

Thanks alot!!!

Was this reply helpful? Yes No
MattB-MSFT on at

Like (0)

Report

You do not need to remove the Xrm.Client from ADX 7.x deployments ( its not supported by product any longer but that application predates it and the updated SDK will not harm it )

Was this reply helpful? Yes No
Anne Pessoa 14 on at

Like (0)

Report

Thanks Matt!

Was this reply helpful? Yes No
Lukasz Kowalski-Gli... on at

Like (0)

Report

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?

Was this reply helpful? Yes No
Suggested answer

prt33k 6,907 on at

Like (0)

Report

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.

Was this reply helpful? Yes No
Lukasz Kowalski-Gli... on at

Like (0)

Report

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.

Was this reply helpful? Yes No
prt33k 6,907 on at

Like (0)

Report

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...

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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

Was this reply helpful? Yes No
Anne Pessoa 14 on at

Like (0)

Report

Hi, do you use outlook maybe?

Was this reply helpful? Yes No