KB32047: In a clustered MicroStrategy Intelligence Server 9.4.x environment, a cache update subscription for Intelligent Cubes and an administrative task to update Intelligent Cubes, when run simultaneously results in the error “Cube instance not found"

SYMPTOM:
In a clustered Strategy Intelligence Server 9.4.x environment, updating Intelligent Cubes via an administrative task and executing a cache update subscription for the Intelligent Cubes at the same time results in the following error message in the DSSErrors.logs:
"Cube instance not found. It may have been deleted"
 
A variation of the above error message is "Cube entry is not found"
 
STEPS TO REPRODUCE:
The following steps assume a two node Strategy Intelligence Server cluster (Node A and Node B) with localized Cache, Cube and Inbox sharing.
Note: The load balance factor = 2:1 (Node A = 2; Node B = 1)
For additional information on load balance factor for subscriptions, refer to the following Strategy Knowledge Base Document below:
KB31628: How does MicroStrategy 9.x handle subscriptions

• In Strategy Desktop 9.4.x, create a simple Intelligent Cube with attribute Category and metric Revenue.
• Publish the Intelligent Cube by executing it on either of the nodes. Let us assume the Intelligent Cube is published on Node B:
  

• Create an event called "Refresh Cubes"
• Create an event-based schedule called "Refresh Cubes"
• Create a cache update subscription for the above Intelligent Cube using the event-based schedule created in Step 4 as seen below:
  

• Schedule an administrative task to "Refresh Intelligent Cubes" using the event-based schedule created in Step 4 as seen below:
  

• On Node B, trigger the "Refresh Cubes" event created in Step 3.
  
• Note: Event-based administrative tasks are executed on the node where the event is triggered.
  
• While Cube01 is executing on Node B, a report job for the same cube is created on Node A as well. This job is the result of the cache update subscription to Cube01 created in Step 5.
  Note: Since Node B had a load balance factor of 1, this job is sent to Node A.
  
• As soon as Node A starts its job execution, it acknowledges Cube01's instance on Node B and drops its own instance.
• When Node B finishes its job execution, it informs Node A but the thread that was executing the same Intelligent Cube on Node A can no longer find its cube instance and shows the following error in DSSErrors.log
  
  Sample Code/Error
  2009-11-20 12:32:26.960-05:00 Cube instance not found. It may have been deleted
  
  

 
CAUSE:
This is a known issue in Strategy Intelligence Server 9.4.x For information on other scenarios that can lead to the same issue, refer to the following Strategy Knowledge Base Documents below:
KB32047: In a clustered MicroStrategy Intelligence Server 9.0 environment, a cache update subscription for Intelligent Cubes and an administrative task to update Intelligent Cubes, when run simultaneously results in the error “Cube instance not found"
 
ACTION:
Strategy will continue to investigate and post updates as soon as they are available.