Feedback
 
Did this article resolve your question/issue?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025

 


Article

Getting error 126 attempting to setup 32-bit ODBC drivers on Windows 64-bit system.

« Go Back

Information

 
Article Number000045866
EnvironmentProduct: OpenEdge
Version: 11.3.1
OS: Windows 8
Question/Problem Description
Getting error 126 attempting to configure 32-bit odbc drivers on windows 8 64-bit system with 64-bit OpenEdge.

User attempted to manually create ODBC driver entries in registry because 32-bit driver registry were missing at the point the user attempted to setup data source.
Steps to Reproduce
Clarifying Information
In 11.3.1 the 64-bit installation installs both 64-bit and 32-bit ODBC drivers.
Error MessageThe setup routines for the progress OpenEdge 11.3 driver ODBC driver ODBC driver could not be loaded due to system error code 126.
Defect/Enhancement Number
Cause
When creating registry keys manually for the 32-bit ODBC drivers the wrong driver file name was entered in the registry key.
Resolution
If there is no listing of the "Progress OpenEdge 11.3 Driver" in the 32-bit ODBC Data Source Administrator (this tool is typically found in c:\windows\syswow64\odbcad32.exe) then it will be necessary to verify the driver files have been intalled and create the entries for the driver in the Windows registry.
 
1)  The files that are part of the ODBC driver interface should be located in the <OpenEdge Installation Directory>\bin32.
The file names are:
pgodbc.lic
pgicu27.dll
pgssl27.dll
pgoe27.dll1
pgoe27r.dll
pgtrc27.dll
 
2) The following can be used to create an odbc_32-bit_install.reg file this presumes the installation was made into c:\Progress\OpenEdge.
Adjust the references to the directory as necessary.  Wherever double slash marks are listed, maintain that syntax so that Windows will enter the paths correcty in the registy (the first slash is treated as an escape sequence character so the second slash is not modified by regedit):
 
Windows Registry Editor Version 5.00
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\ODBC Drivers]
"Progress OpenEdge 11.3 Driver"="Installed"
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBCINST.INI\Progress OpenEdge 11.3 Driver]
"Driver"="C:\\Progress\\OpenEdge\\bin32\\pgoe27.dll"
"Setup"="C:\\Progress\\OpenEdge\\bin32\\pgoe27.dll"
"DriverODBCVer"="3.52"
"APILevel"="1"
"ConnectFunctions"="YYN"
"CPTimeout"="60"
"FileUsage"="0"
"SQLLevel"="0"
"UsageCount"="1"
 
Notice the key points to the Wow6432Node - this registry hive allows 32 bit applications to live alongside 64 bit applications. Adding the keys here ensures  that  the previously created ODBC keys in the 64 bit space will not be overwritten
 
 
3) Import the 32 Bit ODBC Registry Key 
Double click on the odbc_32-bit_install.reg file, and follow the prompts so it will be imported correctly.
 
4) Confirm the driver is set up correctly
Run the 32-bit ODBC administrator (%windir%\SysWOW64\odbcad32.exe).
 
5)  Click on the add button.  Scroll down if necessary to verify that the Progress OpenEdge 11.3 ODBC driver is now visible in the list.
 
Workaround
Notes
The registry entries for the 32-bit drivers should have been created during the installation.
It is unknown why the registry entries were not in existence at the point of failure.
Attachment 
Last Modified Date2/21/2018 3:16 PM