Server: The operation was cancelled because of locking conflicts (Analysis Services)

▲
2
▼

I have a report application that is connected to an Olap cube in Analysis Services and every time that the application query the cube while the cube is processing I'm getting these errors:

1-Server:The operation was cancelled because of locking conflicts.

2-'MSOLAP' failed with no error message available, result code: E_FAIL(0x80004005)

The cube is updating every 10 minutes through a SQL Agent job with SSIS package that contain Analysis Services Processing task and the application is querying the cube every 15 minutes.

I was wondering if there is any option that I can set in the SSIS package or in the Cube.

enter image description here

enter image description here

sql-server
ssis
ssas
mdx
olap-cube
asked on Stack Overflow Feb 23, 2018 by JC_BI • edited Feb 23, 2018 by Tab Alleman

2 Answers

▲
0
▼

If you want to avoid this problem I suggest you process a copy of the cube on another instance or server and then synchronise the processed cube to the server queried by your application.

This will prevent future locking problems and be invisible to the end user.

answered on Stack Overflow Feb 25, 2018 by MrHappyHead
▲
0
▼

ForceCommitTimeOut Property of SSAS Tabular model is similar to the property in the multi dimensional model. These proerties are in milliseconds, so you can reproduce this issue in a functional environment by bringing down the value to 100ms, which would mean 1 second. The solution to this problem is to increase the value in this property to 0, which would mean wait until a lock is released. ForceCommitTimeOut Property of SSAS Tabulare

answered on Stack Overflow Apr 7, 2021 by Dave Kapoor

User contributions licensed under CC BY-SA 3.0