CODEWITHSUNDEEP
c#asp.netvisual-studiodynamics-crm-2011dynamics-crm-2016
Alex Gordon
Alex Gordon

Reputation: 60691

Upgrading Dynamics CRM from 2011 to 2016

With little knowledge of CRM, we were tasked with exposing data and other functionality from CRM 2011. We developed a RESTful wrapper that allows other developers to leverage it in their apps. Some example endpoints might have been:

API/v2/Accounts(someguid)
API/v2/Lead/Create {json object}
etc

This application needs to be upgraded to support dynamics 2016. We fired up our 2011 app, and simply changed a config variable to point to a 2016 instance. So far we haven't been able to do anything because right after the second line below:

        var context = new XrmServiceContext(_organizationService);

        var crmUser = (from systemUser in context.SystemUserSet
                       where systemUser.DomainName == user.DomainUserName
                       select systemUser).FirstOrDefault();

I get authentication failed exceptions:

enter image description here

Is this indeed a known authentication issue when upgrading from 11 to 16, or am I missing something?

Upvotes: 6

Views: 346

Answers (1)

Daryl
Daryl

Reputation: 18895

There have been countless Authenticate Changes between CRM 2011 and 2016. The SDK should handle all of these issues for you, fairly seamlessly.

Download the latest version from https://www.microsoft.com/en-us/download/details.aspx?id=50032, and update any of Microsoft.Xrm.* dlls that you are referencing in your project.

If you're using Nuget, you could add these instead:

  • Microsoft.CrmSdk.Extensions (7.1.0.1 - this contains the older connection method to CRM. It will be going away, but for now, is still compatible)
  • Microsoft.CrmSdk.Deployment (8.2.0.2)
  • Microsoft.CrmSdk.Workflow (8.2.0.0) --> This one should actually be optional.

Once you've updated your references, rebuild, and retry.

Upvotes: 4

Related Questions