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

KB37554: "Unknown exception caught (in COM methods)" error is thrown when updating the schema in MicroStrategy Developer 9.x and above


Stefan Zepeda

Salesforce Solutions Architect • Strategy


"Unknown exception caught (in COM methods)" error is thrown when updating the schema in MicroStrategy Developer 9.x and above.

SYMPTOM:

When a user tries to update the schema through Strategy Developer 9.x and above, the following error is thrown:
---------------------------
Strategy Developer
---------------------------
Unknown exception caught (in COM methods)
This error is thrown using both a two-tier or a three-tier connection.

CAUSE:

Cause 1: This error is thrown when the machine performing the update schema runs out of memory. The memory usage required to update schema increases as more tables are added to the Warehouse Catalog. Therefore, having a large number of source tables is a common cause for this error.
Cause 2: Another probable reason for this error is that Intelligence Server has very old Intelligent Cube cache (around 2+ years) and the schema of the project becomes very inconsistent with the Intelligent Cube cache.
Cause 3: Another possible reason for this error is that Intelligence Server has a problematic Intelligent Cube cache stored in memory.

ACTION:

Action 1: Users should try to increase the memory available for the Developer process. If the schema is being updated on a 32 bit machine, the user may want to consider moving to a 64 bit environment which would utilize more memory for the Developer process.  Moreover, if the Intelligence Server and Developer applications reside on the same machine it is strongly recommended to separate them.
Action 2: Verify whether Intelligence Server has very old Intelligent Cube caches and republishing those Intelligent Cubes can resolve this error.
Action 3: Perform a binary search of unloading cubes from memory to identify the specific cube cache(s) leading to the issue. Once identified, deleting and republishing these cubes can resolve this error.


Comment

0 comments

Details

Knowledge Article

Published:

June 13, 2017

Last Updated:

August 29, 2024