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

KB403143: "Unexpected execution status" error message appears when using URL API to execute a report services document with a default selector value in MicroStrategy Web.


Community Admin

• Strategy


"Unexpected execution status" error message appears when using URL API to execute a report services document with a default selector value in MicroStrategy Web.

SYMPTOM:
Users may follow the instructions in tech note KB39871 to construct a URL using the URL API to select a default selector value on document execution for a report services document in Strategy Web 9.x. However, sometimes users may see the error message shown below:
 

ka04W00000148WzQAI_0EM4400000026a7.png

 


Error in document results

Unexpected execution status: 4

 
Despite the error message, the document may still successfully execute. 
 
CAUSE:
The URL that is constructed by following tech note KB39871 contains two events: event 2048001, which executes the document, and event 2048084, which sets the selector value. The order in which these events are executed is specified by the evtorder parameter. While the order of execution may have been specified correctly in the evtorder parameter, the timing of the events may not be. If the second event of setting the selector value is executed before the first event of executing the document is completed, then this error message will occur. Because there is no way to specify the timing of when the events are executed, this behavior is working as designed but an enhancement request has been logged to address this issue.
 
WORKAROUND:
Consider troubleshooting the dashboard for performance such that it returns quicker to avoid this issue, for more information refer to tech note KB19625: Dashboard performance troubleshooting in MicroStrategy 9.x.
Or, make sure the document is cached beforehand so instead of performing a full execution, the document hits its cache.

KB403143


Comment

0 comments

Details

Knowledge Article

Published:

April 7, 2017

Last Updated:

November 13, 2018