question

JCACERES avatar image
JCACERES asked

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

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) 3- The "MyCube" cube either does not exist or has not been processed. The cube is updating every 5 minutes through a SQL Agent job with SSIS package that contain Analysis Services Processing task and the application is querying the cube every 1 minutes. I was wondering if there is any option that I can set in the SSIS package or in the Cube so it can work in parallel mode or something. ![issue1][1] ![issue2][2] NOTE: The mdx query is taking 3 minutes avg to run... [1]: /storage/temp/4565-issue1.png [2]: /storage/temp/4567-issue3.png
ssasmdxcubeolapsqlserver2014
issue1.png (2.7 KiB)
issue3.png (2.0 KiB)
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
WRBI avatar image
WRBI answered
Just looking through unanswered questions. This article may help you, although it's quite old I think it's still relevant: [Link to Article][1] Here's a excerpt in case the post ever gets destroyed... *There is an SSAS property called ForceCommitTimeout that specifies what happens to a query that is executing against the cube when the “pending commit” lock is placed, meaning these queries are blocking it from completing. ForceCommitTimeout is a signed 32-bit integer property that defines the timeout, in milliseconds, before a pending commit should cancel other commands that preceded the current command, including queries in process. The default value is 30 seconds (30000 milliseconds). If the ForceCommitTimeout has expired and there are queries still executing they are cancelled (the receive a “Server: The operation has been cancelled”) and the old version of the object is swapped out for the new one and any queries that were queued up are allowed to commence. This means that increasing the ForceCommitTimeout will give currently executing queries more time to complete. But it also means that queries that were executed soon after the “pending commit” lock was taken will be stalled for the timeout period before they even start to be executed. This will result in the perception of inconsistent performance as any queries executed during this window might take nearly twice as long to start producing results.* [1]: http://www.jamesserra.com/archive/2011/06/can-you-query-a-ssas-cube-while-it-is-processing/
1 comment
10 |1200 characters needed characters left characters exceeded

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Thank you!!!
0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.