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

KB18397: ‘Metadata Server cannot connect to metadata repository…table or view does not exist’ error occurs when trying to connect to a 2-tier or 3-tier project source in MicroStrategy Developer 9.4.x - 10.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This technical note documents an error that occurs when trying to connect to a project source from MicroStrategy Developer.

SYMPTOM:
When any user, including the Strategy 'Administrator' user, tries to connect to a 2-tier or 3-tier project source in Strategy Developer 9.x - 10.x the following errors occur.
When using an Oracle database, an error as follows occurs:

ka02R000000kc99QAA_0EM440000002Era.jpeg

 


'Metadata Server cannot connect to metadata repository. Database error: Execute query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. ORA-00942: table or view does not exist'.

 

When using a Microsoft SQL Server database, an error as follows occurs:
 

ka02R000000kc99QAA_0EM440000002Erd.jpeg

 


'Metadata Server cannot connect to metadata repository. Database error: Execute query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. Invalid object name 'DSSMDSYSPROP'.'.

 
 
When using a Microsoft Access database, an error as follows occurs:
 

ka02R000000kc99QAA_0EM440000002ErW.jpeg

 


'Metadata Server cannot connect to metadata repository. Database error: Execute query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. The Microsoft Jet database engine cannot find the input table or query 'DSSMDSYSPROP'. Make sure it exists and that its name is spelled correctly.'.

 
 
CAUSE:
One of the causes for this error is because the database schema to which the Data Source Name (DSN) is pointing does not contain the Strategy Metadata tables. The user might have restored a database backup under an incorrect database schema name, one that does not contain the Strategy Metadata tables.
 
ACTION:
The user needs to make sure that the Data Source Name (DSN) is pointing to a database schema that does contain the Strategy Metadata tables. It might be necessary for the user to restore the database under the correct schema name in order to have access to the database schema that does contain the Strategy Metadata tables. Once this action has been performed, the user is able to successfully connect via a 2-tier or 3-tier project source to the Strategy Metadata and projects.
 


Comment

0 comments

Details

Knowledge Article

Published:

May 24, 2017

Last Updated:

May 24, 2017