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

KB484598: Live connection dossiers against MDX data sources in the hybrid History List cannot be executed after they are created in the MicroStrategy 2020 Update 2


Karol Marczuk

Consultant • Strategy


This article describes a known issue with the execution of live connection dossiers against MDX data sources after they are created in MicroStrategy 2020 Update 2.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.

Description


After sending a dossier into the History List, it should open correctly on the same day of creating it. However, on Strategy 2020 Update 2, the same dossier returns the following error a day after its creation.
User request is completed.
MsiInBox: The persist message result, either a persisted report definition, a report result in report cache or a document result file, is not found. It may have been manually deleted by system administrator.
 

ka0PW0000001JefYAE_0EM4W000001Iyhl.jpeg

Steps to reproduce

  • Set History Lists as Hybrid.
ka0PW0000001JefYAE_0EM4W000001Iyhz.jpeg
  • Create a couple of test dossiers.
  • Add them to the History List by going to File > Add to History List.
  • In Strategy Web, go to History List and execute any of the History Lists messages. None of them return errors.
  • Check the History List again the next day. You can see that they return errors now.
ka0PW0000001JefYAE_0EM4W000001Iyi4.jpeg

Why is this happening?


This is an identified limitation in Strategy version 2020 Update 2.

Solution

This issue has been addressed in Strategy 2021. Please upgrade to take advantage of this fix.

Workaround


Change the History Lists to be database based only.


Comment

0 comments

Details

Knowledge Article

Published:

October 4, 2020

Last Updated:

March 21, 2024