Forum Discussion
IDbCommand interface
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 ServiceAs 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 ,
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.
Thank you very much. I am pleased to inform you that the issue has finally been resolved.
After further investigation, I found that the ERP production table was not refreshing properly. The refresh process was taking approximately 6 to 7 hours and eventually stopping without completing successfully.
Our Data Administrator created a separate production table specifically for BI purposes. After connecting to the new table, the issue was successfully resolved.
I would like to sincerely thank the entire Factic Team for your outstanding support, continuous follow-up, and cooperation throughout this process. Your assistance is highly appreciated.