The operation was cancelled because of the locking conflicts

[creedrulz]

Dear All,

I've been trying to import data from a SQL Server Analysis Services database and receiving the following error. It appears that no matter what I try, I will not be able to get it to work.

It would be great if someone could shed some light on this matter.

Thanks,

Dee

[v-chenwuz-msft · Accepted solution]

Hi @creedrulz ,

The vast majority of the time, query timeouts cause this error. The problem is caused by long-running DAX queries the answer is to tune your queries to make them faster. please refer the following articles.

https://blog.crossjoin.co.uk/2021/10/31/understanding-the-the-operation-was-cancelled-because-of-loc... 

SQL Server Analysis Services cube processing fails with Operation canceled HY008 error | Microsoft D...

Best Regards

Community Support Team _ chenwu zhu

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[creedrulz]

@ebeery 

it worked fine on the query editor and I have managed to import once as well. Then when tried to refresh it failed with the same error.

[Dadneo]

Some of my users experience timeouts due to locks, when they have used the DAX wizzard to select thier table/view rather than coding a "select * from ..." statement. DAX tries to get a list of everything in the database catalogue, but does not specify nolocks, so often hits other tasks that might be altering indexes on completely unrelated tables. As "ebeery" states, you might knock something together, but best to do a bit of tuning. I think this needs raising as a bug fix for the DAX wizzard.

[ebeery]

@creedrulz have you verified that the query works successfully when running directly against the source (not from Power BI)?  To me, this looks more likely to be an issue with your data source or query, not with Power BI.