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

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


Community Admin

• Strategy


SYMPTOM:
When attempting to start an Intelligence Server on Linux pointing to a MySQL community Edition metadata using the supported ODBC driver in Strategy , the following error is seen:
 

ka04W000000Oh9jQAC_0EM440000002JGU.png

StartupManager (): LoadServerDef failed. Return Code: 0x80041404
  
The following entry can also be seen in the DSSError.log file:
 
Error type: Odbc error. Odbc operation attempted: SQLExecDirect. Table 'DSSMDSYSPROP' doesn't exist Connection String: DSN=XXX;UID=XXX;. SQL Statement: SELECT PROP_VAL FROM DSSMDSYSPROP WHERE NAME='SCHEMAVERSION'.
 
CAUSE:
This issue is caused by the incorrect description 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.
 
ACTION:
Modify the Description entry in odbc.ini to be exactly "MySQL ODBC 5.1 Driver", as shown below:
 
 
mysql_50_md=MySQL ODBC 5.1 Driver
.
.
 
Driver=/usr/lib/libmyodbc5.so
Description=MySQL ODBC 5.1 Driver
. 
.
 
It will then be necessary to ensure that the "Character set encoding for Unix drivers" parameter, available under the 'Advanced' tab for the database connection, is set to 'Non-UTF8'.
 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

June 1, 2017

Last Updated:

June 1, 2017