SAP Knowledge Base Article - Public

1211060 - Troubleshooting 1157 and 126 ODBC Errors

Symptom

Here are some variations of 1157 and 126 ODBC error messages that can occur when working with Crystal Reports (CR) and attempting to use an ODBC connection:

  • "The setup routines for the <ODBC driver name> ODBC driver could not be loaded due to system error code <error number>" where <error number> is either 1157 or 126.
  • "The Setup Routines for the <ODBC driver name> ODBC driver could not be loaded. You may be low on memory and need to quit a few applications."
  • "ODBC error: Specified driver could not be loaded due to system error <error number> (<ODBC driver name>)" where <error number> is either 1157 or 126.
  • "ODBC error: [Microsoft][ODBC DLL] Specified driver could not be loaded."
  • "Vendor Initialization Failure"

Reproducing the Issue

These error messages can occur when performing one of the following tasks:

  • Creating a new ODBC data source name (DSN) in the 32-bit ODBC Data Source Administrator
  • Selecting and logging on to an ODBC DSN in the Report Designer for use in creating a new report
  • Opening and previewing an existing report (created on another computer) in the Report Designer.

Cause

The 1157 and 126 ODBC error messages can occur due to one or more of the following reasons:

  • The database client software is not installed on your computer.
  • The database client software is installed on your computer but the client software's working directory is not in the Windows search path. The ODBC drivers that Crystal Reports provides are dependent on certain files that are part of your database client software. If these files are not in the Windows search path on your computer, Crystal Reports will not be able to connect to the DSN.
  • You are using 32-bit Crystal Reports and have a 64-bit database client installed on your computer. The bit version of the database client and Crystal Reports must match.

Resolution

To troubleshoot and resolve these error messages, complete the set of steps that best describes your situation.

The database client software is not installed on your computer

Install the database client software on your computer and properly configure it.

It may require the assistance of your Systems Administrator or Database Administrator to accomplish this step.

The database client software is installed on your computer

Ensure that the working directory of your database client appears in the Windows search path by completing the following steps (applicable to Windows 2000 and later):

1. Click Start > Run.
2. In the Run dialog box, type "command". Click OK.
3. In the Command Prompt window, at the prompt, type "path". Press Enter.
4. Review the Windows search path to ensure that database client's bin folder is included. An example of a Windows search path when Oracle is the database client name is:

C:\oracle\product\10.2.0\client_2\BIN

5. In the MS DOS window, at the next prompt, type "exit". Press Enter.

If the database client's bin folder is NOT included, modify the path statement. This adds the bin folder path.

  1. Click Start > Control Panel > System > System Properties. The System Properties dialog appears.
  2. Click the Advanced tab > Environment Variables.
  3. Go to the System Variables section. Click Path > Edit.
  4. Add the database bin path here if it is not referenced.

You may require the assistance of your Systems Administrator or Database Administrator to accomplish this task.

Error messages still occur

If the 1157 and 126 ODBC error messages still occur after completing the steps above, and you are using a CR ODBC driver, reinstall Crystal Reports so that the specific CR ODBC driver (see below for list of CR ODBC drivers) is installed. To do this, complete the following steps:

  1. Uninstall Crystal Reports by selecting the Add/Remove Programs from the Control Panel.
  2. Reinstall Crystal Reports by using a custom install to ensure that the specific CR ODBC driver is selected as part of the installation. Since Crystal Reports 10, additional Crystal Reports database drivers that are not available in the custom install from the CD can also be downloaded from our website.

See Also

1157 - This error means that the ODBC driver itself (DLL file) cannot load its dependency files. This is generally because the database client software is not installed or its working directory (usually called "bin") is not in the Windows search path for this computer.

126 - This error means that the ODBC driver itself (DLL file) cannot load its dependency files. This could be because the database client software is not installed or its working directory (usually called "bin") is not in the Windows search path for this computer. Also, it could mean that the ODBC driver has not been properly installed.

If you are using an ODBC driver provided to you by a third party software vendor (other than Crystal Reports) to connect to your database

  • Contact the vendor of the ODBC driver to find out on which files the ODBC driver is dependent.
  • Include the directories containing those files in your Windows search path.

Keywords

1157 126 SETUP ROUTINES SPECIFIED DRIVER SYSTEM ERROR CODE ODBC ERRORS DRIVER Crystal Reports Connecting via ODBC ODBC Data Source Names (DSNs) ODBC Drivers , c2005338 , KBA , BI-RA-CR , Crystal Reports designer or BusinessViews Manager , Problem

Product

SAP Crystal Reports XI ; SAP Crystal Reports XI R2