Microsoft Dynamics 365 | Integration, Dataverse...

Error with disabled users

(0) Share

Report

Posted on by Kostas K

Hi to all,

At our organization we have plugins and jobs that can assign records to disabled users. Until now we didn't faced any problems, but between 25/3-27/3, jobs that use this procedure, failed with the following error:

The user with SystemUserId=70257641-0464-ec11-8f8f-6045bd888e84 in OrganizationContext=da01578f-4129-4bf3-8ab0-70c12e7c517b is disabled. Disabled users cannot access the system. Consider enabling this user. Also, users are disabled if they dont have a license assigned to them.

From 27/3 until now, everything works as usual. Did Microsoft changed anything depending on user licenses?

Thank you,

Kostas

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Leah Ju Microsoft Employee on at

Like (1)

Report
Hi Kostas,

Maybe you can try to the following way:

https://www.thrives.be/dynamics-365-ce/assign-security-roles-to-disabled-users-in-dynamics365/

There is an Organization Setting which allows us to assign security roles to Disabled Users. The ‘AllowRoleAssignmentOnDisabledUsers’ setting allows us to assign Security Roles to disabled users.

Download and import the solution in the target CRM environment.

Open the solution through the Advanced Setting in Dynamics 365.

Search for the setting AllowRoleAssignmentOnDisabledUsers and click the Add button.

After clicking Add, click the Edit button.

In the popup screen, change the value to true.

Then you can assign roles to disabled users successfully, then you can assign records to the disables users who have been assigned roles.

Was this reply helpful? Yes No
Kostas K 29 on at

Like (1)

Report

Hello Leah,

Thank you for your answer. After a contact with Microsoft Support I had the following answer:

The behaviour that you have reported seems in fact consistent with a known issue that we have had globally, for which the fix has already been rolled-out worldwide. It might take a few days for it to propagate to every existing DataCenter, but from your description I am assuming it has already been fixed for you as well.

It was a microsoft's bug and now everything works fine

Was this reply helpful? Yes No