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
  3. KB34046: "...The object shown in the following hierarchy no longer exists in schema: -Link-TableObject is not found in DFCSchema" error message appears when updating schema in MicroStrategy

KB34046: "...The object shown in the following hierarchy no longer exists in schema: -Link-TableObject is not found in DFCSchema" error message appears when updating schema in MicroStrategy


Community Admin

• Strategy


This technical note describes an issue that occurs when updating a project schema in MicroStrategy.
When the user updates schema in MicroStrategy Developer, the error below occurs:

 

Error(s) occurred while loading schema: DSSSQLEngine: Schema loading error: Population Exception: The object shown in the following hierarchy no longer exists in schema: -Link-TableObject is not found in DFCSchema during DFC conversion.  

 This issue only happens when the option "Update schema logical information" is selected.  If the user runs ScanMD Schema Collection Verification, no inconsistency is found. 

 

CAUSE:

This issue is caused by logical table objects missing from the Schema Collection. In order to track down the cause of the inconsistency, customers encountering this issue should make note of Schema-related changes, Object Migrations, or error messages prior to experiencing the problem. Change Journaling, if it has been enabled, can help in preserving this information.

 

ACTION:

Please contact MicroStrategy Technical Support for further assistance.  Technical Support can help in identifying and re-adding the objects into their respective Schema Collection.

If you encounter this issue please make a note of any Architect work carried out (adding tables through warehouse catalog, unmapping attributes from tables), or errors encountered before the issue was seen.  Also please make a note of whether ScanMD was run in fix mode right before this issue appeared.  ScanMD saves its logs, by default, in Program Files\Common Files\MicroStrategy\Log.

 

 KB 000016683

Comment

0 comments

Details

Knowledge Article

Published:

January 31, 2024

Last Updated:

January 21, 2026