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

KB38136: "The object shown in the following hierarchy no longer exists in schema: -RoleObject is not found in DFCSchema during DFC conversion." error is thrown when updating the schema in MicroStrategy Desktop 9.3.x to 9.4.0 and Developer 9.4.1 and above.


Stefan Zepeda

Salesforce Solutions Architect • Strategy


"The object shown in the following hierarchy no longer exists in schema: -RoleObject is not found in DFCSchema during DFC conversion." error is thrown when updating the schema in MicroStrategy Desktop 9.3.x to 9.4.0 and Developer 9.4.1 and above.

SYMPTOM:
Users observe that the following error occurs when trying to update schema through Strategy Desktop 9.0.x - 9.2.x in either 2-tier or 3-tier mode:
 
 


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

 
Moreover if ScanMD is run then the Attribute Verification common test in ScanMD 8.000.008 detects this inconsistency but is unable to fix it. The following entries can be seen in the ScanMD log:
 

: Transformation Attribute {'\<Project Name>\System Objects\Transformation Attributes\<Transformation attribute name>' with ID }'s attribute forms collection is empty.]

 
CAUSE:
One possible cause of this issue is that the definition of one or more system object(s) associated with transformations has become inconsistent.  
 
ACTION: 
Contact Strategy Technical Support with a backup of the metadata storing the project with this issue for further assistance with this issue.
 
NOTE: 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.
 


Comment

0 comments

Details

Knowledge Article

Published:

May 11, 2017

Last Updated:

May 11, 2017