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
  3. Topics

KB483727: Document/dossier execution fails, or shows some failed visualizations, or wrong data after upgrade to 11.0 or m2019GA/U1/U2

Linbao Zhang

Senior Consultant • MicroStrategy

When the customer upgrades to 11.0 or m2019GA/U1/U2, some documents/dossiers with double-type attribute ID may show wrong data or execution fail with the error message like "System Error 0x00000001 (1) --- Incorrect function", "System Error (EPERM) – Operation not permitted", "User request is completed ()" , or "Document execution fails. Error initializing data model from document instance" shown in DSSErrrors log. The issue has been fixed in m2019U3 or m2020. The issue CANNOT be resolved by changing the data engine version.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
DESCRIPTION
When the user upgrades to 11.0 or m2019GA/U1/U2, they may observe some regression issues on the multi-dataset documents/dossiers which has double-type attribute IDs. The symptoms may vary including

  1. Visualization failed with the error shown "System Error 0x00000001 (1) --- Incorrect function",
  2. Visualization failed with the error shown "System Error (EPERM) – Operation not permitted",
  3. Document execution failed with the error shown "Error initializing data model from document instance",
  4. Document execution failed with the error shown "User request is completed ()",
  5. Wrong data returned when filtering involving double-type attribute IDs.


Additional troubleshooting steps can show the issue is gone sometimes when some dataset is removed from the document/dossier.
CAUSE
This regression issue is caused by the double-type data comparison rule change we made in 11.0 (Articles KB442283). Due to the limitation of some WH, e.g. Oracle. Strategy has to support double-type attribute IDs comparison.
ACTION
The issue has been addressed in m2019U3 and m2020. The customer needs to upgrade to these new releases to pick up the fix.
Strategy Internal Reference Number for this technical note is KB483727 and DE144717

Comment

0 comments

Details

Knowledge Article

Published:

October 13, 2019

Last Updated:

March 21, 2024