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

KB218721: Error received “Exception from HRESULT: 0X80041007” while updating schema in MicroStrategy Developer 2021


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This issue can be caused by invalid object caches. It impacts users who try to update schema in MicroStrategy Developer. There are solutions available for this issue in the current document.

SUMMARY:
This issue can be caused by invalid object caches. It impacts users who try to update schema in Strategy Developer. There are solutions available for this issue in the current document.
 
SYMPTOM:
When a user attempts to update the schema in Strategy Developer, the following error occurs in 2-tier and 3-tier environments:

ka0PW00000019FlYAI_0EM440000002CAo.jpeg


Exception from HRESULT: 0x80041007

CAUSE:
The issue can be caused by logical metadata inconsistencies and/or invalid object caches.  
 
ACTION:   

  1. Run ScanMD Common test to resolve metadata inconsistencies, making sure all precautionary considerations are taken before hand. Reference KB Article.
  2. If the issue persists after running ScanMD, consider to purge all object caches (Project Configuration--> Administration--> Projects --> Purge object caches) and restart I-Server

 
 ADDITIONAL TROUBLESHOOTING:
If the steps above do not resolve the issue, please contact Strategy Technical Support with the following information of troubleshooting already done:

  • Provide ScanMD logs clearly indicating the time frame when the Scan was done as well as the steps on how it was performed
  • Provide the DSSErrors.log from the Iserver after all object caches were purged and the IServer restarted.

Comment

0 comments

Details

Knowledge Article

Published:

May 17, 2017

Last Updated:

March 7, 2024