Customer experience | Sales, Customer Insights,...

Software Developer Toolkit and deprecation of the Regional Discovery service

(1) Share

Report

Posted on by Ben Walker

The software developer toolkit (https://marketplace.visualstudio.com/items?itemName=DynamicsCRMPG.MicrosoftDynamicsCRMDeveloperToolkit) has stopped working for us today due to the deprecation of the Regional Discovery Service. We get the error FCB 'EnableRegionalDisco' is disabled when trying to connect to any Dynamics 365 online instances.

I know the product has never made it out of public preview, so I can't expect any official support for this, but if anyone has any ideas as to how to get round this problem, let me know. I've downloaded the latest copy of the DevTools and replaced everything in the Bin and PluginRegistration folders with the latest versions from the DevTools download, but it's made no difference.

Any suggestions gratefully received....

Thanks,

Ben

I have the same question (0)

All responses (20)

Answers (0)

Suggested answer

davidrcapgemini 10 on at

Like (1)

Report
Hello Ben,

The issue (so I'm told) is with the previous version of the core assemblies and connecting using Office 365 authentication which I think means it still tries to authenticate regionally.

There are 2 fixes worth exploring:

update core assemblies package to the latest version

if possible for connections use OAuth

and 1 interim workaround:

Microsoft I'm told are extending the removal of this if requested.

I'm also testing some of this stuff, will let you know how it goes

Was this reply helpful? Yes No
Suggested answer

davidrcapgemini 10 on at

Like (0)

Report

www.threegreymonkeys.com/.../ found this article, tried the short term fix and it is working

Was this reply helpful? Yes No
Ben Walker 22 on at

Like (0)

Report

Hi David, thanks for the replies.

I tried using the latest version of the core assemblies and it hasn't helped.

I have no problem connecting to my instance of CRM using the SDK in general, but the software developer toolkit does not allow you to enter a connection string by hand, so no way to add the 'skipdiscovery' argument.

You just a get a dialogue box like this:

and there's no way to amend the connection string which is used.
Let me know if I've misunderstood - if you've managed to get the software developer toolkit working with D365 online since the deprecation of the global discover service, do let me know.

Thanks again,

Ben

Was this reply helpful? Yes No
Suggested answer

meelamri 13,216 User Group Leader on at

Like (0)

Report

Hello Ben,

I have been looking for a solution to this problem for a few days. I think I can hold some things...

Below is a screenshot of the issue:

After replacing the dll files in the folder of the extension. I can connect to the CRM using the Global Discovery. The new dll files are from tha latest SDK version..

Result:

I thought I could solve the problem...unfortunately not! Indeed, I receive the following error at the time of deployment:

Could not load file or assembly ''CrmLibraries, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 or one of its dependencies. The located assembly's manifest definition does not match the assembly reference.

After copying also the CrmLibrairies dll. I got the same error while connecting to the CRM:

I am still in the process of finding the solution to the problem. I would like to share my current progress though.

Was this reply helpful? Yes No
Ben Walker 22 on at

Like (0)

Report

Thanks for the update Mehdi, interesting that you are at least able to connect. I'm surprised that it's giving you that v8 assembly reference when you try and deploy. Let me know if you manage to get any further....

Was this reply helpful? Yes No
meelamri 13,216 User Group Leader on at

Like (0)

Report

Hi,

Could you please test the same procedure I shared on my previous post? Thank you

Was this reply helpful? Yes No
Ben Walker 22 on at

Like (0)

Report

After I replace those files in the extensions folder I now get this message when I try and connect the CRM Explorer:

I'll keep investigating....

Was this reply helpful? Yes No
Suggested answer

meelamri 13,216 User Group Leader on at

Like (1)

Report

Hello Ben,

I have some good news. I managed to connect the tool to the CRM and deploy my plugins..

I explain all the details on my blog: xrmtricks.com/.../

I wish you good luck !!

Was this reply helpful? Yes No
Ben Walker 22 on at

Like (0)

Report

That's great news Mehdi, I'll follow your instructions later today and feed back here. Fingers crossed!

Was this reply helpful? Yes No
Jupek 5 on at

Like (0)

Report

Thanks for the blog Mehdi. That worked. One addition though based on my tests using this method. I had to copy also Microsoft.Rest.ClientRuntime.dll to the extension folder to be able login succesfully with legacy VS 2015.

Without that I could see on the logs this error during login:

Could not load file or assembly 'Microsoft.Rest.ClientRuntime, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

Stack Trace : at Microsoft.Xrm.Tooling.Connector.CrmWebSvc.<ExecuteHttpRequestAsync>d__146.MoveNext()

Maybe this is not the problem with newer Visual Studios or I missed some configuration.

Was this reply helpful? Yes No