Article

The ODBC Driver will not install on Windows 64 bit

« Go Back

Information

 
EnvironmentProduct: OpenEdge
Version: All supported versions
OS: Windows 64-bit
Other: ODBC Administrator, SQL92, ODBC, JDBC
Question/Problem Description
Progress ODBC drivers do not appear in the ODBC Data Sources Administration tool.
Progress ODBC drivers are not listed when trying to add a new ODBC Data Source.
No SQL-92 ODBC Driver showing in Microsoft DSN Administrator
32-bit Progress installed on Windows 64-bit is not showing in the Windows 64-bit ODBC manager.
The drivers do not show up in the DSN Administrator
The ODBC Driver will not install on Windows 64 bit

Driver's ConfigDSN, ConfigDriver, or ConfigTranslator failed
Could not load the setup or translator library
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI is missing
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI does not show the ODBC Driver
ODBC Drivers are not being seen in the ODBC Data Source Administrator
Steps to Reproduce
Clarifying Information
No errors were detected during installation
%DLC%\installd.ini shows all JDBC and ODBC client options are set to 1
SQL Client Access product is installed.
Complete install was performed
Windows 64 bit ODBC drivers are only available as of OpenEdge 10.2A and higher 
Error MessageThe setup routines for Progress OpenEdge 10.1x driver ODBC driver could not be loaded due to system error 193
The setup routines for Progress OpenEdge 10.2x driver ODBC driver could not be loaded due to system error 193
The setup routines for the DataDirect 4.20 32-BIT OpenEdge SQL v10.0B ODBC driver could not be loaded due to system error code 193.
Defect/Enhancement Number
Cause
When the 64-bit version of Windows is running, the Progress install properly registers all ODBC drivers - they are just in a different place on x64. 

64-bit ODBC on a 64-bit Windows puts its registry entries here:
HKLM\SOFTWARE\ODBC\ODBCINST.INI
HKLM\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers, 

32-bit ODBC on 64-bit Windows puts its registry entries here:
HKLM\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI
HKLM\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\ODBC Drivers 

The 64-bit ODBC drivers can be configured from the executable here (which is the default under Administrative tools:

%SystemRoot%\system32\odbcad32.exe or %WINDIR%\System32\odbcad32.exe

The 32-bit drivers cannot be found under the 64-bit ODBC Datasource Administrator as they are created on the 32-bit side of the x64 system.
Resolution
In order to configure the 32-bit DataDirect Driver, a different DSN Administrator executable needs to be run in order to configure the 32-bit ODBC Drivers.

Create a desktop icon pointing to the following location:
%WINDIR%\SysWow64\odbcad32.exe

This will start the ODBC Data Source Administrator and from here, it is possible to configure the 32-bit ODBC drivers provided with the license installed.

(The default 64-bit DSN Administrator executable to configure 64-bit ODBC Drivers only is located %WINDIR%\System32\odbcad32.exe)
 
Workaround
Notes
References to other documentation:

Progress article(s):
P118444, How to create 32-bit ODBC DSN in 64-bit Windows machine (embedded video)
Attachment 
Last Modified Date10/6/2017 1:49 PM
Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.



Feedback
 
Was this article helpful?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful.



Characters Remaining: 255