Did this article resolve your question/issue?



System Error 193 when configuring the 10.2A ODBC driver on Windows 64-bit

« Go Back


TitleSystem Error 193 when configuring the 10.2A ODBC driver on Windows 64-bit
URL NameP141118
Article Number000136398
EnvironmentProduct: OpenEdge
Version: 10.2A
OS: Windows 64-bits
Other: Install
Question/Problem Description
System Error 193 when configuring the 10.2A ODBC driver on Windows 64-bit.
Creating a User or System DSN fails with  system error 193.

The 10.2A ODBC driver does not appear in the 32-bit version of the ODBC Administrator tool.
The ODBC driver is listed in the 64-bit Data Source Administrator.

The legacy ODBC Data Source Administrator does not show the odbc driver 32 bits using %WINDIR%\SysWow64\odbcad32.exe

Steps to Reproduce
Clarifying Information
The 32-bit ODBC driver is listed in the 64-bit version of ODBC Data Source Manager.
The 32-bit ODBC driver is not listed in the 32-bit ODBC Data Source Manager.
Error MessageThe setup routines for Progress OpenEdge 10.2A driver ODBC driver could not be loaded due to system error 193
Could not load the setup or translator library
Defect/Enhancement NumberDefect PSC00210706 / OE00180895
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.  

Installation created ODBC driver registry keys in:

The ODBC driver is not created in the wownode as it should:
Upgrade to OpenEdge 10.2B or later, where the installation detects "if bits=64" then writes to the 64 bit registry or the wownode as appropriate.
Choose one of the following set of steps to create the necessary registry keys. 
Make sure there is a valid backup of the registry before modifying it.

1)  Create a .REG file, and copy the lines below:

Windows Registry Editor Version 5.00

"Progress OpenEdge 10.2A driver"="Installed"


Note: [DLC] should refer to the 10.2A installation directory. For example: C:\\progress\\openedge

2)  Save the file, and double-click on it in order to add the keys into the registry.


1)  Open Regedit (windows start - > programs -> run -> regedit.exe)
3)  Right-click on ODBC Drivers and select export.
4)  Save in a file xx.reg
5)  Edit xx.reg and add Wow6432Node to the line 


The changed / edited line should show:


6)  Save xx.reg
7)  Again from regedit go [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Progress OpenEdge 10.2A Driver]
8)  Right-click on Progress OpenEdge 10.2A Driver and select export.
9)  Save in a file yy.reg
10)  Edit yy.reg and add Wow6432Node to the line 


The changed edited line should show:


11)  Save yy.reg

12)  Import xx.reg using import option from Register Editor (File -> import)

13)  Import yy.reg using import option from Register Editor (File -> import)

From this point on, use the 32-bit ODBC Data Source Administrator to add/configure your User or System DSN:


Last Modified Date11/20/2020 7:33 AM
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.