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

KB18752: ’Method `~` of object `~` failed’ error message appears when performing an ’Update Schema’ operation in MicroStrategy Developer 9.4.x-10.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This knowledge base article explains why ’Method `~` of object `~` failed’ error message appears when performing an ’Update Schema’ operation in MicroStrategy Developer 9.4.x-10.x

SYMPTOM:
When performing an 'Update Schema' operation in Strategy Developer 9.4.x-10.x, users see one of the following three error messages:
 


Method `~` of object `~` failed

End of Stream

There is an unknown exception in the COM method

The error may prevent the 'Update Schema' from being successfully completed.
 
CAUSE:
If the issue is found to be machine independent, a metadata inconsistency could be the cause of it.
 
ACTION:
To resolve this issue, users should first try running the latest version of Scan MD against the project in check mode to determine if Scan MD may be able to correct the issue. For information on how to download and use Scan MD, see KB483179: Using ScanMD to fix known logical metadata inconsistencies in the MicroStrategy Product Suite 2019 and later.
 
If Scan MD is unable to detect an inconsistency relevant to the issue, it may be possible to identify the object or objects causing the difficulty by enabling an additional diagnostic setting. Follow the steps outlined below:
 

  • Open the Diagnostics Configuration located under Programs -> Strategy -> Tools -> Diagnostics Configuration, as shown below:
ka04W000001IrM0QAK_0EM440000002EqP.jpeg
  • Change the Configuration to Machine Default, as shown below:
ka04W000001IrM0QAK_0EM440000002Eq9.jpeg
  • Scroll to Engine -> DFC Engine Trace, drop down the file log and select <New>, as shown below:
ka04W000001IrM0QAK_0EM440000002Eq5.jpeg
  • Name the new log DFC_Engine_Trace and enter a log file size. Then click OK, as shown below:
ka04W000001IrM0QAK_0EM440000002Eq4.jpeg
  • Save the changes in Diagnostics and reproduce the issue. A log file called DFC_Engine_Trace.log is generated in C:\Program Files\Common Files\MicroStrategy\Log. The log file shows detailed information about the objects being accessed during the update schema. Scroll to the bottom of the log and determine which object was being accessed at the time of the unexpected error.
  • Contact Strategy Technical Support with the generated log for further assistance.

 


Comment

0 comments

Details

Knowledge Article

Published:

June 6, 2017

Last Updated:

September 13, 2021