Error Code: 2147746581 - new user set up

(0) Share

Report

Posted on by LeeD

I've set up a new user. They are getting this when trying to log in:

Error Code: 2147746581

Session Id: 5e5fefc8-b554-431b-af1e-255044cb4f7b

Timestamp: Wed Jun 28 2023 10:57:10 GMT+0100 (British Summer Time)

RetrieveUserContext: Cannot read properties of undefined (reading 'guid')
TypeError: Cannot read properties of undefined (reading 'guid') at https://content.powerapps.com/resource/uci-infra/scripts/app.f6c56afdc1bd3add6b950f2d41c9f351.js:14:852187 at async Object.boot (https://content.powerapps.com/resource/uci-infra/scripts/app.f6c56afdc1bd3add6b950f2d41c9f351.js:14:849306)

I have checked their roles, security etc which matches another existing member of the same team. I've also ran the diagnostic on the power platform:

Results + fixes

 This user is allowed to sign in.

 This user has an active license or the environment has per app plans.

 This user is a member of the environment's group.

I've tried researching but I cannot find the same issue online. The only mention of the same error code (but different reason) is this https://powerusers.microsoft.com/t5/Microsoft-Dataverse/App-Access-issue/td-p/1295433

Any advice on where to look/update etc?

Thanks

Lee

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (11)

Answers (1)

Drew Poggemann 9,287 Most Valuable Professional on at

Like (0)

Report

Hi @LD_Spotlight ,

I know this is probably something you have tried but have the user clear their cache in the browser or use an incognito window to login and access the application to see if that fixes it.

Was this reply helpful? Yes No
LeeD 18 on at

Like (0)

Report

Hi Drew

Yes and the above message appears.

Cheers

Was this reply helpful? Yes No
Drew Poggemann 9,287 Most Valuable Professional on at

Like (1)

Report
Hi @LD_Spotlight

You appear to have checked the logical things I would check. I would try the following and if it doesn't work then open a ticket with Microsoft:

Try a different computer

Check to see if any conditional access policies are in place that could stop the user (i.e. not a managed endpoint or something)

You could try "Level Up for Dynamics 365" chrome extension and try impersonating the user to see if that works

Was this reply helpful? Yes No
LeeD 18 on at

Like (0)

Report

Thanks @dpoggemann

I'll give that a try and let you know.

Thanks again
Lee

Was this reply helpful? Yes No
gamgoumy 2 on at

Like (0)

Report

I just had this issue. When I made the team in Dynamics, I set the AD Security Group then I set the Membership type to Owner. It should have been Members and Guests. Deleting and recreating the team as Member and Guests resolved the issue

Was this reply helpful? Yes No
Verified answer

LeeD 18 on at

Like (2)

Report

Thanks @gamgoumy This is not a new team but just adding a new user to existing teams. However upon trial and error we go it working via Safari (was using Chrome). I'm not sure if there is a chrome setting stopping the access, but its the same settings for all my users.Thanks @dpoggemann as well for your input!

Was this reply helpful? Yes No
Fighter 4 on at

Like (1)

Report

Hi guys!
Please check if you have the Read privilege set to Organization in your Security Role:
1) Attribute
2) Entity
3) Relationship Entity
Regards
Sergiy

Was this reply helpful? Yes No
KFlanagan 16 on at

Like (0)

Report

When I received this error - I tried using incognito Mode with the same user log in and it worked.
With that information I cleared cache and logged in with the same cred and it worked.

But I have a feeling it was grabbing the cache of my second email which did not contain rights to that site.

Was this reply helpful? Yes No
twhite-cfauk 9 on at

Like (0)

Report

You're a diamond, was missing the relationship read permission on a role trying to grant minimal access to dynamics and was stabbing in the dark until seeing your comment. Many many thanks!

Was this reply helpful? Yes No
kriede 2 on at

Like (0)

Report

We had the same issue at several users of a client and clearing the browser cache in Chrome solved the issue.

Was this reply helpful? Yes No