Forum Discussion
Resolver IIIFailed to load data sources.
I am getting a "Failed to load data sources" on some of my datasets. Literally nothing has changed on them for the past 30 days.
Activity ID: ff54089d-e0d1-4b8d-90f0-2ad3530e5c78
Request ID: c40d1ddc-66e2-c0fe-bb58-678a88d269c4
Correlation ID: fb07f1ae-afe2-8959-5c8e-550e5ed93ee3
Status code: 404
Time: Fri Jul 14 2023 14:07:19 GMT-0700 (Pacific Daylight Time)
Service version: 13.0.21054.54
Client version: 2307.1.14623-train
Cluster URI: https://wabi-west-us-c-primary-redirect.analysis.windows.net/
Issue was resolved when I had someone else take over the dataset. The error still popped up for them, but they were able to configure the gateway server settings and then the error went away.
5 Replies
AnthonyGenoveseI also tried to open a service request and I get an error when I try to submit the ticket.
- AnthonyGenovese
Still having this issue. It is a part of a development pipeline. This is happening in dev. QA and Prod are fine.
Hi AnthonyGenovese ,
According to my internal search, I got this error message:
Exception object created: Microsoft.PowerBI.ServiceContracts.PowerBIRemoteServiceException: PowerBI service client received error HTTP response. HttpStatus: 404. PowerBIErrorCode: DMTS_MonikerNotFoundError,
If there is a "404 not found", generally renamed or deleted, if you use a gateway, you can first go to the test environment of the gateway computer to check the path of the data source configuration to see if it can be accessed normally.
Best Regards,
Liu Yang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
- AnthonyGenovese
The exact same gateway is used for Dev, QA, and Prod. The dataset is the exact same between Dev, QA, and Prod. QA and Prod work. Dev is the only one that is not working. When I deploy a new copy of the dataset to a different workspace, it works fine. This seems to be an issue with the Power BI service.
- AnthonyGenovese
Issue was resolved when I had someone else take over the dataset. The error still popped up for them, but they were able to configure the gateway server settings and then the error went away.
