Common License-related Error Messages

A license is required for this agent

Different licenses are required for different Enterprise Edition (Multi-Tier) Database Agents. If you experience A license is required errors, contact your Account Manager. They can provide you with the appropriate license file.

If you have a current license file, follow the relevant instructions to activate it.

Client access is restricted by license

Licensees must take account of all applications in the environment that use our data access products, and the data access mechanisms (ODBC, JDBC, OLE-DB, ADO.NET, XMLA, and others) they use.

Sales will generate a license that covers the necessary APIs and/or data access mechanisms. Failure to license all the required mechanisms will result in the "Client access" error.

Duplicate Serial Number

The duplicate serial number error message arises when two or more environments are running with the same serializd license file.

To resolve the conflict, ensure that each licensed environment has an individually serialized license file.

Exceeded maximum number of licensed connections

This error is discussed in the UDA Knowledgebase.

License file oledb_lt.lic was not found for this product

Our Lite Edition (Single-Tier) OLE-DB Provider for ODBC Data Sources is licensed separately from all other products.

If you encounter *License file oledb_lt.lic was not found for this product* errors, take the following action:

  1. Ensure that you have a temporary or permanent oledb_lt.lic license file.
  2. Ensure that the license file has been transferred with binary preserving methods. Use of ASCII transfer may corrupt license files.
  3. Ensure that the license resides in the same directory as the OLE DB provider.
  4. Ensure that the directory is passed to the System and User PATHs.
  5. Finally, if the problem persists, contact OpenLink Product Support.

No valid license was found

General Problem

No valid license was found errors tend to arise from one of three scenarios:

  1. The target machine contains more logical processors than the license permits. Users must obtain licensing for all logical processors.
  2. Hyperthreading can cause the OpenLink License Manager (oplmgr) to detect more logical processors than physical cores exist in the machine. Users may disable hyperthreading or upgrade their license to accommodate the logical processor count. Contact Product Support for additional information.
  3. The license pertains to a major release of software which differs from the major release of the software installed on the machine. Users must contact our Sales or Support team to obtain an appropriate license.

Specific to Oracle HSODBC (Heterogeneous Services Generic Connectivity) or DG4ODBC (Database Gateway for ODBC)

  1. Ensure that you have a valid OpenLink license file.
  2. Ensure that the license file is placed in the same directory as an OpenLink Single-Tier client driver or an OpenLink Multi-Tier server components installation.
  3. Ensure that binary ftp was used to transfer any license. ASCII ftp corrupts licenses.
  4. Ensure that openlink.sh or openlink.csh was run from the root of the relevant OpenLink installation. openlink.sh is compatible with bourne and bash shells. openlink.csh is compatible with C shells. This sets ODBCINI, ODBCINSTINI, and other environment variables that facilitate ODBC connectivity.
  5. Use echo $OPL_LICENSE_DIR to confirm whether the OPL_LICENSE_DIR environment variable is set, and what its value is. If not set, export the variable from the commandline. It must point to the directory(ies) that contain(s) your OpenLink license file. For example: 

    export OPL LICENSE_DIR=/usr/openlink/bin:/opt/openlink/licenses

  6. Ensure that you can establish basic ODBC connections using simple applications like odbctest or iodbctest.
  7. Ensure that the environment variables set in Step #4 are available at the time HSODBC is run.
  8. Add OPL LICENSE_DIR to the inithsodbc.ora file, if licensing problems persist. You may also set other environment variables like ODBCINI, the Single-Tier OPENLINKINI, and so on in inithsodbc.ora, as needed.
  9. Test.

oplrqb has no registration information

Occurs with 4.x or newer drivers

  1. Insure that you have a valid temporary or commercial license.
  2. Insure that the license is named oplrqb.lic.
  3. Place the license in the bin sub-directory of your OpenLink installation.
  4. Insure that the relevant PATH variable contains the bin sub-directory of the OpenLink installation.
  5. Remove any expired or extraneous license files from the system.
  6. Restart your Request Broker.
  7. Test.

Occurs with 1.x or 3.x drivers

  1. Ensure that you have a valid temporary or permanent license.
  2. Ensure that the license is named register.ini.
  3. Place the license in the bin sub-directory of your OpenLink installation.
  4. Ensure that the relevant PATH variable contains the bin sub-directory of the OpenLink installation.
  5. Remove any expired or extraneous license files from the system.
  6. Shutdown your Request Broker.
  7. Run the following command from the bin sub-directory: 

    register

  8. Restart your Request Broker.
  9. Test.

This evaluation copy has expired

"This evaluation copy has expired" errors will occur, if you do not obtain a license for your OpenLink Single-Tier drivers. OpenLink's Single-Tier drivers must be licensed after the evaluation period has expired.

If you have obtained a Single-Tier license -- and you continue to experience registration errors -- you may have received an inappropriate license key. Please forward a copy of your license and your driver version to OpenLink Product Support. Be advised -- certain Progress Large Client drivers register with Progress Small Client keys. Ask Product Support for guidance.

If you are certain that you have obtained the correct license, you may have a corrupt registry. You will need to uninstall your OpenLink Single-Tier driver, remove references to the driver from your registry, and reinstall. Subsequent attempts to register the Single-Tier driver should succeed.

Unable to open a Request Broker license (Network failure)

Error occurs on Unix

  1. Log into the problem machine.
  2. Run ps -ef and make sure that oplmgr, oplrqb, and www_sv are not running. Kill any relevant processes. For example: 

    ps -ef | grep oplmgr 
ps -ef | grep oplrqb 
ps -ef | grep www_sv

  3. cd into root of your OpenLink installation.
  4. Run the following command in a bourne or bash shell -- 

    . ./openlink.sh

  5. cd into the /bin sub-directory of your OpenLink installation.
  6. Us ls -al to insure that oplrqb.log is writable by its owner.
  7. vi oplrqb.ini.
  8. Locate the [Protocol TCP] section. For example: 

    [Protocol TCP] 
PingWatchdog = No 
PingInterval = 600 
Listen = 5000 
PortLow = 5000 
PortHigh = 6000 
;IPAddress = 127.0.0.1

  9. Remove the semicolon from the IPAddress parameter.
  10. Hardcode your machine's IP address.
  11. Record the value passed to Listen.
  12. Exit the file.
  13. Run netstat -a to insure that UDP port 60001 is free. For example: 

    netstat -a | grep 60001

  14. Run netstat -a to insure that the TCP port passed to Listen is free. For example: 

    netstat -a | grep 5000

  15. Run oplmgr -? to insure that you do not have version 0.9.4. If you do, you have a bug, and you must stop and contact OpenLink Product Support. For example: 

    $ ./oplmgr -? 
OpenLink License Manager Version 0.9.4 as of Fri Feb 03 2006 (Release 6.0 cvsid 00082). 
Compiled for Linux 2.4.20-43.9.legacysmp (i686-pc-linux-glibc23) 
Copyright (C) OpenLink Software.

  16. Use ls -al to make sure that all files in ~/openlink/bin and ~/openlink/lib have file ownership.
  17. Make sure that there are no files named .opl* or opl* in /tmp. Remove them. Here, * is a wildcard.
  18. Start your Request Broker process.
  19. Test your connection.

If the same error persists send the following resources to OpenLink Product Support:

Error occurs on Windows

  1. Log into the problem machine.
  2. Use the Services utility to insure that the OpenLink License Manager and OpenLink Request Broker are shut down. Run the task manager and make sure that www_sv is not running. Kill any relevant processes.
  3. Expand your Start=>Programs menu.
  4. Expand the OpenLink Data Access Drivers folder.
  5. Click the Session Rules Book entry. This should open the oplrqb.ini file (a.k.a. "Session Rules Book) in Notepad.
  6. Locate the [Protocol TCP] section. For example: 

    [Protocol TCP] 
PingWatchdog = No 
PingInterval = 600 
Listen = 5000 
PortLow = 5000 
PortHigh = 6000 
;IPAddress = 127.0.0.1

  7. Remove the semicolon from the IPAddress parameter.
  8. Hardcode your machine's IP address.
  9. Record the value passed to Listen.
  10. Exit the file.
  11. Open an MS-DOS prompt.
  12. Run netstat to insure that UDP port 60001 is free.
  13. Run netstat -a to insure that the TCP port passed to Listen is free.
  14. cd into the bin sub-directory of the OpenLink installation.
  15. Run oplmgr -? to insure that you do not have version 0.9.4. If you do, you have a bug. For example: 

    $ ./oplmgr -? 
OpenLink License Manager Version 0.9.4 as of Fri Feb 03 2006 (Release 6.0 cvsid 00082). 
Compiled for Linux 2.4.20-43.9.legacysmp (i686-pc-linux-glibc23) 
Copyright (C) OpenLink Software.

  16. If you have a new license file, put it in the bin sub-directory of your OpenLink installation.
  17. Restart the OpenLink License Manager using the Services panel.
  18. Restart the OpenLink Request Broker using the Services panel.
  19. Test your connection

If the same error persists send the following resources:

You need to upgrade your license to run this software

This error is typically seen in two situations --

* when the license is for an earlier version of the software than is being used -- for example, when a Release 5.x license is being used with a Release 6.x driver.

* when the license is for a smaller number of logical processors than the machine reports to our components -- for example, when a 1 (one) CPU license is used on a dual-core machine.

To resolve this error, provide your Account Manager with the number of processor cores in your machine, and indicate whether hyperthreading is active. Also provide the version(s) of the OpenLink component(s) you're trying to use, and a copy of the current license file. Your Account Manager will provide an appropriate temporary license for testing, and assess whether any additional fees will be due before provision of a new permanent license.

Your ODBC Driver is not correctly registered...

Lite Edition registration errors will occur, if you do not obtain a license for your OpenLink Single-Tier drivers. OpenLink's Single-Tier drivers must be licensed after the evaluation period has expired.

If you have obtained a Single-Tier license -- and you continue to experience registration errors -- you may have received an inappropriate license key. Please forward a copy of your license and your driver version to OpenLink Product Support. Be advised -- certain Progress Large Client drivers register with Progress Small Client keys. Ask Product Support for guidance.

If you are certain that you have obtained the correct license, you may have a corrupt registry. You will need to uninstall your OpenLink Single-Tier driver, remove references to the driver from your registry, and reinstall. Subsequent attempts to register the Single-Tier driver should succeed.