Forum Discussion
Scheduled Refresh Failure on Report Server (May 2025) - IDbCommand interface exception
Hi FLORENTINO_23,
Thank you for the update, and we are glad to hear that your refresh issue has been resolved.
Based on our understanding, while using SELECT * followed by “Remove Other Columns” will work, it is considered best practice to explicitly select only the required columns in your SQL query. This improves performance, reduces data transfer, ensures better query folding, and helps avoid unexpected schema changes. Your current approach is acceptable for small datasets. However, for production scenarios, defining columns at the source is recommended.
Should you have any further questions, please feel free to contact the Microsoft Fabric community.
Thank you.
Hi FLORENTINO_23,
We appreciate your inquiry through the Microsoft Fabric Community Forum.
Based on our understanding, since the refresh works in Power BI Desktop but fails only on Power BI Report Server with an IDbCommand/IDataReader cancellation error, this may indicate a server side execution issue rather than a problem with the report or the dataset model.
One possible resolution path is to first check the PBIRS logs, for example, RSPowerBI_*.log and correlate the findings with ExecutionLog3 using the SessionID. This will help identify the exact cause of the failure, such as a timeout, a driver/provider issue, a credential or delegation problem, or memory pressure. After that, please ensure driver consistency between Desktop and the server, for example, verify that the same 64-bit ODBC and/or OLE DB providers are installed on both systems. Additionally, validate the authentication context, especially if you are using Windows authentication including Kerberos. If the queries are long running, consider increasing server side timeout settings in ReportServer.config, such as DatabaseQueryTimeout and ExternalCommandTimeout.
Also, review query performance, including whether query folding occurs, heavy joins, and whether source side execution is being used. Monitor server resources and refresh concurrency as well. PBIRS executes refresh operations within a constrained background engine, which may cancel dependent operations if one operation fails.
Additionally, kindly refer to the links below:
Troubleshoot scheduled refresh in Power BI Report Server - Power BI | Microsoft Learn
Power BI report scheduled refresh in Power BI Report Server - Power BI | Microsoft Learn
Power BI report data sources in Power BI Report Server - Power BI | Microsoft Learn
Configure Kerberos to Use Power BI Reports - Power BI | Microsoft Learn
Query folding guidance in Power BI Desktop - Power BI | Microsoft Learn
What's new in Power BI Report Server - Power BI | Microsoft Learn
We hope the information provided helps resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric Community.
Thank you.