Troubleshooting

OpenEdge 10.2A Setup install process creates registry entries under incorrect Node. In 10.2A functionality was added for 64-bit OpenEdge installs which results in the wownode is not being written to, where in previous versions (10.1B and 10.1C) it is. Jan 15, 2019 So we realized that the issue is not with the third party driver rather it is the registry key from where the ODBC Data Source Administrator (ODBCAD32.exe) actually picks up the list of drivers. The ODBC Data Source Administrator (ODBCAD32.exe) picks up the list of entries from the following registry path.

Problem

You receive the following system error code 193 when using the Microsoft ODBC Administrator to create the DataSource for Tivoli Netcool / OMNIbus on Windows 64-bit: The setup routines for the DataDirect 5.3

Symptom

Receive the error
'The setup routines for the DataDirect 5.3 <driver name> ODBC driver could not be loaded due to system error code 193.'

Cause

The driver is a 32-bit driver and the default Microsoft ODBC Administrator utility is for 64-bit drivers.

Tally Odbc Driver Not Found. Download Faster Windows 10

Resolving The Problem

On 64-bit Windows, there are two versions of the Microsoft ODBC Administrator tool. Typically, you go to Start --> Administrative Tools --> Data Sources (ODBC) to create ODBC connections. This calls the program %WINDIR%System32odbcad32.exe to create a 64-bit ODBC connection. However, this program will not create 32-bit ODBC connections.

The ODBC gateway requires a 32-bit ODBC connection. Use the 32-bit version of the Microsoft ODBC Administrator tool located in %systemdrive%WindowsSysWoW64odbcad32.exe to create the ODBC Data Source.

Tally Odbc Driver Not Found. Download Faster Version

Document Information

Tally Odbc Driver Not Found. Download Faster Than 64

Modified date:
17 June 2018