Hi Folks,
We have been seeing frequent issues with the scheduled data refresh in Power Bi online. Our data is refreshed directly from Azure Sql Database and we see this issue atleast 5-6 times a week (sometimes more). The issue is more frequent for the report "MucpViewAndClickTracking" which has the largest amount of data compared to our other reports.
Failure Error msg : the last refresh attempt failed because of an internal service error.
Other data
Technical Information:
Activity Id: 02f891d3-1fbc-400e-ae56-067c67e47608
Request Id: 5c6b2b09-f221-488b-ab43-01c5fe509286
Cluster Name: DF-MSIT-SCUS-redirect.analysis.windows.net
Refresh Start Time: 12/29/2016 20:38:11Z
Refresh End Time: 12/29/2016 22:00:12Z
Let me know if you need more information.
3 Comments
v-qiuyu-msftCommunity Support
Hi vishayv,
The same issue has been reported: CRI 28622015, CRI 24196163. I will keep an eye on this issue and update here once get feedback.
Best Regards,
Qiuyun YuAny updates on this ? we have been seeing some more failures recently, albeit with a different error messages :
Error Details
error msg : Microsoft SQL: Transaction (Process ID 99) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Technical Information:
Activity Id: c768b34b-464b-4ff2-84d8-86a99eed8cef
Request Id: b6d7c837-8c54-4b05-8ac3-051c0993ceae
Cluster Name: DF-MSIT-SCUS-redirect.analysis.windows.net
Refresh Start Time: 01/03/2017 08:40:51Z
Refresh End Time: 01/03/2017 09:34:00Z- v-qiuyu-msft
Hi vishayv,
Sorry for the late response. The CRI mentioned in my original post are closed. It turns out the issue is related to the report.
In your scenario, regarding the new error "Microsoft SQL: Transaction (Process ID 99) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.", it should be related to the SQL database deadlock. You can follow this article troubleshoot the issue: Transaction (Process ID) was deadlocked on lock resources with another process and has been chosen as the deadlock victim (Msg 1205).
Best Regards,
Qiuyun Yu