Forum Discussion
Report Failure in Service
All the reports were refreshing with no issues till 3 days back, but suddenly all the reports have started failing in prium as well as pro workspace with below error-
In all the failure message, it s the same message with different report name which is at the end (in this case it is freightforwarder container)
| Data source error: | {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"The key didn't match any rows in the table."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ErrorCode","detail":{"type":1,"value":"10061"}},{"code":"Microsoft.Data.Mashup.ValueError.Key","detail":{"type":1,"value":"[workspaceId = \"03816662-1884-4d76-8902-83fcfa6878eb\"]"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"Expression.Error"}},{"code":"Microsoft.Data.Mashup.ValueError.Table","detail":{"type":1,"value":"#table({\"workspaceId\", \"workspaceName\", \"workspaceType\", \"Tags\"}, {})"}}],"exceptionCulprit":1}}} Table: Freight Forwarder Containers. | |||||||
| Cluster URI: | WABI-AUSTRALIA-SOUTHEAST-redirect.analysis.windows.net | |||||||
| Activity ID: | 01cca263-b015-4cf2-8854-4b1e64a014bc | |||||||
| Request ID: | d47e8547-3c99-4314-a6fb-153076c4b655 | |||||||
| Time: | 2025-09-19 08:33:48Z | |||||||
| Details | # Type Start End Duration Status Details
|
Hi learner03 , Thank you for reaching out to the Microsoft Fabric Community Forum.
The fact that your report refreshes successfully in Desktop but fails in the Service indicates the issue is specific to the Power BI Service environment, not the report itself. This error usually means the service is trying to access a workspace, table,or data row that it cannot find or doesn’t have permission to access.
Most likely causes are the service principal, gateway account or dataset credentials used in the Service no longer have proper access to the workspace or data source. Even if IT hasn’t intentionally changed anything, tokens can expire, credentials can become invalid or subtle permission changes may block access.
You should re-enter or test the dataset credentials in the Service, ensure the gateway account (if used) has proper permissions and confirm that the workspace and its tables are still accessible by the Service account. Desktop works because it runs under your user context, which still has access, whereas the Service uses its own account context. Once the credentials and permissions are validated, the refresh in the Service should start working again.
6 Replies
Likey Causes:
-
Permissions changed — your service principal / gateway account lost access to that workspace or its contents.
-
If this is querying the Power BI REST API, the API response might have changed.
-
If this is querying an external database (SQL, SharePoint), then the join key changed or the source stopped returning rows.
Shravan133 The report is refreshing in the desktop though but not just in service and asked the IT team, they said they changed nothing from their end
Hi learner03 , Thank you for reaching out to the Microsoft Fabric Community Forum.
The fact that your report refreshes successfully in Desktop but fails in the Service indicates the issue is specific to the Power BI Service environment, not the report itself. This error usually means the service is trying to access a workspace, table,or data row that it cannot find or doesn’t have permission to access.
Most likely causes are the service principal, gateway account or dataset credentials used in the Service no longer have proper access to the workspace or data source. Even if IT hasn’t intentionally changed anything, tokens can expire, credentials can become invalid or subtle permission changes may block access.
You should re-enter or test the dataset credentials in the Service, ensure the gateway account (if used) has proper permissions and confirm that the workspace and its tables are still accessible by the Service account. Desktop works because it runs under your user context, which still has access, whereas the Service uses its own account context. Once the credentials and permissions are validated, the refresh in the Service should start working again.
-
Hi learner03 , hope you are doing great. May we know if your issue is solved or if you are still experiencing difficulties. Please share the details as it will help the community, especially others with similar issues.
Hi learner03 , Hope you're doing okay! May we know if it worked for you, or are you still experiencing difficulties? Let us know — your feedback can really help others in the same situation.
Hi learner03 , Hope you're doing fine. Can you confirm if the problem is solved or still persists? Sharing your details will help others in the community.
