topic Re: Refreshing Failure in Report Server

Refreshing Failure

Anonymous — Thu, 13 Feb 2025 03:06:21 GMT

Can someone help me to figure out what is going on with this error message? Thanks, appreciated

Data source error: {"error":{"code":"DMTS_OAuthTokenRefreshFailedError","pbi.error":{"code":"DMTS_OAuthTokenRefreshFailedError","details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"AADSTS700003: Device object was not found in the tenant '8da74ad6-a2e3-4087-96e3-e8f1dc8f82cc' directory. Trace ID: 1095d020-bbf0-4a26-b677-67d4c9750000 Correlation ID: 52adc646-d621-46bb-ba05-b0b673b70805 Timestamp: 2025-02-13 02:05:03Z"}}],"exceptionCulprit":1}}} Table: System One WO.
Cluster URI: WABI-WEST-US-D-PRIMARY-redirect.analysis.windows.net
Activity ID: 7054f0bd-da7d-458b-97da-b3b64e0e59ab
Request ID: a2238cc2-9b86-4430-ab5f-291eca46623a
Time: 2025-02-13 02:05:03Z

Re: Refreshing Failure

Poojara_D12 — Thu, 13 Feb 2025 04:55:39 GMT

Hi @Anonymous

The error message indicates that Power BI is unable to refresh the OAuth token due to an issue with Azure Active Directory (AAD). Specifically, it states that the device object was not found in the tenant, which means your device may not be registered in your organization's AAD. This can happen if your device was recently removed, reset, or if your account was modified. Another possible reason is that the authentication token used for the data connection has expired and cannot be refreshed, often due to password changes, multi-factor authentication (MFA) issues, or account permission updates. To fix this, you should first check if your device is properly registered in Settings → Accounts → Access work or school. If the issue persists, go to Power BI Service → Settings → Manage connections and gateways, locate the affected data source, and re-authenticate by updating the credentials. Also, ensure your account still has the necessary access permissions to the data source. If using a service principal, verify that it has not been disabled. If you are unsure, contacting your IT administrator can help resolve access-related problems.

Re: Refreshing Failure

Anonymous — Thu, 13 Feb 2025 05:41:47 GMT

Hi, Poojara_D12,

I have all dataflows, semantic models and reports in one workspace last year and they were refreshing regularly without too much issue.

In 2025, I set up the dataflows in workspace A then post my reports and semantic models in another workspace B. And none of semantic models were able to refresh successfully. It further triggered the above shared error message. Do you think if two separated workspaces were the cause of this error message? Please advise. Thanks,

By the way, I just published the semantic model to the same workspace as dataflow models. It still could not refresh successfully.

I am new to this power BI service portal. Can you help me further? Thanks,

Re: Refreshing Failure

Poojara_D12 — Thu, 13 Feb 2025 05:42:09 GMT

Hi @Anonymous

Yes, separating dataflows into Workspace A while keeping semantic models and reports in Workspace B can cause refresh failures if the proper connections and permissions are not set up. Dataflows are not automatically accessible across workspaces unless explicitly shared and correctly referenced. One common issue is missing permissions, where the service account or user running the refresh lacks Viewer or Contributor access to Workspace A. Additionally, if the dataflow in Workspace A is using an on-premises gateway, Workspace B must also have the correct gateway settings. Another factor could be licensing restrictions, especially if using Premium Per User (PPU) or Fabric capacities, which require both workspaces to be in the same capacity. You should verify that the semantic models in Workspace B are correctly connected to the shared dataflows in Workspace A and update the references if necessary. Testing the refresh in Power BI Desktop before publishing can help diagnose the issue.

Re: Refreshing Failure

Anonymous — Thu, 13 Feb 2025 05:56:24 GMT

Hi Poojara:

But how come even I put the sementic model into the same workspace as dataflows, it still has the refresh issue. I just tested it. When I worked on Power BI desktop, I have no issue for refreshing.

My laptop was just reimaged last week, which might requires some new setup but I don't know how. Can you teach me?

May I know where to find Settings → Accounts → Access work or school? Thanks, appreciated.

The following is the error I got:

Data source error: {"error":{"code":"DMTS_OAuthTokenRefreshFailedError","pbi.error":{"code":"DMTS_OAuthTokenRefreshFailedError","details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"AADSTS700003: Device object was not found in the tenant '8da74ad6-a2e3-4087-96e3-e8f1dc8f82cc' directory. Trace ID: 3bcf3167-0f10-4d7f-9884-cf13da9b2a00 Correlation ID: 2b6a34e3-031f-4855-b9be-64c32d88068a Timestamp: 2025-02-13 05:55:12Z"}}],"exceptionCulprit":1}}} Table: Cost Prev Year.
Cluster URI: WABI-WEST-US-D-PRIMARY-redirect.analysis.windows.net
Activity ID: 76681ab0-aa09-4d76-a009-1848125616a8
Request ID: 68fe20aa-f34d-898f-08cf-8903eab99268
Time: 2025-02-13 05:55:17Z

Re: Refreshing Failure

Poojara_D12 — Thu, 13 Feb 2025 05:58:47 GMT

Hi @Anonymous

If your semantic model and dataflows are in the same workspace but still failing to refresh, the issue might be related to authentication or missing configurations after your laptop was reimaged. In Power BI Service, you need to verify that your data source credentials are correctly set up. Go to Settings → Semantic Model Settings → Data Source Credentials, and ensure they are entered correctly. If you're using an on-premises gateway, check Manage Gateways to confirm that it is running and mapped properly. Since your refresh works in Power BI Desktop but fails in the cloud, republishing the latest version may help. Additionally, ensure your account is properly connected by navigating to Settings → Accounts → Access work or school on your laptop. If the issue persists, check whether your workspace is on Premium Per User (PPU) or Fabric capacity, as licensing restrictions might affect refresh behavior. Reviewing these settings should help resolve the issue.

Re: Refreshing Failure

Anonymous — Thu, 13 Feb 2025 06:07:28 GMT

Hi, Poojara:

Thanks for your prompt response and help me patiently. You nailed it. It was Data Source Credentials.

Thanks, appreciated.

Re: Refreshing Failure

Poojara_D12 — Thu, 13 Feb 2025 06:09:24 GMT

Glad that it helped you!! Happy to help 🙂

If possible kindly subscribe my youtube channel and share as much as you can, it really motivates me.

Thanks in advance!

Re: Refreshing Failure

Anonymous — Thu, 13 Feb 2025 19:39:57 GMT

I just did subscribe to your channel. Looking forward to learning more from you. 🙂