EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB15180: ‘Maximum number of caches has been reached. Cannot create new caches’ error occurs even though caching not enabled in MicroStrategy Intelligence Server


Community Admin

• Strategy


‘Maximum number of caches has been reached. Cannot create new caches’ error occurs even though caching not enabled in MicroStrategy Intelligence Server

SYMPTOM:
Even though caching is turned off in Strategy Intelligence Server, the following error occurs:
Maximum number of caches has been reached. Cannot create new caches
CAUSE:
Caches are of three types - Matching, History, and Matching, History. In all three instances, a cache file is created. So even though the user might have report caching turned off, History List messages can still deplete resources.
 
ACTION:
To resolve this error message the user can either increase the maximum number of History List messages per user or, as an administrator, can delete any old History List messages. Also if the maximum number of caches setting in the Project Configuration -> Caching -> Reports (general) is set to a small number, increasing this up to the maximum value (1000000) may also allow new caches to be created. Refer to the following Strategy Knowledge Base technical notes on how to achieve this task:
 

  • KB5656 - How to control the number of messages that can be stored in the History list in Strategy Intelligence Server
  • KB13711 - How to invalidate/delete caches and History List messages in Strategy Intelligence Server using a scheduled administration task

NOTE:

  1. Deleting History List messages through a scheduled task or directly from a users Inbox will delete the relevant cache from disk as well as memory if there are no other users history list messages pointing to this cache.
  2. If an Inbox file is deleted directly from the Inbox repository storage the messages in the file will not be retrievable. Also since deleting the file directly without going through the Intelligence Server will not update the associated cache files and the cache files will never be deleted automatically. Hence this action is not supported.


15180


Comment

0 comments

Details

Knowledge Article

Published:

June 3, 2017

Last Updated:

June 3, 2017