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

KB319311: System Manager exit code “0” is returned instead of “1” when mismatches are found when using an Integrity Manager test in MicroStrategy 10.3.


Community Admin

• Strategy


This article discuss a known issue with System Manager 10.3 where it returns an incorrect exist code for "success" when the particular Integrity Manager process has found an error.

SUMMARY:
This article discuss a known issue with System Manager 10.3 where it returns an incorrect exist code for "success" when the particular Integrity Manager process has found an error.
 
SYMPTOM:
In Strategy 10.3, when using a System Manager workflow to run an Integrity Manager check, if mismatches are found, the exit code returned will be “0” (Execution succeeded with no error or mismatched object) instead of “1” (Execution completed with errors or mismatched objects.)
 
STEPS TO REPRODUCE:

  1. Obtain either two separate machines or two separate environments that will contain the same exact document. For example, the "Corporate Sales Overview" document within the Strategy Tutorial project.
  2. On machine 2, in the Tutorial Project, navigate to the "Corporate Sales Overview" (Strategy Tutorial\Public Objects\Reports\Documents and Scorecards\Corporate Sales Overview), alter the document layout, and save the changes.
  3. Within Integrity Manager, run a check against the unaltered PDF document on machine 1 and the altered PDF document on machin3 2; note that differences are found in this test. Save this run as "test.mtc."
  4. Create System Manager workflow with just the Integrity Manager process, and fill in the .mtc parameter with test.mtc from the Integrity Manager run.
  5. Notice that the error code returned is "0", indicating that the test was successful and that no changes were detected between documents, when it is supposed to be "1", since changes were made to one of the documents.

 
CAUSE:
This issue has been identified as a defect in Strategy 10.3.
 
ACTION:
This issue has been fixed in Strategy 10.9 and 10.4 Hotfix 6, please upgrade to those versions to take advantage of the fix.


Comment

0 comments

Details

Knowledge Article

Published:

April 14, 2017

Last Updated:

March 20, 2018