Mobile Offline Dynamics CRM app error - dynamics-crm

Mobile offline profile defines that every account should be downloaded. Status of the accounts is "available" in the mobile app. However, when we go offline, no account record can be opened due to following error in Event Viewer:
The requested record was not found or you do not have sufficient permissions to view it.
Inner Error Message:
**
Offline store failed with error: 'Error: SQLite.SQLiteException: no such table: account
at Microsoft.MicrosoftDynamicsCRMforWindows10!+0x2c1548
at Microsoft.MicrosoftDynamicsCRMforWindows10!+0x366779
at Microsoft.MicrosoftDynamicsCRMforWindows10!+0x36552a
at System.Collections.Generic.List..ctor(Collections.Generic.IEnumerable collection)
at Microsoft.MicrosoftDynamicsCRMforWindows10!+0x35bda2
at Microsoft.MicrosoftDynamicsCRMforWindows10!+0x35bb44
at System.Action.Invoke()
at Microsoft.MicrosoftDynamicsCRMforWindows10!+0x35b50c
at Microsoft.MicrosoftDynamicsCRMforWindows10!+0x35b3af' while trying to retrieve with key 'account:'
**
Also, following status is maintained in the application:
"An administrator made changes to the Dynamics 365 system that might affect offline availability. We're working on getting everything back in sync."
This message is more than 1 week for now.
Anybody has an idea to fix this? Version is V8.2 and user has sufficient permissions to access accounts.

Related

Power Automate (MS Flow) Error: "Something went wrong. The requested approval is not accessible to the caller." How do I fix this?

My user tries to access Microsoft Power Automate (Flow) approvals via email notifications that the Flow sends to them. When clicking on the approval, they get an error "Something went wrong. The requested approval is not accessible to the caller." When directly accessing their approvals at us.flow.microsoft.com > Action items > Approvals, they only see approvals up to January. The same approvals are working for other users. How do I fix approval access?
I tried having the user login via an incognito tab. I also checked whether the user still has MS PA licenses assigned to them, and they seem to be correct (the user has MS 365 E1, MS 365 Business Premium, and MS Power Automate Free).
Figured out the what was causing the issue for our user. The user had a duplicate enterprise microsoft account, so both were being sent the email notification about the approvals, but only the duplicate account was being given access to them. Removing the duplicate account fixed the issue.
If we had had two users with the same name & neither can be deleted, another solution would've been to change how the approvals are routed (ie. by email instead of name.)

Failed to get device list from HomeGraph: Requested entity was not found

I have implemented Smart home actions as per documentation, i have enabled Home graph api,
i got agentUserId from Google Oauth playground, but when i submit agentUserId and service account key in test suite its returns an Error 404 msg:
Failed to get device list from HomeGraph: Requested entity was not found.
I am able to operate my devices from google home app, but not able to test with test suite.
I am looking for possible reasons.
I encountered this today, and was confused as nothing was even trying to contact my server. I had been using the test tool successfully beforehand, so I knew my agentUserId was correct, that HomeGraph API was enabled and my service account was correct. It turned out that I was not currently linked to my Google Home app on my mobile with the same user at the time I was trying to run the test tool. I had unlinked it, therefore the agentUserId was not found on Google's side.
To summarise:
On your mobile link to your test Action
Make sure this is the same user account which you have the agentUserId from - ideally capture a log of your SYNC output and compare
Verify your service account's key in the JSON file you upload is listed in the list of "private_key_id"s in your service account
Try the test tool again whilst you are still linked on your mobile

Dynamics 365 Plugin Registration Tool gives permission error

When I try to connect to Dynamics 365 CRM with the Plugin Registration Tool I get the following permission error:
"You don't have permission to access any of the organizations in the
Microsoft Common Data Service region that you specified. If you're not
sure which region your organization resides in, choose "Don't know"
for the CDS region and try again. Otherwise check with your CDS
administrator. Parameter name: EMEA"
I have the System Administrator role
I can sign-in to the web interface and work with no issues
I'm sure of our region, tried to login with and without it ("Don't know" option)
Also tried with an application password as our organization uses multi factor authentication
Using the latest version of the tool on Nuget (9.0.0.9506 in the about dialog)
I can connect to my trial server the same way
We had a user who was able to connect with the same user roles set
This seems machine and account independent. Other users including the organization creator are getting the same error
We are directly connected to the internet, no proxies
One solution I've read suggested cleaning the cache files which don't appear on my system. And we get the same error on clean installations.
Solved by leaving the "Show Advanced" checkbox unchecked and not entering User ID / Password. Then a second dialog opens for credentials and 2FA authentication which just works.
You don't need an application password, as you'll be asked for MFA in the next step.
I don't know how our old teammate was able to sign in with the "Show Advanced" option selected. He was getting the same dialog and continue.

Dynamics CRM Plugin Trace log record throwing Access Denied error for System Administrator

Its really weird to see Access Denied error for System Administrator in CRM.
When trying to open any record from Plugin trace logs, system throws the below error in our dev environment.
Access Is Denied
You do not have enough privileges to access the Microsoft Dynamics CRM object or perform the requested operation. For more information, contact your Microsoft Dynamics CRM administrator.
Unable to verify the missing access rights as there is no 'Download Log' button, platform trace cannot be checked since this is CRM online. I don't see any relationship control issue like lookup/subgrid in this OOB entity.
Also if you see the page title, it says Dashboard - fishy? Any pointers to troubleshoot this?
This is crazy, when we try to delete the Plugin trace log entries, it says the most useful message:
Not enough privilege to access the Microsoft Dynamics CRM object or perform the requested operation. The current Organizationid '79bd6aa8-984f-4d51-ae47-0a178c71d762' does not match with userOrTeam's organization id '760ed188-468e-40ca-86bd-ceca16ee64a1'.
So these were moved as part of sandbox refresh from another instance. Damn, then why they are showing in this org grid beyond POA; MS can answer it, probably they will solve this platform bug as its not allowing to delete because of POA.

Dynamics 365 unexpected error

When creating a case I get the below error.
Access Error The system could not log you on. This could be because
your user record or the business unit you belong to has been disabled
in Microsoft Dynamics 365. If you contact support, please provide the
technical details.
This occurred shortly after deleting the CRM Admin user and creating a new CRM Admin user in the Office 365 users screen.
The more technical message is
The user with
SystemUserId=bb51ba1c-66e8-4dc1-82ca-cb64e25f3ff9 in
OrganizationContext=7e061672-3a31-4588-9770-9f94711c7f09 is
disabledDetail.
The error message is saying that the user with that ID is disabled so the first thing to do would be to open that record and check which user it is.
To do that, use the URL below but replace the xx's and the yourregion part of the url (I've already added your user id).
https://xxxxxxxx.yourregion.dynamics.com/main.aspx?etc=8&extraqs=&histKey=952109180&id={bb51ba1c-66e8-4dc1-82ca-cb64e25f3ff9}&newWindow=true&pagetype=entityrecord
You will then need to enable that user or resolve problems from there.
I would also check that you don't have any plugins or workflows which have been setup to run as that user when creating a case.

Resources