File 'keys.jlm' not found. 

This error occurs when keys.jlm is looked for, but not found in the CLASSPATH. 

In development mode, add the directory or JAR containing keys.jlm to your CLASSPATH used for running the application. Note that for applets, the directories in the classpath elements have to be terminated with a slash. If your application is already deployed (and thus should not even look at the keys.jlm file any more), the deployment must have failed in some way. 

The license has expired. 

The license is a time-limited one and it has expired. 

Contact your ILOG sales representative to renew the license.  

Key found but maintenance expired. 

The license has time-limited maintenance. You are attempting to use a release or patch of an ILOG product that was issued after the maintenance period ended. 

Either go back to an ILOG product version that was issued before your maintenance period ended, or contact your ILOG sales representative to renew the maintenance contract.  

Key found for an older version. 

The license key is for a given ILOG product version or minor revisions of it. You are trying to use a new major version of the ILOG product with it.  

Contact your ILOG sales representative to renew the license.  

Key found for another machine. 

The license key is bound to a given computer. You are trying to use the ILOG product on a different computer. 

The hostid for which the license is valid is mentioned in the key. You can determine the hostid of your computer by executing the 'jhostid' program. After checking that these two are really different, either use a computer that has a matching hostid, or contact your ILOG sales representative to order a new NODE license for your computer.  

Key not found for this application name. 

The license key is bound to an application name, but the application name registered through registerApplication() is different. 

Check the spelling of the registerApplication() argument versus the application name found in the license key.  

Your keys.jlm file has no valid key. 

The keys.jlm file has only invalid keys, or no keys at all. 

Check that the keys.jlm is at the place where you expect it to be (for example, by moving it away and seeing whether you get a different error message). Then look at the keys.jlm file with a text editor. If it contains keys that are no longer usable, contact your ILOG sales representative to order new licenses.  

Key found with a corrupted format. Or: Invalid character in a checksum. 

The keys.jlm file has keys that do not match the expected syntax of JLM keys. 

Check that the keys.jlm is at the place where you expect it to be (for example, by moving it away and seeing whether you get a different error message). Then either restore the file using an earlier, working backup, or look at the keys.jlm file with a text editor and eliminate malformed keys from it.  

Key found for another product. 

You are trying to use a functionality that is not covered by the valid license keys. 

Contact your ILOG sales representative to buy licenses for the added product that you are trying to use.  

Key found for another key type. 

The keys.jlm file contains a key whose type is not one of the following: EVAL, NODE, SITE, RUNTIME. 

Check that the keys.jlm fileis at the place where you expect it to be (for example, by moving it away and seeing whether you get a different error message). Then look at it with a text editor and eliminate malformed keys from it.  

EVAL key found, but a key of type SITE or NODE is required. 

Some operations, such as deployment, require a key of a particular type. While for development, EVAL, SITE and NODE keys give the same rights, for deployment, EVAL keys cannot be used. 

Contact your ILOG sales representative to buy the required type of license key.  

Can't access your key file. 

The keys.jlm file present but not accessible. 

Check that the keys.jlm file is at the place where you expect it to be (for example, by moving it away and seeing whether you get a different error message). Then check its access permissions and whether you can view it in a text editor.  

Missing application name, initialization function was not called. Or: The function IlvProductUtil.registerApplication was not called. 

In a deployed application, an ILOG product is used without IlvProductUtil.registerApplication having been called before. 

Add an IlvProductUtil.registerApplication call to the JAR and redeploy it. Make sure this call is executed early enough during the initialization of the application.  

Key found with an expired date. 

The validity period of a key is terminated. 

Check that the keys.jlm fileis at the place where you expect it to be (for example, by moving it away and seeing whether you get a different error message). Then look at it with a text editor and eliminate expired keys from it. If you then lack license keys, contact your ILOG sales representative to buy new license keys.  

The required 'SITE' name is missing in your keys file. 

The first key in the keys.jlm file is not preceded by a LICENSE line that contains the site name. 

Check that the keys.jlm fileis at the place where you expect it to be (for example, by moving it away and seeing whether you get a different error message). Then look at it with a text editor and add the LICENSE line that was present when you were sent the license keys.  

Wrong banner flag, please contact ILOG support. 

The banner flag of a license is not among the valid values. You must have been sent incorrect keys. 

Contact ILOG support, to get corrected license keys. When doing so, send a copy of the malformed keys.jlm file.  

Key found with an invalid checksum code. 

The checksum code of a key is not valid. The keys must have been corrupted since you received them from ILOG. 

Check that the keys.jlm is at the place where you expect it to be (for example, by moving it away and seeing whether you get a different error message). Then either restore the file using an earlier, working backup. Or contact ILOG support. When doing the latter, please send a copy of the malformed keys.jlm file.  

Unknown license error ID#xyz, Please contact ILOG Support. 

An internal malfunctioning of JLM has occurred. 

Contact ILOG support. When doing so, send a copy of the malformed keys.jlm file.