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

KB18804: After executing a ’PURGE [ALL REPORT] CACHING' script in MicroStrategy Administrator Command Manager 9.x and 10.x, History List messages return the message 'Cached report result not found in server report cache.'


Community Admin

• Strategy


After executing a ’PURGE [ALL REPORT] CACHING' script in MicroStrategy Administrator Command Manager 9.x and 10.x, History List messages return the message 'Cached report result not found in server report cache.'

SYMPTOM:
After executing a ’PURGE CACHING' script in Strategy Administrator - Command Manager 9.x and 10.x, users are not able to access any History List message.
 

ka04W000000OhLhQAK_0EM440000002BIP.jpeg

 
When opening a History List message, the following error is shown:
 

ka04W000000OhLhQAK_0EM440000002BIR.jpeg

 
Cached report result not found in server report cache. It may be deleted by server administrator.
CAUSE:
This issue occurs because the script deletes all caches regardless of the cache type. This means that caches linked to History List messages are deleted too. The full syntax for the command is as follows:
 
PURGE CACHING IN ( PROJECTS | "<project_name>");
As can be seen from the syntax there is no syntax for separating Matching, History, or both types of caches.
 
ACTION:
Instead of using the 'PURGE' command, use the 'EXPIRE' command in Strategy Administrator - Command Manager 8.x, as shown below:
 

ka04W000000OhLhQAK_0EM440000002BIW.jpeg

 
EXPIRE ( REPORT CACHES | REPORT CACHE "<cache_name>") IN PROJECT "<project_name>";
The 'EXPIRE' command will not delete the caches that are linked to History List messages, instead all caches will have the expired flag set which will clean up all 'Matching' caches and leave 'History' caches still available, as shown below:
 

ka04W000000OhLhQAK_0EM440000002BIU.jpeg

 


Comment

0 comments

Details

Knowledge Article

Published:

May 24, 2017

Last Updated:

May 24, 2017