Use the following guidelines to troubleshoot licensing problems:
1. Ensure that the Windows Single-Tier license is placed in your Lite32 sub-directories.
2. If on Unix, ensure that the Single-Tier license is placed in the b/in sub-directory of the OpenLink installation. Alternatively, users may pass the full path to licenses to OPL_LICENSE_DIR. This variable may be set using the command line, openlink.sh, openlink.csh, or your .profile.
3. Multi-Tier users ensure the licence is placed in the bin/ sub-directory of the server component installation.
4. Ensure that ftp transfers are conducted in binary. OpenLink's .lic licenses are binary-format files.
5. Windows Single-Tier users should uninstall their software, remove all references to Single-Tier software from the registry, and reinstall, if licensing problems persist. Occasionally, Windows Single-Tier users experience registry corruption, which necessitates the registry wipe and reinstall.
OpenLink consultants have other utilities that may help debugging if you suspect a license-file is corrupt.
The license version must match the Single-Tier driver version or the Multi-Tier request broker and agent version. Operating System Licenses must be generated for the appropriate operating system. CPU's The number of CPUs cited in the license must match the number of CPUs present in the machine. Access Mechanism Licenses may restrict ODBC or JDBC data access. Other licenses permit both ODBC and JDBC access. Database Licenses must list each of the databases to which the user intends to connect. Applications Certain licenses are limited for use with one application.
OpenLink's 1.x and 3.x ship with a license text file. Consultants may open this license with Notepad or a similar text editor. The file should contain the same parameters listed above.