Did this article resolve your question/issue?



DataDirect Setup routines for the driver could not be loaded due to system error 126 or 1157

« Go Back


TitleDataDirect Setup routines for the driver could not be loaded due to system error 126 or 1157
URL Name3052
Article Number000147908
EnvironmentProduct: Connect for ODBC
Version: All supported versions
OS: Windows
Database: All supported databases
Application: All ODBC applications
Question/Problem Description
These errors occur when trying to connect or when configuring a Connect for ODBC data source using the ODBC Administrator tool.
It occurs when one or more of these conditions is true:
1. The desired driver has not been installed
2. The required database-specific client software has not been installed
3. The system path does not include the database-specific client software and/or the driver
Steps to Reproduce
Clarifying Information
Error MessageSetup routines for the driver could not be loaded due to system error 126
Setup routines for the driver could not be loaded due to system error 1157
Defect/Enhancement Number
This error message means that one or more of the files required to load the driver could not be located. This could be a driver file(s) or a database client software file (s).

1. Is the correct driver installed?

Make sure that the name of the Connect for ODBC driver you configure in your ODBC data source is actually the one which you need to connect to your database. During installation you might have selected the wrong driver or accepted the default (first driver in the list: Btrieve) driver to be installed.

You can see the name of the driver you have installed in the ODBC Administrator tool in the 'Driver' field next to the 'Name' field of your ODBC data source. Also when configuring the Connect for ODBC driver, the title bar of the window usually shows the name of the ODBC driver you are configuring. Under the Drivers tab, you'll see a list of the installed ODBC drivers.

If you have installed the incorrect driver, uninstall the DataDirect software via Control Panel and install it again, this time making sure to install the driver of your choice.

2. Appropriate client software installed?

For each database, search for the below listed file on the machine where you have installed the Connect for ODBC driver to ensure the required database specific client software has been installed.

Note that this is only one of the database specific client software files that will be used by the Connect for ODBC driver and as such you should not copy just this single file from one to another machine, but instead perform a full installation of the database specific client software onto each machine on which you want to use the Connect for ODBC driver.

The file names listed below are provided only as a search term to help you locate the client software installation.

 Informix Informix Client SDK ISQLT09a.dll
 Oracle SQLNet(for 7x)
 Net 8 (for 8x)
 Paradox Borland DB Engine IDAPI32.dll
 Pervasive SQL 2000Pervasive.SQL 2000 client software 
 Pervasive SQL 7.0Pervasive.SQL 7.0 client software 
 Btrieve 6.15 for Windows 9xBtrieve Developer's Kit or
Btrieve WorkStation Client Engine
 Btrieve 6.15 for Windows NTBtrieve Developer's Kit,
Btrieve WorkStation Client Engine, or
Btrieve Client/Server Database Engine
 Progress 7/8/9 SQL89 Progress Client Networking PROSQL32.dll
 Progress 9 SQL92 Progress SQL92 Client Access PROCLI92.dll
 Progress OpenEdge 10 SQL92 Progress OpenEdge 10 SQL92 Client Access PROCLI92.dll

Additional system requirements can be found in the Driver Help file or in the ODBC Reference Guide.

For example, if you are trying to configure a data source for the Connect for ODBC driver for ORACLE, you must have Oracle SQL*NET/Net installed. Users must have the 32-bit version of this Oracle client software installed in order to configure a 32-bit Connect for ODBC driver for Oracle. Users must have the 16-bit version of the Oracle client software installed in order to configure a 16-bit Connect for ODBC driver for Oracle.

Note: for recent versions of DB2, Informix, Oracle, MS SQL Server and Sybase, DataDirect also provides Connect for ODBC wire-protocol drivers which do NOT require additional database specific client software.

3. Have you added the database client software and driver directories to your SYSTEM environment variable PATH

Once you locate the client software install directory, add the full directory name, including the drive letter to your SYSTEM environment variable called PATH (ie: C:\Informix\bin;)

- For Windows 9x machines, edit the PATH environment variable by modifying the autoexec.bat file. You'll need to reboot in order for changes to take effect.

- On Windows NT/2000/XP/2003 you should NOT modify the autoexec.bat. You should also NOT set the environment variables in a command window (as it will only affect programs run from within that specific command window)

Instead on Windows NT and Windows 2000, select Start , Settings , Control Panel. On Windows XP and Windows Server 2003, select Start, Control Panel

Next on Windows NT and Windows 2000, double-click on the System icon. On Windows XP and Windows Server 2003 depending on the Windows theme and the currently selected view type, you may have to select Performance and Maintenance before you can select the System icon.

On Windows NT in the System Control Panel, navigate to the System Environment Variables section. On Windows 2000, Windows XP, and Windows Server 2003 from the System Properties window select the Advanced tab and click on the Environment Variables button.

Here you can modify the SYSTEM environment variable PATH. If your application is running only under the current user account you could add it to the USER portion of the environment variable PATH.

Add the DataDirect driver installation directory and the database client software directory at the beginning of your PATH to avoid any dll's being picked up from other locations mentioned on your PATH.

Rebooting is only required when you have applications which run as services.

Last Modified Date2/28/2018 9:38 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.