ServerError_DMTS_MonikerDatasourcesNotFoundErrorCode

Adding to this for future context.

We had this error when a user whom had left the org still 'owned' PowerBi Reports. As soon as I moved ownership to myself, the error stopped and everything worked as expected.

Hi KarenL7,

Thank you for reaching out to the Microsoft fabric community forum.

The error you're encountering: ServerError_DMTS_MonikerDatasourcesNotFoundErrorCode

This typically indicates that the Power BI service cannot align the dataset’s data source with any configured sources on the on-premises data gateway. Common causes include:

• A discrepancy between the dataset's source definition and the gateway configuration.
• The gateway's metadata cache being out of sync.
• Or as seems to be the case here, a backend mapping issue affecting multiple users.

You've done well by adding temporary data sources to continue refreshes. For a permanent solution and a deeper understanding of the issue, I recommend reviewing the following steps that might be resolve the issue.

Immediate Workaround: Add temporary/duplicate data sources to the gateway to resume refreshes. This is not ideal but allows continuity.

Verify Existing Gateway Bindings: Navigate to Power BI Service > Workspace > Dataset > Settings > Gateway Connection. Confirm if it indicates "Not configured correctly" despite the gateway being online.

Rebind the Dataset to the Gateway: In Gateway Connection, ensure the following: The server/database names exactly match (including casing and formatting). The authentication method aligns with what is configured in the gateway. If necessary, delete the faulty gateway source and recreate it with precise settings.

Utilize Advanced Editor to Compare Queries: In Power BI Desktop, access Advanced Editor and review the data source path. Confirm it matches the gateway path (e.g., server.domain.com vs. SERVER might lead to mismatches).

Republish the Dataset: After verifying the data source, publish a new version of the PBIX file and reconfigure the gateway connection.

Update Power BI Gateway: Ensure the latest version of the gateway is installed, as updates may resolve certain bugs: Download latest gateway

Kindly please refer to the below provided official Microsoft links for more information:
Troubleshoot gateways - Power BI | Microsoft Learn
Data refresh in Power BI - Power BI | Microsoft Learn

Also kindly refer to the below solved thread links for better understanding:
Solved: Analysis Services Error: DMTS_MonikerWithUnboundDa... - Microsoft Fabric Community
Solved: Error in the Service with Refresh - ServerError_DM... - Microsoft Fabric Community

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you for using Microsoft Community Forum.

DamoUK  - I have literally just refreshed my powerbi reports to check the status of everything - and all the datasources have suddenly just reappeared!!

I am not sure what had happened to be honest as I had not changed anything.  Unsure if Microsoft had suddenly changed something in the service - but I am now able to begin to refresh - hopefully you can now do the same?

Karen

Hi KarenL7 

You're encountering a situation that appears to be affecting multiple users across the Power BI ecosystem, where scheduled or on-demand dataset refreshes are failing despite the data sources being correctly configured and previously functioning. This issue is often observed when the Power BI Service unexpectedly loses the mapping between the dataset and the on-premises data gateway, even though the gateway itself is operational and logs show no explicit errors. In such cases, the service starts prompting for a datasource that is already defined, leading to confusion and refresh failures.

As you've rightly identified, others in the Microsoft Fabric Community have experienced similar problems, such as those reported in this community thread. In these scenarios, Power BI seems to treat existing data sources as missing or invalid, possibly due to an internal sync issue between the service and the gateway metadata. A practical workaround, as you've implemented, involves creating temporary (duplicate) data sources in the gateway to "reconnect" the dataset to a valid source and allow urgent refreshes to proceed. This can serve as a short-term fix but also signals a need for a more permanent resolution from Microsoft's side.

For others experiencing this issue, the recommended approach is to verify the following: ensure that the gateway is online and that the data source credentials are up to date; cross-check the gateway mapping in the dataset settings in Power BI Service; and consider removing and re-adding the data source or reassigning the gateway to the dataset. Additionally, it’s worth keeping an eye on the Microsoft Fabric Service Health dashboard for any broader incidents and submitting a support ticket if the issue persists beyond a temporary workaround.

Experiencing this issue again in Jan 2026. Last time we encountered this error MS issued a global fix which automatically created successsful refreshes, our POA is to sit tight for the same fix. Is anyone encountering the same issue again?