Share via

SSAS Synchronization locking(?) issue

Stefan 196 Reputation points
2020-09-28T11:49:39.573+00:00

Hi,
We are running SSAS Tabular (2019, same issue on 2017)
We have an environment with one server acting dedicated as a processing server (we can call it server 1) and another one dedicated for user query load (we can call it server 2).
Multiple times during the day the cube at server 1 is being processed and then there is a standard SSAS synchronization synching the changes out to server 2.
The synch is perform at the same time when there is query load on server 2.

This scenario often works fine, however some times the synchronization job fails and the error messages below can be found in msmdsrv.log at server 2.

Message: File or folder '\?\xx:\OLAP\Data\my_cube.version.db' could not be moved. It may be locked by indexing or antivirus software. (Source: \?\xx\msmdsrv.log, Type: 3, Category: 289, Event ID: 0xC1210021)

Message: An error occurred at critical stage of transaction; we intercepted it, but have to terminate the process. (Source: \?\L:\OLAP\Log\msmdsrv.log, Type: 3, Category: 289, Event ID: 0xC1210058)


The ForceCommitTimeout is set to the default value = 30000 = 30 sec.
Is this locking issue due to long running user queries or can it be some other problem? I thought that setting ForceCommitTimeout to 30 sec would mean that any query running against the cube would be killed after that time period.

SQL Server Analysis Services
SQL Server Analysis Services
A Microsoft online analytical data engine used in decision support and business analytics, providing the analytical data for business reports and client applications such as Power BI, Excel, Reporting Services reports, and other data visualization tools.
1,290 questions
0 comments
Accepted answer
  1. Darren Gosbell 2,376 Reputation points
    2020-09-28T23:21:34.737+00:00

    Is this locking issue due to long running user queries or can it be some other problem? I thought that setting ForceCommitTimeout to 30 sec would mean that any query running against the cube would be killed after that time period.

    This is almost certainly some other issue, not a query locking issue. Query locks are maintained internally at a level above the file system. The issue you are seeing is most likely caused by some other process on the system (as the error says this could be indexing or AV software). So I would check if you are running any of those services and see if you can exclude the SSAS data folders from being scanned by them.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Lukas Yu -MSFT 5,821 Reputation points
    2020-10-02T03:20:17.52+00:00

    Hi,
    Have you resolved your issue ? If yes, you could mark useful post as answer, if not, could you inform us what's now the issue is ?

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.