Refresh Error in Power Bi

[Tsheps]

Hi there. I've always refreshed Power Bi reports with ease, however, when i refresh certain reports this morning, I receive the following error(which prevents a refresh):
DataSource.Error: Microsoft SQL: The service has encountered an error processing your request. Please try again. Error code 8657.
A severe error occurred on the current command. The results, if any, should be discarded.
RequestId: TDS;3e45b3db-de1e-4431-b757-8b9a663
Time: 2026-07-13T12:45:50.7038293Z
Details:
DataSourceKind=CommonDataService
DataSourcePath=org195567.crm4.dynamics.com
Message=The service has encountered an error processing your request. Please try again. Error code 8657.
A severe error occurred on the current command. The results, if any, should be discarded.
RequestId: TDS;3e45b3db-de1e-4431-b757-8b9a6
Time: 2026-07-13T12:45:50.7038293Z
ErrorCode=-2146232060
Number=40001
Class=16
State=1
ConnectionId=3e45b3db-de1e-4431-b757-8b.

Kindly please help me to troubleshoot this issue. 

[v-kathullac · Accepted solution]

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.

[kirstend]

I am having this issue in PowerBI as well, both in the desktop app and the scheduled refreshes. I have narrowed it down to four tables in my Dataverse for Teams environment. It started yesterday morning no later than 8am Mountain Time. I also got a similar error code when using a Dataflow to move data from a Dataverse for Teams table to a full Dataverse environment yesterday with one of the problematic tables. All these worked fine as of late Wednesday.

I have a case open with Microsoft since this is directly impacting our Procurement function, including reports used by our C Suite.

Error with my dataflow: 
Mashup Exception Data Source Error, Error Details: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: DataSource.Error: Microsoft SQL: The service has encountered an error processing your request. Please try again. Error code 8657. A severe error occurred on the current command. The results, if any, should be discarded. RequestId: TDS;1d9f19f7-6313-4bed-a609-4972050cd4a9;10 Time: 2026-07-16T17:02:02.6837773Z Details: Reason = DataSource.Error;ErrorCode = 10478;DataSourceKind = CommonDataService;DataSourcePath = org5fc3dfd9.crm.dynamics.com;Message = The service has encountered an error processing your request. Please try again. Error code 8657. A severe error occurred on the current command. The results, if any, should be discarded. RequestId: TDS;1d9f19f7-6313-4bed-a609-4972050cd4a9;10 Time: 2026-07-16T17:02:02.6837773Z;ErrorCode = -2146232060;Number = 40001;Class = 16;State = 1;ConnectionId = 1d9f19f7-6313-4bed-a609-4972050cd4a9;Microsoft.Data.Mashup.Error.Context = User (Request ID: 9bee1ae5-453f-479e-9013-3d6259771f70).

[Arjunushas]

Is your issue resloved ?

[kirstend]

We have now learned that Microsoft recently implemented enforcement of capacity limits for Dataverse for Teams environments, and that is what the issue is. I thought they were already enforcing it, so I did not realize we were out of compliance (the capacity information shows us at 83%) and would have issues. Ironically we were working on moving to a full (paid) Dataverse for this solution, and they had initially said they couldn't unblock us or add capacity unless we proved we had licensing and were moving, but now they are just advising that we reduce the columns in the query that won't run, which has not solved the problem, to date. I think we'll be moving to another solution in general and stop using the Power Platform after this (still ongoing) issue.

[kirstend]

Not yet. They came back and said: "Our product team reviewed the org that's impacted and found it is a "Lite" org that is not intended for any significant workload, and it is hitting capacity limits.

Here's what the error message means:

Error code 8657 is "Could not get the memory grant of N KB because it exceeds the maximum configuration limit..."

In plain terms: your query asked the SQL engine for a memory grant, but the amount requested exceeded the maximum memory that your service tier / resource pool / Resource Governor workload group is allowed to hand out. The query never gets to run because it can't reserve the working memory it estimated it needs.

The wrapper text — "The service has encountered an error processing your request. Please try again." — is Azure SQL's generic transient-error phrasing, but 8657 itself is not really transient. Retrying usually reproduces the same failure because the underlying cause (query shape or tier limits) hasn't changed.

Moving forward, the product team is unable to unblock/add capacity without the expected license for a "fully fledged" Dataverse organization that provides the capacity you would require.

Can you provide your exact contract details with Microsoft? It appears based on this being a "Lite" org that you might not be contracted for a "production-ready" organization."

Basically saying this is because I'm using Dataverse for Teams, and have essentially reached my capacity, but I'm at lower capacity (83%) now than previously, (85%), and the issues only started a week ago.

I think they changed something to try to force people using Dataverse for Teams that were getting close to the top of their capacity to move to full Dataverse.

We were already trying to build out a paid version of this in full Dataverse, but are probably 90 days away from launch, so we've asked them to unblock/add capacity to enable us to keep using our current environment while we work to move to full Dataverse and have not heard back yet.

This will change our long-term plans and we will likely move ASAP to an OOB solution since Microsoft seems to be changing the rules in the middle of the game, and we don't have faith that something like this won't happen again in the future. We are already seeing something similar happening with PowerBI and Fabric where it seems like they are trying to force people behind another paywall there.

[Arjunushas]

Hi @Tsheps ,

I am experiencing the same issue. Has your issue been resolved?

[Prince0011 · Accepted solution]

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.

[Tsheps]

Hi @Prince0011 thank you for your response. 

I also suspect it's a Dataverse issue rather than a Power Bi issue. The refresh issue persists for all versions of the diffderent reports connected to the same source. 

[v-kathullac · Accepted solution]

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.

[Arjunushas]

I am experiencing the same issue with a specific Dataverse table. The query I'm using is very basic and does not contain any complex transformations:

Power Query

let

Source = CommonDataService.Database("<Dataverse Environment>", []),

Opportunity = Source{[Name="<Table Name>"]}[Data]

in

Opportunity

Even with this simple query, the table fails to load. I also tested loading the same table into Excel, and it returns the same error. All other tables from the same Dataverse environment load successfully without any issues.

Additional details:

• Started occurring yesterday around 9:30 AM IST.
• Using the latest version of Power BI Desktop.
• The issue is isolated to one table only.
• The same behavior occurs in both Power BI and Excel, suggesting the issue may not be client-related.

Error:

DataSource.Error: Microsoft SQL: The service has encountered an error processing your request.
Please try again. Error code 8657.

A severe error occurred on the current command. The results, if any, should be discarded.

DataSourceKind=CommonDataService
ErrorCode=-2146232060
Number=40001
Class=16
State=1

Since the error occurs with a direct table load and only for this specific table, I'm wondering if there could be an issue with the table's metadata, schema, indexes, relationships, permissions, or the Dataverse TDS endpoint for this table. Has anyone else encountered Error 8657 / 40001 for a single Dataverse table, and if so, what was the resolution?

[Tsheps]

Hi @v-kathullac thanks so much for the dubgging tips! Will sure try them out. 

[djurecic]

Hi @Tsheps ,

 What is the data source of the sementic model- it looks like could be related to a memory issue. 

[Tsheps]

Hi. It's a table in PowerApps(Dataverse)