Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Hi
I am in the process of learning Power BI and built few reports and published on "Premium Content" workspace. But I am getting Scheduled Refresh Error. Below is the error message. I have seen few posts on the same, should i just re-publish reports or any other suggestions are welcome. Please advise
Failure details: The last refresh attempt failed because of an internal service error. This is usually a transient issue. If you try again later and still see this message, contact support.
DataSource.Error: <pii>Microsoft SQL: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.</pii>. DataSourceKind = <pii>SQL</pii>. DataSourcePath = <pii>01euwdwanal01p.database.windows.net;upfieldReporting</pii>. Message = <pii>Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.</pii>. ErrorCode = <pii>-2146232060</pii>. Number = <pii>-2</pii>. Class = <pii>11</pii>. ;Microsoft SQL: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding
Solved! Go to Solution.
There may be several reasons of why this is happening, depending if you connected to your data source either by Import or by Direct Query. First impression is that the time it takes to your Power Query to process exceeds the threshold limit of Power BI processing (2 hours to refresh a data source). This may be because either your data model or queries are not optimal (too heavy) or the data source is too busy to process your requests.
If you have refreshed successfully previously then you should wait or try to republish.
Hi, @rshanka2
Why not try to use direct query? When there is a large amount of data, the import method can take up a lot of resources, such as memory.
Here are some reference information that may be helpful
https://stackoverflow.com/questions/51718344/how-to-set-a-max-run-time-timeout-for-power-query
Hope this helps.
Best Regards,
Community Support Team _ Zeon Zheng
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thank You, my workspace does not allow direct query for now. So will have to use Import.
Also I did increase the timeout command and the report ran fine on web.
Thank You all for your prompt response.
Thanks for your feedback😀. Could you please mark your post as Answered since it is working now? It will help the others in the community find the solution easily if they face the same problem with you. Thank you.
Hi, @rshanka2
Why not try to use direct query? When there is a large amount of data, the import method can take up a lot of resources, such as memory.
Here are some reference information that may be helpful
https://stackoverflow.com/questions/51718344/how-to-set-a-max-run-time-timeout-for-power-query
Hope this helps.
Best Regards,
Community Support Team _ Zeon Zheng
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks Much. I do use import.
1) Also should i increase the time out from SQL to PBI desktop query to > 2hrs and publish so that the reports run without failing to refresh?
2) One of the reports had simple query using NO locks and a where clause and was still not able to refresh. So was wondering what was going on behind scenes.
3) Just a suggestion for MS to have a command for schedule refresh time out too so that we can directly increase time out period on the web/workspace than actual desktop version.
Thanks Again
There may be several reasons of why this is happening, depending if you connected to your data source either by Import or by Direct Query. First impression is that the time it takes to your Power Query to process exceeds the threshold limit of Power BI processing (2 hours to refresh a data source). This may be because either your data model or queries are not optimal (too heavy) or the data source is too busy to process your requests.
If you have refreshed successfully previously then you should wait or try to republish.
User | Count |
---|---|
128 | |
108 | |
99 | |
65 | |
62 |
User | Count |
---|---|
137 | |
115 | |
102 | |
71 | |
61 |