This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
Hi experts,
My desktop report refreh in 2 min and 30 sec but on service report is no refresh and continues refresh and comes this error again and again... please guide.
An error occurred while processing the semantic model. Please try again later or contact support. If you contact support, please provide these details. Hide details Data source errorThe operation was canceled..
The exception was raised by the IDbCommand interface. Cluster URIWABI-WEST-EUROPE-D-PRIMARY-redirect.analysis.windows.net Activity ID4b32d9d9-8671-4e5b-b12b-420365469e6c Request ID3a895656-0ae9-41d2-a16f-c2f68f5f78cf Time2026-05-02 07:24:59Z
Solved! Go to Solution.
Hi @123abc ,
Thank you for reaching out to the Microsoft Community.
To assist further with the root cause analysis, could you please help confirm the following details:
What is the data source type (SQL Server, Lakehouse, API, Excel, etc.)?
How long does the refresh take in Power BI Service compared to Power BI Desktop?
Is the dataset using Incremental Refresh or a full refresh?
What is the approximate dataset size (row count/data volume), and has there been any recent increase?
Based on the error shared, the issue commonly occurs when query execution gets interrupted in the Power BI Service, even though the refresh succeeds in Desktop.
Some possible areas to validate include:
Query timeout or long-running source queries in the Service
Gateway connectivity or network interruptions
Capacity memory/resource pressure
Power Query transformations behaving differently in Service due to query folding
Source database blocking or locking
Incremental refresh or parameter-related issues
Credential or privacy setting differences between Desktop and Service
As part of troubleshooting, please also try the following if possible:
Test refresh with a smaller subset of data
Temporarily remove recent transformations or complex measures
Capture detailed refresh behavior using XMLA endpoint
Best Regards,
Chaithra E.
Hi @123abc ,
May I ask if you have resolved this issue? Please let us know if you have any further issues, we are happy to help.
Thank you.
Hi @123abc ,
We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.
Thank you.
Hi @123abc ,
Thank you for reaching out to the Microsoft Community.
To assist further with the root cause analysis, could you please help confirm the following details:
What is the data source type (SQL Server, Lakehouse, API, Excel, etc.)?
How long does the refresh take in Power BI Service compared to Power BI Desktop?
Is the dataset using Incremental Refresh or a full refresh?
What is the approximate dataset size (row count/data volume), and has there been any recent increase?
Based on the error shared, the issue commonly occurs when query execution gets interrupted in the Power BI Service, even though the refresh succeeds in Desktop.
Some possible areas to validate include:
Query timeout or long-running source queries in the Service
Gateway connectivity or network interruptions
Capacity memory/resource pressure
Power Query transformations behaving differently in Service due to query folding
Source database blocking or locking
Incremental refresh or parameter-related issues
Credential or privacy setting differences between Desktop and Service
As part of troubleshooting, please also try the following if possible:
Test refresh with a smaller subset of data
Temporarily remove recent transformations or complex measures
Capture detailed refresh behavior using XMLA endpoint
Best Regards,
Chaithra E.
What is the data source? Do you have a gateway? Are you sure there is network connectivity between power bi service and the source?
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 33 | |
| 25 | |
| 23 | |
| 20 | |
| 15 |
| User | Count |
|---|---|
| 64 | |
| 41 | |
| 27 | |
| 22 | |
| 22 |