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

KB13631: Error ‘com.microstrategy.web.objects.WebObjectsException: Expected execution status 1, received status X’ occurs when running custom Java application based on Web APIs in MicroStrategy SDK 9.x


Community Admin

• Strategy


Error ‘com.microstrategy.web.objects.WebObjectsException: Expected execution status 1, received status X’ occurs when running custom Java application based on Web APIs in MicroStrategy SDK 9.x

SYMPTOM:
When running a custom Java application based on Web APIs in Strategy SDK 9.x, the following error is encountered intermittently:
 


com.Strategy.web.objects.WebObjectsException: Expected execution status 1, received status X

 
 
where 'X' is an integer.
 
This error is most often encountered when executing a report instance or when creating a new empty report instance. The error is intermittent.
 
CAUSE:
The 'execution status' refers to the interface com.Strategy.webapi.EnumDSSXMLStatus. In many cases, the next call in the application expects report results to be ready, even when empty, before trying to retrieve data or perform any type of manipulation. Depending on the Strategy Intelligence Server workload, the time it takes to retrieve the same amount of data will differ even if the report has been cached. Since, by default, report execution is asynchronous, the application will not wait for the processing on Strategy Intelligence Server to finish but will trigger the next call to be executed.
 
ACTION:
Make sure that the report execution call is synchronous. This can be done by a call to setAsynch(false) or to setMaxWait(-1). Call to setMaxWait(-1) is preferable, as shown below:
 
 

WebReportInstance rptInst = reptSrc.getNewInstance("XXX"); 
//rptInst.setAsync(false); this call is equivalent to the setMaxWait(int i) call below and could be used interchangeably
rptInst.setMaxWait(-1);
rptInst.setPollingFrequency(250); 
int status = rptInst.pollStatus(); 
WebReportData repData = rptInst.getResults();

 
 
Using setMaxWait(-1) means that the next call will not be triggered until the report returns results or errors out on Strategy Intelligence Server (exceeds governing settings etc.).
 
ADDITIONAL INFORMATION:
 
The Strategy SDK allows you to customize the standard Strategy Web interface, and extend and integrate the Strategy business intelligence functionality into other applications. However, before changing the way Strategy Web products look or behave, it is helpful to understand how the application is built. For more information regarding the Strategy Web architecture or the process of customizing Strategy Web, please refer to Strategy Developer Zone (https://resource.microstrategy.com/msdz/).
 
To access the Strategy Developer Zone, you must have access to the Strategy Knowledge Base, you must have purchased the Strategy SDK, and you must be current on your Strategy maintenance agreement. If you are a US-based business and believe that you satisfy all three of these conditions but you do not have access to the Strategy Developer Zone, please contact Strategy Technical Support at support@microstrategy.com or at (703) 848-8700. If you are an international business, please contact Strategy Technical Support at the appropriate email address or phone number found at http://www.microstrategy.com/Support/ContactUs.asp.
 
CUSTOMIZATION WARNING:
 
This customization is provided as a convenience to Strategy users and is only directly applicable to the version stated. While this code may apply to other releases directly, Strategy Technical Support makes no guarantees that the code provided will apply to any future or previous builds. In the event of a code change in future builds, Strategy Technical Support makes no guarantee that an updated version of this particular customization will be provided. In the event of a code change in future builds, Strategy may not be able to provide additional code on this matter even though this customization is provided at this time for this specific build. For enhancements to this customization or to incorporate similar functionality into other versions, contact your Account Executive to inquire about Strategy Consulting assistance.


Comment

0 comments

Details

Knowledge Article

Published:

June 15, 2017

Last Updated:

June 15, 2017