KB31561: History List messages for users are not synchronized across all nodes if they have an active session while a clustered environment disconnects and reconnects a node in MicroStrategy 9.x.

SYMPTOM
In a Strategy Intelligence Server 9.x clustered environment, History List messages are not synchronized across all nodes of the cluster if one node leaves and re-joins the cluster while there are active user sessions on the servers.
STEPS TO REPRODUCE
The following steps are for a Strategy 9.x clustered environment on Windows with two Intelligence Servers. The nodes are named Node A and Node B. The cluster is set up with localized Cache/Intelligent Cube/Inbox sharing.
 

• In Strategy Desktop, log into Node A as user "Administrator" and send Report A to history.
• The History List message can be seen in the Administrator's Inbox on both the nodes.
  

• On Node A, go to "Cluster Nodes" under "System Administration". Remove Node B from the cluster as seen below:
   
  

• From Node A, send Report B to history.
• The Administrator's Inbox on Node A now has 2 History List Messages.
• Re-join Node B into Node A 's cluster.
• From each node check the Administrator's Inbox and notice the number of History List messages on Node A are different from Node B.
   
  

 
CAUSE
This is working as designed. Strategy Intelligence Server cluster configuration changes should only be made when the system is idle and there are no active user sessions in the cluster.
An enhancement has been logged to display a warning message when the administrator tries to make changes to a cluster while there are active user sessions on the Intelligence Servers.
ACTION
As long as the user sessions are created after the Intelligence Server cluster nodes are joined with each other, History List messages will be synchronized across all nodes of the cluster.