Refresh Error in Power Bi

Thankyou djurecic   for Addressing the issue.

Hi Tsheps  ,

Thank you for reaching out to Microsoft Fabric Community Forum, Below are the few debug points which can resolve your issue.

• Retry the refresh after 15–30 minutes, as Error 40001 is often a transient service issue.
• Check Microsoft 365/Power Platform Service Health to verify if there is an ongoing Dataverse or Power BI service incident.
• Identify the failing query/table by refreshing each query individually in Power Query Editor.
• Test the Dataverse connection by creating a new Power BI report and loading a small table from the same Dataverse environment.
• Clear the data source permissions in Power BI Desktop (File > Options and settings > Data source settings) and sign in again.
• Verify recent changes in the Dataverse environment, such as renamed/deleted tables or columns, relationship changes, or security updates.
• Reduce query complexity by removing unnecessary columns, filtering data at the source, and avoiding large joins if applicable.
• Update Power BI Desktop to the latest version and test the refresh again.
• Test from another client/tool (e.g., SSMS using the Dataverse TDS endpoint or Power Apps) to determine whether the issue is with Dataverse or Power BI.
• If the issue persists, collect logs and environment details (Power BI version, affected tables, Desktop/Service behavior, and whether all users are impacted) and escalate to Microsoft Support if necessary.

below is the microsoft support ticket link : 

Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn

Thanks,

Chaithanya.

Hi,

Based on the error details, this appears to be a service-side Dataverse (Common Data Service/TDS endpoint) issue rather than a problem with your Power BI report.

A few things to try:

• Verify whether you can query the same Dataverse tables outside of Power BI (e.g., using the TDS endpoint or another client). If the same error occurs, it's likely a Dataverse service issue.

• Since the reports refreshed successfully before and only started failing recently, check whether there were any recent changes to the Dataverse environment, schema, or security roles.

• If your organization uses the Dataverse TDS endpoint, verify that it's still enabled and that the required user permissions are intact. Microsoft has guidance on TDS endpoint configuration and access control: https://learn.microsoft.com/power-platform/admin/control-tds-settings

• Clear the Power BI cache and retry the refresh, or test from another machine to rule out a local issue.

The SQL error 40001 is commonly associated with transient service or transaction failures. Since the issue appeared suddenly and affects previously working reports, I'd recommend opening a Microsoft Support ticket if it persists. Include the RequestId, ConnectionId, timestamp, and full error message so Microsoft can trace the request in the backend logs.

Some related community discussions that may also be useful:

• Dataverse SQL/TDS troubleshooting: https://learn.microsoft.com/power-apps/developer/data-platform/dataverse-sql-query

• A similar Dataverse TDS issue where re-enabling the TDS endpoint resolved metadata problems: https://community.dynamics.com/blogs/post/?postid=2e85893b-6107-4588-8aa9-1c63996ce89d

To help narrow it down, could you confirm:

• Does the issue affect all reports connected to this Dataverse environment or only specific ones?

• Are you connecting via the Dataverse connector or directly through the TDS endpoint?

• Has anything changed in the Dataverse environment since the last successful refresh?

If Microsoft identifies the root cause or provides a workaround, please consider sharing the resolution here—it would be very helpful for others encountering the same Error 8657.

If you found this reply helpful, please consider giving it a Kudos. If it helps resolve your issue, marking it as the Accepted Solution will help other community members facing the same problem.