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

KB38755: "Metadata server initialization failed because the "VERSION" property in table "DSSMDSYSPROP" is missing or valid" error message appears when configuring a metadata using MySQL Community database in MicroStrategy on Linux platforms


Community Admin

• Strategy


SYMPTOM:
 
When creating metadata tables in the Configuration Wizard against a MySQL Community database on a Linux Intelligence Server, an error message appears after entering the DSN name and password in Strategy 9.x - 10.x universal, as shown below:
 
Sample Code/Error
An error occurred while creating a default Metadata configuration:
(Metadata server initialization failed because the 'VERSION' property in table 'DSSMDSYSPROP' is missing or invalid. You may be trying to connect to a metadata repository version unsupported by this release. Please contact your system administrator. )
 
 
Go on configuring the Intelligence server in the configuration wizard, after entering Strategy authentication, the same error appears, as shown below:
 
Sample Code/Error
An error occurred while creating a default Metadata configuration:
Server Definition manipulations error: Metadata server initialization failed because the 'VERSION' property in table 'DSSMDSYSPROP' is missing or invalid. You may be trying to connect to a metadata repository version unsupported by this release. Please contact your system administrator.
 
In the DSSError.log, there are a lot of entries like the below:
 
Sample Code/Error
Execute Query failed. Error type: Odbc error. Odbc operation attempted: SQLExecDirect. Unknown table 'DSSMDSYSPROP' Connection String: DSN=***;UID=***;. SQL Statement: DROP TABLE DSSMDSYSPROP.
 
In the MACfgWiz.xml file, there are a lot entries like the below:
 
Sample Code/Error
<log4j:event logger="MACfgWiz" timestamp="1323174934012" level="DEBUG" thread="SwingWorker-pool-1-thread-4">
<log4j:message><!]></log4j:message>
<log4j:throwable><! Unknown table 'DSSMDSYSPROP'
 at com.Strategy.tools.MADbJniDriver.MADbJniStatement.nativeExecute(Native Method)
 at com.Strategy.tools.MADbJniDriver.MADbJniStatement.execute(Unknown Source)
 at com.Strategy.tools.MADbJniDriver.MADbJniStatement.executeUpdate(Unknown Source)
 at com.Strategy.tools.macfgwiz.backbone.common.CfgWizConnection.executeStatement(Unknown Source)
 at com.Strategy.tools.macfgwiz.backbone.repository.MDConfigOpImpl.executeScript(Unknown Source)
 at com.Strategy.tools.macfgwiz.backbone.repository.MDConfigOpImpl.run(Unknown Source)
 at com.Strategy.tools.macfgwiz.ui.common.ConfigurationProcedure.submit(Unknown Source)
 at com.Strategy.tools.macfgwiz.ui.common.CfgWizArchitect.submit(Unknown Source)
 at com.Strategy.tools.macfgwiz.ui.graphic.steps.SummaryStep$ConfigurationExecutor.doInBackground(Unknown Source)
 at com.Strategy.tools.macfgwiz.ui.graphic.steps.SummaryStep$ConfigurationExecutor.doInBackground(Unknown Source)
 at javax.swing.SwingWorker$1.call(Unknown Source)
 at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
 at java.util.concurrent.FutureTask.run(Unknown Source)
 at javax.swing.SwingWorker.run(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)
]]></log4j:throwable>
</log4j:event>
 
Connecting to the metadata in DB Query tool shows all metadata tables, but no server definition can be found in the tables.
 
CAUSE:
 
An incorrect description is used for the MySQL Community Edition ODBC driver in the odbc.ini file. If the description for the ODBC DSN does not match "MySQL ODBC 5.1 Driver", the Strategy metadata connectivity layer will expect the data from the driver to be in UTF-8 format whereas the driver uses a UTF-16 character set by default. The cause is similar to KB37790.
KB37790: "StartUpManager (): LoadServerDef failed. Return Code: 0x80041404" error occurs when attempting to start an Intelligence Server pointing to a MySQL Community Edition metadata using the supported ODBC driver in MicroStrategy on a Linux platf
 
ACTION:
 
Modify the Description entry in odbc.ini to be exactly "MySQL ODBC 5.1 Driver", as shown below:
 
Sample Code/Error
 
MySQL=MySQL ODBC 5.1 Driver
 
.
 
Driver=/usr/lib/libmyodbc5.so
Description=MySQL ODBC 5.1 Driver
 
.
. .
 
 
  
 
 


Comment

0 comments

Details

Knowledge Article

Published:

June 1, 2017

Last Updated:

June 1, 2017