KB483462: An error occurs when connecting DSN from MongoDB ODBC on Windows with MicroStrategy 2019

Symptom

On Windows machines, the Intelligence server, Desktop, and Workstation are unable to successfully connect to MongoDB using a DSN created in ODBC Data Source Administrator.
When a user tests connectivity for MongoDB by using the DSN created in ODBC Data Source Administrator, an error occurs:
SQL Engine service could not be reached, falling back to Direct SQL Engine mode. 

Cause

This error appears because the MongoDB ODBC connection needs to load 

mongodb.jar

sforce.jar

mymongo64.dll

mymongo64s.dll

Solution

The explicit path of 

mongodb.jar 

sforce.jar

To set the JVM Classpath

• Open ODBC Data Source Administrator (64-bit).
• Select Create New Data Source.
• Select the driver Strategy ODBC Driver for MongoDB Client to set up as a data source.
  

• Set a separate folder for the DSN to save the schema.
  

• Select the SQL Engine tab.
• Set SQL Engine Mode to 2 - Direct.
• Manually input the JVM Classpath where 

  mongodb.jar

  and

  sforce.jar

  are stored. These files are under the ODBC folder where you installed the Strategy product.
  The JVM Classpath for products installed in the default path is:
  Windows Intelligence server: 
  

  C:\Program Files (x86)\Common Files\MicroStrategy\ODBC\mongodb.jar	C:\Program Files (x86)\Common Files\MicroStrategy\ODBC\sforce.jar

  
  Windows Desktop:
  

  C:\Program Files\MicroStrategy\Desktop\odbc\mongodb.jar	C:\Program Files\MicroStrategy\Desktop\odbc\sforce.jar

  
  Windows Workstation:
  

  C:\Program Files\MicroStrategy\Workstation\odbc\mongodb.jar	C:\Program Files\MicroStrategy\Workstation\odbc\sforce.jar

  
  

• Click Apply and OK.
• Click Test Connect.
  This process may take some time to generate the config files under the schema definition path set in step 4.
  

• Once complete, the connection should be established.