Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
I have a scheduled refresh, but this morning it failed, and the message I got is:
Power BI Premium Backend Error: | An error has occurred while framing the dataset 2fefb4d0-37b6-4a2b-983e-2a054055e0b4, error: Microsoft.AnalysisServices.OperationException: Failed to save modifications to the server. Error returned: 'The lock operation timed out. '. at Microsoft.AnalysisServices.Tabular.Model.SaveChangesImpl(SaveFlags flags, Int32 maxParallelism) at Microsoft.ASWL.Service.Engine.SeethruAutoSync.SeethruAutoSyncManager.<InvokeFramingAsync>d__32.MoveNext() in /_/ASWL.Service/Engine/SeethruAutoSync/SeethruAutoSyncManager.cs:line 0. |
Cluster URI: | WABI-WEST-EUROPE-E-PRIMARY-redirect.analysis.windows.net |
Activity ID: | 9e75a600-54da-4c0b-ade1-39a9fc2d23b7 |
Request ID: | 9e75a600-54da-4c0b-ade1-39a9fc2d23b7 |
Time: | 2024-03-06 05:32:08Z |
I could not find any related issues, so any help is appreciated.
Kind regards,
Siebe
Solved! Go to Solution.
Hello @Anonymous,
The problem (sort of) resolved itself. I suspect the underlying cause was capacity issues on our side. For now we can mark this post as solved.
Kind regards,
Siebe
Hi @Anonymous ,
Apologies for the issue you have been facing.
If its a bug, we will definitely would like to know and properly address it. Please go ahead and raise a support ticket to reach our support team: Link
After creating a Support ticket please provide the ticket number as it would help us to track for more information.
Thanks.
Hello @Anonymous ,
We haven’t heard from you on the last response and was just checking back to see if you have created a support ticket.
After creating a Support ticket please provide the ticket number as it would help us to track for more information.
Thanks.
Hello @Anonymous,
The problem (sort of) resolved itself. I suspect the underlying cause was capacity issues on our side. For now we can mark this post as solved.
Kind regards,
Siebe
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Fabric update to learn about new features.
User | Count |
---|---|
6 | |
4 | |
3 | |
3 | |
3 |