Use the following guidelines to troubleshoot licensing problems:
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.
This document is empty and basically useless. It is generated by a web service that can make some statements in HTML Microdata format. This time the service made zero such statements, sorry.