OpenLink Support: SupportWeb.CommonLicenseErrorMessages

Common License Error Messages

This page lists OpenLink's most common error messages:

Common License Error Messages

A license is required for this agent
Client access is restricted by license
Duplicate Serial Number
Exceeded maximum number of licensed connections
License file oledb_lt.lic was not found for this product
No valid license was found

General Problem
Specific to Oracle HSODBC, Heterogeneous Services Generic Connectivity

oplrqb has no registration information

Occurs with 4.x or newer drivers
Occurs with 1.x or 3.x drivers

This evaluation copy has expired
Unable to open a Request Broker license (Network failure)

Error occurs on Unix
Error occurs on Windows

You need to upgrade your license to run this software
Your

A license is required for this agent

OpenLink's Database Agents require licenses. If you experience A license is required errors, contact your OpenLink Account Manager. Your Account Manager will provide you with the appropriate license file.

If you have a current license file, take the following action:

Place the license file in the /bin/ sub-directory of your OpenLink server components installation.
Ensure that your OpenLink /bin/ sub-directory appears in your PATH environment variable.
Set an OPL_LICENSE_DIR that contains this same directory.
Restart your OpenLink Request Broker (4.x-5.x) or OpenLink License Manager to initialize the license.

Client access is restricted by license

Licensees must take account of all applications in the environment that use OpenLink products for data access purposes. Then, users need to tally the data access mechanisms used by these applications. These mechanisms may include ODBC, JDBC, OLE-DB, ADO.NET, XMLA, and others. Sales will generate a license that covers the necessary APIs 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 brokers run in conflict on the same network. In order to resolve the conflict, contact an OpenLink Account Manager and acquire the appropriate licensing. If you do not obtain this licensing, one broker will continue to shut the other broker down.|

Exceeded maximum number of licensed connections

This error is indicative of too many users trying to access the database at once, based on your current license restrictions. For example, if you purchased a 50-connection Multi-Tier software license, it's likely that a 51st user is attempting connection, thus causing this error.

We recommend you monitor the list of existing connections on the server, in one of the following ways:

At a DOS prompt (Windows) or Unix command prompt (Unix/Linux/Darwin), navigate to the OpenLink bin directory and type
```
./oplshut -s
```
Open up your HTML-based Admin Assistant (http://localhost:8000/ ) on the server, then click Server Components Administration*=> *Request Broker Administration => List of Current Connections.

This information will keep you current on how many concurrent connections are in use at a given time.

Note: If the Apache web server is in use to make your ODBC connections, you may receive this error message when using an earlier version of Apache. Among other fixes, version 1.3.2.8 eliminates leaks of several file descriptors to child processes, such as CGI scripts. These CGI scripts can include PHP or Perl scripts, which may make calls to our ODBC Driver. Rather than releasing the file descriptor to our ODBC Driver, the CGI script will continue to have a hold on the driver, which in turn continues to use up a license. With this in mind, OpenLink Support strongly recommends that customers upgrade their version of Apache to at least version 1.3.2.8.

License file oledb_lt.lic was not found for this product

OpenLink's Single-Tier OLE-DB Provider for ODBC Data Sources is licensed separately from all other products. If you encounter *Licence file oledb_lt.lic was not found for this product* errors, take the following action:

Ensure that you have a temporary or permanent OLEDB license.
Ensure that the license has been ftp'd in binary, where appropriate. Use of ASCII ftp corrupts license files.
Ensure that the license resides in the same directory as the OLE DB provider.
Ensure that the directory is passed to the System and User PATHs.

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:

The target machine contains more processor cores than the license permits. Users must obtain licensing for all physical processor cores.
Hyperthreading causes the OpenLink License Manager to detect more processor cores than actually exist in the machine. Users may disable hyperthreading or upgrade their OpenLink Software enhanced for this technology. Ask OpenLink Product Support for additional information.
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 OpenLink Sales to obtain the appropriate license.

Specific to Oracle HSODBC, Heterogeneous Services Generic Connectivity

Ensure that you have a valid OpenLink license file.
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.
Ensure that binary ftp was used to transfer any license. ASCII ftp corrupts licenses.
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.
Use echo $OPL LICENSE_DIR
to see if the
OPL_LICENSE_DIR environment variable is set. If not, export the variable from the commandline. It points to the directory that contains your OpenLink license file. For example:
```
export OPL LICENSE_DIR=/usr/openlink/bin
```
Ensure that you can establish basic ODBC connections using simple applications like odbctest or iodbctest.
Ensure that the environment variables set in Step #4 are available at the time HSODBC is run.
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.
Test.

oplrqb has no registration information

Occurs with 4.x or newer drivers

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

Occurs with 1.x or 3.x drivers

Ensure that you have a valid temporary or permanent license.
Ensure that the license is named register.ini.
Place the license in the bin sub-directory of your OpenLink installation.
Ensure that the relevant PATH variable contains the bin sub-directory of the OpenLink installation.
Remove any expired or extraneous license files from the system.
Shutdown your Request Broker.
Run the following command from the bin sub-directory:
```
register
```
Restart your Request Broker.
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

Log into the problem machine.
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
```
cd into root of your OpenLink installation.
Run the following command in a bourne or bash shell --
```
. ./openlink.sh
```
cd into the /bin sub-directory of your OpenLink installation.
Us ls -al to insure that oplrqb.log is writable by its owner.
vi oplrqb.ini.

Locate the [Protocol TCP] section. For example:


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

Remove the semicolon from the IPAddress parameter.
Hardcode your machine's IP address.
Record the value passed to Listen.
Exit the file.
Run netstat -a to insure that UDP port 60001 is free. For example:
```
netstat -a | grep 60001
```
Run netstat -a to insure that the TCP port passed to Listen is free. For example:
```
netstat -a | grep 5000
```

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.

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

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

A copy of your oplrqb.lic file
The output of: strace ./oplrqb -fd
The output of oplrqb -?

Error occurs on Windows

Log into the problem machine.
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.
Expand your Start=>Programs menu.
Expand the OpenLink Data Access Drivers folder.
Click the Session Rules Book entry. This should open the oplrqb.ini file (a.k.a. "Session Rules Book) in Notepad.

Locate the [Protocol TCP] section. For example:


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

Remove the semicolon from the IPAddress parameter.
Hardcode your machine's IP address.
Record the value passed to Listen.
Exit the file.
Open an MS-DOS prompt.
Run netstat to insure that UDP port 60001 is free.
Run netstat -a to insure that the TCP port passed to Listen is free.
cd into the bin sub-directory of the OpenLink installation.

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.

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

If the same error persists send the following resources:

A copy of your oplrqb.lic file
The output of: strace ./oplrqb -fd
The output of oplrqb -?

You need to upgrade your license to run this software

This license occurs when the license does not cater for the number of processor cores contained within the machine. For example, two processor licenses would return this error on a machine that had two, dual core processors.

To resolve this error, obtain the true number of processor cores on your machine and convey this information to your OpenLink Account Manager. The Account Manager will access any additional fees and provide the appropriate license.

Your OpenLink Lite ODBC Driver is not correctly registered...

OpenLink Lite 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.