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

KB442593: Error Occurred When uploading .mstr file with Native PostgreSQL ODBC connection to 11.x MicroStrategy Linux I-Server


Haiping Jiang

Quality Engineer, Senior • MicroStrategy


This knowledge base article describes an issue that may occur when trying to upload certain .mstr file with Native PostgreSQL ODBC connection to 11.x MicroStrategy Linux I-Server. The impact is limited to .mstr file generated from 11.x MicroStrategy Windows I-Server/Windows Workstation/Windows Desktop.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.

SYMPTOM1


When a user try to upload .mstr file with Live cube which created by using DSN DB role combined with Native PostgreSQL ODBC driver, the below error message is displayed
after he inputs username and password and clicks “Test & Save Changes” button:

ka0PW0000001JVzYAM_0EM44000000gEIx.png

 
Then the user clicks “Cancel” button and checks data in Visualization.

ka0PW0000001JVzYAM_0EM44000000gEJ7.png

 

SYMPTOM2


When a user try to upload .mstr file with In memory cube which created by using DSN DB role combined with Native PostgreSQL ODBC driver, the below error notification is displayed after he clicks “Republish Cube” button and inputs username and password:

ka0PW0000001JVzYAM_0EM44000000gEJC.png

 

CAUSE


We’re using Progress ODBC driver manager on both Windows and Linux I-Server environment. For Unicode drivers on Linux environment will use UTF-8 by default unless we set DriverUnicodeType=1 in the connection string to clarify we’re using a UTF-16 driver. Valid values for the option are 1 (UTF-16) or 2 (UTF-8).
 

ACTION


Currently, this issue is being reviewed by Strategy Technology team for a potential code fix on an upcoming Strategy release.
 

WORKAROUND


Edit the DB role and add “DriverUnicodeType=1;” at the end of the connection string, click the “Save” button in DB role configuration.
 
To find the DB role, please open the dossier which a customer uploaded, and choose “Edit Dataset” from the dataset.
 

ka0PW0000001JVzYAM_0EM44000000Rike.png

 
Then choose “Edit Table” from the table.

ka0PW0000001JVzYAM_0EM44000000Rikj.png

Edit the DB role by adding “DriverUnicodeType=1;” at the end of the connection string, click the “Save” button.

ka0PW0000001JVzYAM_0EM44000000Riko.png

  KB442593


Comment

0 comments

Details

Knowledge Article

Published:

January 16, 2019

Last Updated:

March 21, 2024