Loading...

Resolving User Not Licensed Errors When Saving A Row (Microsoft Dataverse)

Resolving User Not Licensed Errors When Saving A Row (Microsoft Dataverse)
Featured image of post Resolving User Not Licensed Errors When Saving A Row (Microsoft Dataverse)

When working with the Microsoft Dataverse platform, you sometimes get presented with error messages in the strangest circumstances. Take, for example, a recent scenario where we were getting the following error message whenever we attempted to save a Case row within Dynamics 365 Customer Service:

The user with SystemUserId=1e18d5cd-72a6-462a-98ab-eb76b1f17b79 in OrganizationContext=e1c03efe-c3a0-4a35-9ed7-05f49ab97918 is not licensed, and its SystemUserAccessMode=0 is not either of (NonInteractive=4, SetupUser=1)

The error would fire against any operation we targeted against the table - such as saving a row or executing a plug-in that performed some action against the table. A close reading of this error would suggest that something is going on as part of the transaction invoking the context of a user that is no longer active within the environment. The joys of inheriting a system from another project. 😉 We checked a few things in the first instance on any plug-ins registered on the Case table:

  • The value of the Run in User’s Context setting on all appropriate plug-in steps to ensure that the original developer hadn’t put it to the disabled user.
  • Verified that the code wasn’t impersonating the user in question.

Finally, as a punt, we noticed that the table had several real-time workflows executing against it. We decided to deactivate all of these workflows and then re-activate them, working on the assumption that something had been cached relating to the disabled user. This was despite the fact that another active service account owned the workflows. Doing this resolved the issue, and much to our surprise, the error no longer appeared.

I must say, this is the strangest Dataverse platform error I have faced for a while, and I’m still not 100% sure why the steps we followed resolved the issue. Answers on a postcard below if you can share any insights, but I hope this proves helpful if you encounter the same problem yourself in the future.

Published on:

Learn more
The CRM Chap
The CRM Chap

Anything and everything to do with the #PowerPlatform, #MSDYN365, #Azure and more!

Share post:

Related posts

Power Platform – Coauthoring within the Canvas Designer announcement

The public preview of a new coauthoring feature within Canvas Designer has been announced, allowing multiple makers to collaborate in real-tim...

1 day ago

Power Platform admin center – Updated Tenant settings feature announcement

Administrators of the Power Platform take note: an updated version of the Tenant settings feature for the Power Platform admin center (PPAC) w...

2 days ago

Power Platform admin center – The ‘Created by’ column information on the Environments page is being moved

Important changes are coming to the Power Platform admin center (PPAC). Specifically, the ‘Created by’ column on the Environments page is bein...

4 days ago

Set up telemetry monitoring using enhanced data model | Power Platform Shorts

This video is a tutorial on how to set up telemetry monitoring using an enhanced data model using Power Platform Shorts. If you're looking to ...

4 days ago

Boosting Developer Efficiency with Power Platform Innovations

Join this video session to learn about Power Platform innovations that help developers maximize their efficiency. You'll be introduced to the ...

4 days ago

Build intelligent and scalable solutions with Microsoft Power Apps and Microsoft Power Platform 

In this blog post and the accompanying demo video, we want to highlight what is possible with Microsoft Power Apps and Microsoft Power Platfor...

8 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy