KB8621: “User request is completed. Maximum memory usage has been reached for existing objects." error message is received by users in MicroStrategy Web

SYMPTOM:
Users may receive the following possible errors when using Strategy Web:
 
Some possible errors in the Strategy Web error log:

• "Message not persisted in user inbox. Inbox may be full."
  
• "Error in report results. Your request could not be processed due to a Server error. Please try again. If the problem persists, contact the Server Administrator."
  
• "User request is completed Maximum memory usage has been reached for existing objects. It could be that the object is too big. Please try later or contact with Administrator."
   
  

Some possible errors in the DSSErrors log:

• "Error MsiWorkingSet::AddNewMsg(): failed to deposit the new message into user inbox."
  
• "Error CDSSServerMessage::get_OriginalRI: WSResultPool->GetRI for msg B8113CE811E8EBD154E30080EF7500DC return error 0x80003F79"
  
• "Error MsiWorkingSet::AttachNewRIToMsg(): GetReportInstance()"
  
• "Error CDSSServerMessage::hPersistMsgRslt: report result has been dropped"
  
• "Error in report results. Your request could not be processed due to a Server error. Please try again. If the problem persists, contact the Server Administrator."
  
• "User request is completed Maximum memory usage has been reached for existing objects. It could be that the object is too big. Please try later or contact with Administrator."
• "Pool::Add: can't add object of size xxxx because the current high memory consumption of xxxxxxKB"

CAUSE:
These errors occur because the working set Random Access Memory (RAM) has been exceeded and can no longer be accessed in order to operate with working set reports.
 
These errors can occur under two circumstances:

1. A single report instance (RI) is larger than the `Max RAM for Working Set Result Pool` setting. The single RI cannot fit into the Working Set (WS) Result Pool, so this error occurs. The same occurs when a single RI cannot fit into the RAM allocated for report cache; the report will run successfully but will not create a cache.
    
2. Not enough RIs in the WS Result Pool can be swapped to disk to make room for the new incoming RI. A RI cannot be swapped to disk if it is being utilized. At the time a user requests or manipulates a report, the RI must be put into memory and the needed amount of memory is reserved for the new RI. It will take some time to construct the RI and load it into memory and during this time, the RI cannot be swapped to disk.

 
If there are many users requesting reports at the same time (or a few users requesting large reports), then the WS Result Pool may be filled with RIs that cannot be swapped. At this time, users who request a RI may receive one of the errors above because RIs cannot be swapped to disk to make room for the new RI.
 
ACTION:
 
Increase the "Maximum RAM for Working set cache"  in the Strategy Intelligence Server Configuration as shown below:

WARNING:
Increasing the 'Maximum RAM for Working Set cache' setting will increase the possible limit amount of RAM that can be used by the Strategy Intelligence Server. Setting this to a higher limit does not mean the memory will be set aside for immediate use by the Strategy Intelligence Server. However, if needed, that limit is available, in the same way the Maximum RAM for cache settings behave.
RELATED KB ARTICLES
KB8617:  What is the 'Working Set' governor setting in Strategy Intelligence Server 2021?
KB10138:   How are the concepts of Working Set, Working Set Result Pool, History List related to each other in Strategy Intelligence Server?
KB8621