microsoft dynamics crm invalid user authorization

Up your game with a learning path tailored to todays Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.

In CRM 2011 instance, there were some workflows that were using custom workflow activities.

I couldnt find the exact cause of this issue, and it turns out I am not the only one affected by this issue.

In this blog, I will walk through the steps that helped me to overcome this issue.

After the backup solution has been exported, delete the workflows that are using custom workflow activities.

Unregister the custom workflow activities that were added during CRM 2011 to Dynamics 365 upgrade.

Import the backup solution of the workflows that was exported earlier (at step 2).

This error generally appears for Dynamics 365 on-prem more then online.

Depending on the situation, this error might appear sometimes or all the time while browsing the site.

Below is a list of fixes I have done for different scenarios to get me pass this, hopefully its helpful for someone.

Strangely a quick iisreset or server reboot fixes the problem.

They were trying to access the installer by launching Dynamics 365 in the browser, clicking the gear icon in the top right corner and going clicking on Apps for dynamics 365.

At that point, they would be greeted with the error, it happened on all accounts.

After enabling data encryption by going to Settings Data Management Data Encryption, the error went away.

While installing the 8.2.0.749 (KB3205084) patch, it said it completed successfully but if I viewed the logs, there was actually some SQL errors during the database upgrade.

It looked like this left the CRM organization in some sort of limbo state.

Whenever I tried to access CRM, I would be instantly greeted with the Invalid User Authorization error.

The one thing I did notice was that in deployment manager, the organization build version was incorrect.

Deleting and re-importing the org from deployment manager didnt work.

The only solution was to restore the SQL backup (you made one of these before the upgrade right) and re-import the organization and re-do the database upgrade.

It was a huge hassle but I was two days out investigating the issue with a quickly approaching deadline, and the SQL restorere-import would of been done in a lot less time.

Microsoft Dynamics Crm Invalid User Authorization