Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hi PBI RS Community,
Since last Friday, we've been getting this error for our scheduled data refreshes.
User are having to open the report in PBI Desktop, refresh and save back to RS.
I've been looking through the log files but couldn't find any useful info or clues to why this could be happening.
I am contemplating a server reboot hoping that it would fix the issue. However, before I do that, i'd like to know what the root cause is and a possible fix is so that if this happens in the future, i'll know what to do.
SessionID: 5329586f-5338-4465-b285-760658dd2a0b [0] -1055784932: Timeout expired. The timeout period elapsed prior to completion of the operation.. The exception was raised by the IDbCommand interface. [1] -1055784932: The command has been canceled.. The exception was raised by the IDbCommand interface. [2] -1055784932: The command has been canceled.. The exception was raised by the IDbCommand interface. [3] -1055784932: The command has been canceled.. The exception was raised by the IDbCommand interface. [4] -1055784932: The command has been canceled.. The exception was raised by the IDbCommand interface. [5] -1055784932: Timeout expired. The timeout period elapsed prior to completion of the operation.. The exception was raised by the IDbCommand interface.
There have been no changes to the reports, dashboards and credentials. Data source connection test is successful.
Any help is would be greatlty appreciated.
Thanks in advance!
Solved! Go to Solution.
Hi,
We fixed the issue by restarting the Report Server service. There was no unexpained growth in data volumes. Infact, data volumes were small only a few hundreds of rows.
Thanks, PowerAI.
Have you tried running the various queries or attaching some kind of profiler to the source of the data? Is it suddenly performing really badly? (data growth can cause these kinds of issues)
Hi,
We fixed the issue by restarting the Report Server service. There was no unexpained growth in data volumes. Infact, data volumes were small only a few hundreds of rows.
Thanks, PowerAI.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!
| User | Count |
|---|---|
| 8 | |
| 4 | |
| 3 | |
| 2 | |
| 2 |