Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Error Message: The operation was cancelled because of locking conflicts.

Error Message:

The operation was cancelled because of locking conflicts.

 

this error goes hand in hand with:

 

Error Message:

A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread.

 

I first started seeing this error in the last 3 weeks...I haven'tseen it before then.  I've submitted at least 5 frowny face feedbacks.

 

-----

Feedback Type:

Frown (Error)

 

Timestamp:

2022-03-31T15:37:14.2245370Z

 

Local Time:

2022-03-31T08:37:14.2245370-07:00

 

Session ID:

95301c9c-9766-47f6-94c1-09596ab40e29

 

Release:

April 2022

 

Product Version:

2.104.382.0 (22.04) (x64)

 

OS Version:

Microsoft Windows NT 10.0.22000.0 (x64 en-US)

 

CLR Version:

4.7 or later [Release Number = 528449]

 

Peak Virtual Memory:

55.7 GB

 

Private Memory:

956 MB

 

Peak Working Set:

1.23 GB

 

IE Version:

11.1.22000.0

 

User ID:

xxxxx

 

Workbook Package Info:

1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: True.

 

Telemetry Enabled:

True

 

Model Default Mode:

Import

 

Model Version:

PowerBI_V3

 

Enabled Preview Features:

PBI_shapeMapVisualEnabled

PBI_enableWebView2

PBI_mobileAuthoringFormattingUI

PBI_useModernFormatPane

PBI_sparklines

 

Status: Needs Info

Hi, @mikebreen 

Which action do you perform then cause the issue occurs? Would you please share detail steps so we can understand the issue better. 

 

Best Regards,
Community Support Team _ Ailsa Tao

Comments
v-yetao1-msft
Community Support
Status changed to: Needs Info

Hi, @mikebreen 

Which action do you perform then cause the issue occurs? Would you please share detail steps so we can understand the issue better. 

 

Best Regards,
Community Support Team _ Ailsa Tao

mikebreen
Employee

Hi @v-yetao1-msft 

The error happened when loading the visual.  For example:  opening the report, adjusting a filter, clicking refresh.

 

Thanks,

Mike

v-yetao1-msft
Community Support

Hi , @mikebreen 

If a query has to wait too long to do so, then it will kill any still running queries so it can go ahead and commit those changes, and when it does, you'll see a "lock violation" error. So you need to tune your query to make it faster so you don't get errors like this . Maybe you can refer to the two documents below .

https://docs.microsoft.com/en-us/power-bi/guidance/power-bi-optimization 

https://www.tessellationtech.io/optimizing-power-bi-reports/ 

 

Best Regards,
Community Support Team _ Ailsa Tao

 

 

mikebreen
Employee

Hi @Ailsa-msft ,

 

Thanks for your help.  Your links got me to Use Performance Analyzer to examine report element performance in Power BI Desktop - Power BI | Micr..., and I was able to see the delays.  I improved the DAX for the measures, and I no longer get this error.

 

Thanks,

Mike