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

KB486762: MicroStrategy Out-of-the-Box Exasol and Teradata Driver Install and Uninstall Behavior Reference


Yao Fu

Quality Engineer, Senior • MicroStrategy


The MicroStrategy shipped Exasol driver uses the same name as the native driver in all platforms. The drivers may overwrite each owner's registry key. Use the following options to ensure registry keys are not overwritten.

Symptom


Strategy ships the native Exasol ODBC driver out-of-the-box. The driver was renamed to Exasol Driver on all platforms (including Strategy Workstation). This is the same driver name id a user manually installs the Exasol ODBC driver from the installer download from the Exasol website.
In some cases, a user may install the Strategy Platform and Strategy Workstation on the same Windows machine (however, this is not the best practice that Strategy recommends). To provide consistent user experience and avoid conflict in the registry key, use the following install and uninstall behavior:
Case 1: Install the Strategy Platform first, then install Strategy Workstation. The registration keys point to the Workstation install like the following:

Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Exasol Driver]"UsageCount"=dword:00000001"Description"="Exasol 24.1.0 ODBC driver x64""Driver"="C:\\Program Files\\MicroStrategy\\Workstation\\ODBC\\Exasol\\EXAODBC.dll""Setup"="C:\\Program Files\\MicroStrategy\\Workstation\\ODBC\\Exasol\\EXAODBCConfig.dll""Company"="EXASOL AG""DriverODBCVer"="03.52""ConnectFunctions"="YYN""InstallDir"="C:\\Program Files\\MicroStrategy\\Workstation\\ODBC\\Exasol\\"

Case 2: Install Workstation first, then install the Strategy Platform. The registry keys point to the Strategy Platform installation like the following:
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Exasol Driver]"Description"="Exasol 24.1.0 ODBC driver x64""Driver"="C:\\Program Files (x86)\\Common Files\\MicroStrategy\\ODBC\\Exasol\\EXAODBC.dll""Setup"="C:\\Program Files (x86)\\Common Files\\MicroStrategy\\ODBC\\Exasol\\EXAODBCConfig.dll""UsageCount"=dword:00000001"Company"="EXASOL AG""DriverODBCVer"="03.52""ConnectFunctions"="YYN""InstallDir"="C:\\Program Files (x86)\\Common Files\\MicroStrategy\\ODBC\\Exasol"

Case 3: Install the Strategy Platform first, then install Workstation. After that, uninstall Workstation and the registry keys point to the Strategy Platform install like the following:
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Exasol Driver]"Description"="Exasol 24.1.0 ODBC driver x64""Driver"="C:\\Program Files (x86)\\Common Files\\MicroStrategy\\ODBC\\Exasol\\EXAODBC.dll""Setup"="C:\\Program Files (x86)\\Common Files\\MicroStrategy\\ODBC\\Exasol\\EXAODBCConfig.dll""UsageCount"=dword:00000001"Company"="EXASOL AG""DriverODBCVer"="03.52""ConnectFunctions"="YYN""InstallDir"="C:\\Program Files (x86)\\Common Files\\MicroStrategy\\ODBC\\Exasol"

Case 4: Install Workstation first, then install the Strategy Platform. After that, uninstall the Strategy Platform and the registry keys point to the Workstation install like the following:
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Exasol Driver]"UsageCount"=dword:00000001"Description"="Exasol 24.1.0 ODBC driver x64""Driver"="C:\\Program Files\\MicroStrategy\\Workstation\\ODBC\\Exasol\\EXAODBC.dll""Setup"="C:\\Program Files\\MicroStrategy\\Workstation\\ODBC\\Exasol\\EXAODBCConfig.dll""Company"="EXASOL AG""DriverODBCVer"="03.52""ConnectFunctions"="YYN""InstallDir"="C:\\Program Files\\MicroStrategy\\Workstation\\ODBC\\Exasol\\"

Case 5: Install the Strategy Platform first, then install Workstation. After that, uninstall the Strategy Platform and the registry keys point to Workstation like the following:
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Exasol Driver]"UsageCount"=dword:00000001"Description"="Exasol 24.1.0 ODBC driver x64""Driver"="C:\\Program Files\\MicroStrategy\\Workstation\\ODBC\\Exasol\\EXAODBC.dll""Setup"="C:\\Program Files\\MicroStrategy\\Workstation\\ODBC\\Exasol\\EXAODBCConfig.dll""Company"="EXASOL AG""DriverODBCVer"="03.52""ConnectFunctions"="YYN""InstallDir"="C:\\Program Files\\MicroStrategy\\Workstation\\ODBC\\Exasol\\"

Case 6: Install Workstation first, then install the Strategy Platform. After that, uninstall Workstation and the registry keys point to the Strategy platform like the following:
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Exasol Driver]"Description"="Exasol 24.1.0 ODBC driver x64""Driver"="C:\\Program Files (x86)\\Common Files\\MicroStrategy\\ODBC\\Exasol\\EXAODBC.dll""Setup"="C:\\Program Files (x86)\\Common Files\\MicroStrategy\\ODBC\\Exasol\\EXAODBCConfig.dll""UsageCount"=dword:00000001"Company"="EXASOL AG""DriverODBCVer"="03.52""ConnectFunctions"="YYN""InstallDir"="C:\\Program Files (x86)\\Common Files\\MicroStrategy\\ODBC\\Exasol"

Case 7: User may have already installed the native Exasol driver and then installed Strategy products. Because drivers share the same name, the registry keys point to the Strategy installation path. The old DSNs based on the self-installed driver can still be used. If the user uninstalls Strategy, the old DSNs become unstable.

Cause

This behavior is due to the Strategy shipped Exasol driver uses the same name as the native driver in all platforms. The drivers may overwrite each owner's registry key.

Action

In Case 1 through Case 6, there is no action needed. In Case 7, once the user installs Strategy again, the DSNs become usable.


Comment

0 comments

Details

Knowledge Article

Published:

May 14, 2024

Last Updated:

June 21, 2024