Product Documentation
Cadence License Manager
Product Version 22.01, April 2023

Error Messages and What to Do about Them

Licensing Error Messages reported by Cadence Products

All Cadence products releases released after June 2006 will provide FlexNet messages as is. This section describes the new error message syntax. For detailed decription of the old Cadence licensing error messages please refer to Appendix A

The licensing error messages can be classified as one of the following:

You can also use the lic_error utility to return a detailed explanation and a possible corrective action.

Detailed Syntax

The detailed syntax for an error message is as follows:

Error (licensing)

ERROR (LMC|F-<License API Code><Cadence Error Code>|<FlexNet Error Code>): License call failed[ for <feature>][, <version>][ and <quantity>].[ The license server path is defined as <serverpath>.] <SoftShare Error Message>|FlexNet error message is as follows,

FlexNet ERROR( <Major Err#>, <Minor#>, <System#> ): <error string>.

Run 'lic_error LMC|F-<License API Code><SoftShare Error Code>|<FlexNet Error Code>' for more information.


Cadence advises customers not to use lmremove to remove licenses from active or idle applications. lmremove can cause licenses to become orphaned and thereby deny a license for a legitimate user. An orphaned license can be cleared only by restarting the license server. Customers should use the TIMEOUT option in the options file to reclaim any idle licenses. The minimum timeout interval is 3600 seconds or 1 hour.


Error Message Syntax Description

Parameter

Description

ERROR|WARNING|INFO|QUESTION

The error tag.

LMC|F-<CODE>

Specifies the error code, where:

LM - License Manager

C - Indicates that the error is local to the SoftShare API.

F - Indicates that the error is a Flexnet error.

<Licence API Code> - (0-99) Indicates the licensing API that generated the error.

<SoftShare Error/Warning/Info/Question Code> -. Errors that are local to Cadence source code.

<FlexNet Error/Warning/Info/Question Code> - The Error code returned by FlexNet API.

License call failed

Basic error message header for all licensing errors. Warning, Info, and Question do not have a basic header.

Token call failed

Basic error message header for all token errors. Warning, Info, and Question do not have a basic header.

<feature>, <version> <quantity> and <serverpath>

The feature, version, quantity and serverpath that caused the error. These values are displayed where relevant. These fields are applicable only to errors.

<Cadence API Error/Warning/Info/Question Message>

The message explains the error/warning/info within Cadence.

<FlexNet Error Message>

The actual FlexNet message that explains the licensing failure.

Example

ERROR (LMF-02004): License call failed for feature 12111, version 5.0. The license server search path is defined as 5280@sunrise:5280@sunset. The FlexNet error message is as follows,

FlexNet ERROR(-4, 132, 0): Licensed number of users already reached.

 

Run 'lic_error LMF-xx02004' for more information.

Error (token)

ERROR (LMC-<License API Code><SoftShare Error Code>: Token call failed. <SoftShare Error Message>

Run 'lic_error LMC-XX<License API Code><SoftShare Error Code>' for more information.

These error messages are reported by the token mechanism and are Cadence only errors.

For detailed description of the syntax refer to Error section above.

Warning

WARNING (LMC|F-<License API Code><SoftShare Warning Code>|<FlexNet Warning Code>): <SoftShare Warning Message>|<FlexNet Warning Messsage>

Run 'lic_error LMC|F-<License API Code><SoftShare Warning Code>|<FlexNet Warning Code>' for more information.

For detailed description of the syntax refer to Error section above.

Example

WARNING (LMC-07702): Unable to validate license feature(s)(first attempt). After the third attempt the application will wait indefinitely until the licenses become available. The feature(s) and version(s) are as follows

12111 5.0

cpe 5.0

Run 'lic_error LMC-07702' for more information.

Info

INFO (LMC|F-<License API Code><SoftShare Info Code>|<FlexNet Info Code>): <SoftShare Info Message>|<FlexNet Info Messsage>

For detailed description of the syntax refer to Error section above.

Example

INFO (LMC-07501): Regained all licenses. All licenses OK.

Question

QUESTION (LMC|F-<License API Code><SoftShare Question Code>|<FlexNet Question Code>): <SoftShare Question Message>|<FlexNet Question Messsage>

For detailed description of the syntax refer to Error section above.

Example

QUESTION (LMC-02601): All licenses for 12111 are in use. Do you want to wait? (y/n) [n]

Cadence Error Messages

Note: Since API code is dynamic, we have marked it as 'XX'.

INFO (LMC-XX501): Regained all licenses. All licenses OK.

WARNING (LMC-XX701): Max search path length exceeded - extra ignored.

The combined length of license server search path specified in the CDS_LIC_FILE, applicable contents of the clients file, LM_LICENSE_FILE and the default location of install_dir/share/license/license.dat exceed the MAXPATHLEN on Unix systems. Typically this is 1024 chars. For Windows the limit is hardcoded to 512. The excess data is ignored.

If you use LM_LICENSE_FILE to specify other vendors search path, Cadence recommends that you use CDS_LIC_ONLY variable, which will limit your search path to CDS_LIC_FILE for Cadence applications.

WARNING (LMC-XX702): Unable to validate license feature(s)(first attempt). After the third attempt the application will wait indefinitely until the licenses become available.

Applications revalidate licenses periodically and could not reconnect to the license daemon within the specified threshold value. This happens if the application is unable to communicate with the license server or if the license was reclaimed by the server and allocated to another user.

WARNING (LMC-XX703): Unable to validate license feature(s)(second attempt). After the third attempt the application will wait indefinitely until the licenses become available.

Applications revalidate licenses periodically and could not reconnect to the daemon within the specified threshold value. This happens if the application is unable to communicate with the license server or if the license was reclaimed by the server and allocated to another user.

ERROR (LMC-XX801): The protocol version used encode/decode the token is not supported.

This error occurs when an application creates/decodes a token. This is an internal error within the application. Refer to application specific documentation for more information.

ERROR (LMC-XX802): This token has expired. It can no longer be used.

This error occurs when an application decodes a token. This is an internal error within the application. Refer to application specific documentation for more information.

ERROR (LMC-XX803): The token input data exceeds the maximum allowed limit.

This error occurs when an application creates a token. This is an internal error within the application. Refer to application specific documentation for more information.

ERROR (LMC-XX804): The token input data is empty.

This error occurs when an application creates a token. This is an internal error within the application. Refer to application specific documentation for more information.

ERROR (LMC-XX805): The token is corrupted. Unable to decode.

This error occurs when an application decodes a token. This is an internal error within the application. Refer to application specific documentation for more information.

ERROR (LMC-XX806): Cannot decode token. Check user key.

This error occurs when an application decodes a token. This is an internal error within the application. Refer to application specific documentation for more information.

ERROR (LMC-XX807): Cannot read token.

This error occurs when an application decodes a token. This is an internal error within the application. Refer to application specific documentation for more information.

ERROR (LMC-XX808): An internal error occurred while encoding/decoding the token.

This error occurs when an application creates/decodes a token. This is an internal error within the application. Refer to application specific documentation for more information.

ERROR (LMC-XX901): Internal API error occured. Licensing API not initialized.

This is a Cadence internal error. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMC-XX902): Can't find license file.

The application cannot find a valid license file or port@host address to connect with the license server. Verify that the first license file or port@host address in the license file path is valid. You see this error if the first entry is not valid. Make sure your CDS_LIC_FILE and LM_LICENSE_FILE environment variable is pointing to a correct license file or port@host address.

ERROR (LMC-XX903): Malloc failed. Not enough memory.

This is a Cadence internal error. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMC-XX904): Function/program set by CDS_LICFLTR is not defined or does not exist.

If you have set the CDS_LICFLTR variable, then you must be able to access the program. If the program is not in the current directory, specify full path to it. If required, contact your license administrator.

ERROR (LMC-XX905): Function/program set by CDS_LICFLTR returned an error status.

Your filter program filed with an error status. If you have set the CDS_LICFLTR variable, then the program returned a non-zero status. If required, contact your license administrator.

ERROR (LMC-XX906): Program set by CDS_LICFLTR must have read and execute permissions.

You (as owner, group, or other) must have read and execute permission on this program. Contact your license administrator.

ERROR (LMC-XX907): Program set by CDS_LICFLTR is not an executable file.

The program specified is not a regular executable/script file. Make sure it is not a directory, block device etc.

ERROR (LMC-XX908): vfork() failed while executing program set by CDS_LICFLTR.

Cannot fork a child process to run the program set by CDS_LICFLTR. The vfork manual page describes some of the reasons why vfork might fail. The solutions include increasing your swap space. See the fork man page or contact your system administrator.

ERROR (LMC-XX909): exec() failed while executing program set by CDS_LICFLTR.

exec cannot load program set by CDS_LICFLTR. This could be due to the following:

See the exec man page for more information. Contact your license administrator.

ERROR (LMC-XX910): Program set by CDS_LICFLTR was terminated by a signal.

The CDS_LICFLTR program received a signal, usually a kill signal from the user. Try to start the application again.

ERROR (LMC-XX911): A different version of this feature has already been checked out. Attempt to check out another version is not allowed.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMC-XX912): Unable to validate license features checked out by the application.

The application is unable to validate the license features it had checked out earlier. This happens if the application is unable to communicate with the license server or, if the license was reclaimed by the server and allocated to another user. Cadence applications validate the license features with the license server periodically. If the application cannot validate all the licenses, the application will block indefinitely ( and queue ) until it can regain all the licenses.

ERROR (LMC-XX913): Attempting to regain lost licenses.

The application is attempting to regain the lost licenses.

ERROR (LMC-XX914): Unable to validate license features checked out by the application. Application will now wait until all the licenses become available again.

Even the third attempt to regaining the licenses failed. The application will now block indefinetely ( and queue ) for a license until it can regain all the licenses.

ERROR (LMC-XX915): Unable to contact license server - session exiting.

Applications revalidate licenses periodically and could not reconnect to the daemon within the specified threshold value. The current process is aborting. The communication to the license server was interrupted for some reason while the program was executing.

ERROR (LMC-XX916): Wrong quantity specified during check-in. The check-in quantity must match the checkout quantity.

This is a Cadence internal error. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMC-XX917): Bad user-defined data specified during check-in. The user-defined data doesn't match any of the user-defined data associated with the specified feature.

This is a Cadence internal error. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMC-XX918): Unknown attribute type specified for one or more items in the attribute list. Please use one of the SS_ATTR_* attribute types defined in lmAPI.h.

This is a Cadence internal error. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMC-XX919): The exit status of program set by CDS_LICFLTR could not be determined.

The exit status of the CDS_LICFLTR program could not be determined.

ERROR (LMC-XX920): An unexpected error EINVAL was returned by waitpid.

This is a Cadence internal error. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMC-XX921): An attempt to block the SIGCHLD signal failed.

The attempt to block the SIGCHLD signal failed.

ERROR (LMC-XX922): An attempt to unblock the SIGCHLD signal failed.

The attempt to unblock the SIGCHLD signal failed.

ERROR (LMC-XX923): Invalid attribute data found. Null and empty strings are not valid attribute data.

This is a Cadence internal error. Contact Cadence support at support@cadence.com for further assistance.

FlexNet Error Messages

Note: Since API code is dynamic, we have marked it as 'XX'.

ERROR (LMF-XX001): Cannot find license file.

The application cannot find a valid license file or port@host address to connect with the license server. Verify that the first license file or port@host address in the license file path is valid. You see this error if the first entry is not valid. Make sure your CDS_LIC_FILE and LM_LICENSE_FILE environment variable is pointing to a correct license file or port@host address.

ERROR (LMF-XX002): Invalid license file syntax.

You need a new license file. Reinstall the license file with Cadence Installation Software or contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX003): No license server system for this feature.

The daemon name specified in the license file FEATURE line does not match the vendor daemon name specified in the VENDOR or DAEMON line.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX004): Licensed number of users already reached.

All available licenses for a particular application are in use. To add more licenses, contact your Cadence Sales Representative or Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX005): No such feature exists.

The license server does not serve the requested feature. If licensing has not been configured correctly, this problem can result from using the wrong license file. If licensing is configured correctly when you receive this message, you need a new license file.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX006): No port number in license file and \"FLEXlm\" service does not exist.

This happens if the SERVER line does not specify a TCP/IP port number, and the TCP/IP license service does not exist in /etc/services. Make sure you specify an unused port ( Cadence ships with 5280 as default ) in the SERVER line. See the FlexNet Users Guide for more information on specifying the TCP/IP FLEXlm service in the /etc/services file.

ERROR (LMF-XX007): No socket connection to license server manager.

Application attempted to diconnect from the server after the process had already been disconnected from the license server. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX008): Invalid (inconsistent) license key.

The encryption code in license file is inconsistent. This error occurs when the license file contains a corrupted FEATURE line for the requested application. You need a new license file. Reinstall the license file with Cadence Installation Software or contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX009): Invalid host.

The nodelocked hostid specified in the license server for the feature the application requested, does not match the hostid of the machine where the application is running.

ERROR (LMF-XX010): Feature has expired.

The feature has expired. Today's date is after the expiration date in the license file. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX011): Invalid date format in license file.

The start date, expiration date or the issue date specified in the license file is not valid. You need a new license file. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX012): Invalid returned data from license server system.

Communication failed between the application and the license server. Perhaps, the license server did not respond to the application within the timeout period because of a busy network or due to server being busy due to a high volume of checkouts. If the license server is busy and not responding you need to restart the license server. If the network is frequently busy and your application is timing out, consider the following options:

ERROR (LMF-XX013): No SERVER lines in license file.

There should be at least one SERVER line in the license file. Reinstall the license file with Cadence Installation Software or contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX014): Cannot find SERVER hostname in network database.

The application cannot contact the hostname specified in the SERVER line of the license file. Verify the host name in the /etc/hosts file, NIS and DNS entries. Also verify that the client can reach the license server using the telnet command. The workaround is to use IP-Address (e.g., 123.456.789.123) instead of hostname.

ERROR (LMF-XX015): Cannot connect to license server system.

The client cannot connect to the license server. If lmstat indicates the daemons are running, this error message can indicate that the network is not working properly. Verify that the client can reach the license server using the telnet command. You can also encounter this problem in a busy network. If the network is frequently busy and your application is timing out, consider the following options,

ERROR (LMF-XX016): Cannot read data from license server system.

Communication failed between the application and the license server. Perhaps, the license server did not respond to the application within the timeout period because of a busy network or due to server being busy due to a high volume of checkouts. The license server could have also died before the application attempted to read data from it. If the license server is busy and not responding or if the vendor daemon died, you may need to restart the license server. If the network is frequently busy and the application is timing out, consider the following options:

ERROR (LMF-XX017): Cannot write data to license server system.

Communication failed between the application and the license server. Perhaps, the license server did not respond to the application within the timeout period because of a busy network or due to server being busy due to a high volume of checkouts. The license server could have also died before the application attempted to read data from it. If the license server is busy and not responding or if the vendor daemon died, you may need to restart the license server. If the network is frequently busy and the application is timing out, consider the following options

ERROR (LMF-XX018): License server system does not support this feature.

The feature is probably not supported because:

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX019): Error in select system call.

The select system call failed.

ERROR (LMF-XX020): License server system busy (no majority).

The license server is busy establishing a quorum in fault-tolerant configration so that licensing can start. This error is very rare, and checkout should be retried if this occurs.

ERROR (LMF-XX021): License file does not support this version.

The version requested by the application for this feature is higher than the version number of the feature the daemon supports. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX022): Feature checkin failure detected with license server system.

The checkin request did not receive a proper reply from the license server. You can ignore this message.

ERROR (LMF-XX023): License server system temporarily busy (new server connecting).

The license server is busy establishing a quorum in fault-tolerant configration so that licensing can start. New requests from applications are deferred during this period. This request should be retried.

ERROR (LMF-XX025): License server system does not support this version of this feature.

The version requested by the application for this feature is higher than the version number of the feature the daemon supports. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX026): Request for more licenses than this feature supports.

Application attempted to check out more features than there are in the license file feature line, such as, three licenses when only two licenses are available in the license file.

ERROR (LMF-XX027): Cannot read /dev/kmem.

Application attempted to read /dev/kmem and failed.

ERROR (LMF-XX028): Cannot read /vmunix.

Application cannot read /vmunix and failed.

ERROR (LMF-XX029): Cannot find ethernet device.

Application cannot locate the ethernet device on the machine.

ERROR (LMF-XX030): Cannot read license file.

The license file is not readable, probably because the system permissions of the license file prohibit read access. If you are using the clients file and the permissions on the license file are correct, check the permissions on the clients file because the license file cannot be found if the clients file is not readable.

ERROR (LMF-XX031): Feature start date is in the future.

The feature is not enabled yet. The current date is before the feature start date.

ERROR (LMF-XX032): No such attribute.

Application used a unknown attribute with the FlexNet get and set attribute API's. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX033): Bad encryption handshake with vendor daemon.

This handshake operation between Cadence vendor daemon and lmgrd failed. Use lmstat -a to verify that the daemons are up and running properly on server. If lmstat indicates that the daemons are not running, you must restart the license daemons.

ERROR (LMF-XX034): Clock difference too large between client and license server system.

The system date on the client does not agree closely enough with the date on the license server. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX036): Feature database corrupted in vendor daemon.

The daemon's run-time feature data structures have become corrupted. This is an internal daemon error. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX037): Duplicate selection mismatch for this feature.

A feature was checked out with one license type(dupgroup), and then another attempt was made to check out the same feature with a different license type. A feature can only be checked out using one license type. Either the license file has two feature lines of incompatible types, or two different applications are checking out the same feature in different ways. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX038): User/host on EXCLUDE list for feature.

The options file excludes the user, host, or display from using feature. Contact your license administrator or contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX039): User/host not on INCLUDE list for feature.

The options file does not include the user, host, or display for this feature. If you have an INCLUDE line in the options file you automatically exclude everyone else unless you specifically include them.

Contact your license administrator or contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX040): Cannot allocate dynamic memory.

malloc failed to allocate sufficient memory. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX041): Feature was never checked out.

Application attempted to check the status of a feature that was never checked out. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX042): Invalid parameter.

Application specified an invalid attribute with the FlexNet get and set attribute API's. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX043): No key data supplied in call to lc_new_job() or lc_init().

Application specified no key data during FlexNet initialization. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX044): Invalid key data supplied.

Application specified incorrect key data during FlexNet initialization. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX045): Function not available in this version.

This FlexNet Licensing client function is not available.This could be due to incorrect initialization. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX046): Software is evaluation version.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX047): Clock setting check not available in vendor daemon.

The license server cannot verify compatible system clock settings. The system date on the application client does not agree closely enough with the date on the license server.

ERROR (LMF-XX048): Platform not enabled.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX049): Date invalid for binary format.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX050): Key data has expired.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX051): Not initialized.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX052): Vendor daemon did not respond within timeout interval.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX053): Checkout request rejected by vendor-defined checkout filter.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX054): No FEATURESET line in license file.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX055): Incorrect FEATURESET line in license file.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX056): Cannot compute FEATURESET data from license file.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX057): socket() call failed.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX058): setsockopt() call failed.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX059): Message checksum failure.

Communications error messages between the FLEXenabled application and license server are encrypted and checksummed for security and integrity. The checksum will usually fail because of poor networking communications. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX060): License server system message checksum failure.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX061): Cannot read license file data from license server system.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX062): Network software (tcp/ip) not available.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX063): You are not a license administrator.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX064): lmremove request before the minimum lmremove interval.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX065): Unknown VENDORCODE struct type passed to lc_new_job() or lc_init().

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX066): Include file/library version mismatch.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX067): No licenses available to borrow.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX068): License BORROW support not enabled.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX069): FLOAT_OK can't run standalone on license server system.

This error can occur because the license server isn't running, or the application needs to add @localhost with the lmpath command.

ERROR (LMF-XX070): Meter already being updated, locked.

lmutil lmborrow -startupdate was issued but not updated yet. To override this, stop and restart the license server system.


Overriding may cause loss of licenses.


ERROR (LMF-XX071): Invalid TZ environment variable.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX072): Old VENDORCODE (3-word) struct type passed to lc_new_job() or lc_init().

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX073): Local checkout filter rejected request.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX074): Attempt to read beyond end of license file path.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX075): SYS$SETIMR call failed.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX076): Internal Error - Please report to Macrovision Corporation.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX077): Bad version number - must be floating point number, with no letters.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX078): FLEXadmin API functions not available.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX079): Internal error -79.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX080): Internal error -80.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX081): Internal error -81.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX082): Invalid PACKAGE line in license file.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX083): Version of vendor daemon is too old.

Vendor daemon version is older than the application's FlexNet Licensing version. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX084): USER_BASED license has no specified users -- see license server system log.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX085): License server system does not support this request.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX086): License object already in use.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX087): Checkout exceeds MAX specified in options file.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX088): System clock has been set back.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX089): This platform not authorized by license.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX090): Future license file format or misspelling in license file.

The file was issued for a later version of FlexNet Licensing than this program understands. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX091): Encryption seeds are non-unique.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX092): Feature removed during lmreread, or wrong SERVER line hostid.

Checkout failure due to two possible causes:

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX093): This feature is available in a different license pool.

This is a warning condition. The license server system has pooled one or more INCREMENT lines into a single pool, and the request was made on an INCREMENT line that has been pooled. If this is reported as an error, it's an internal error.

ERROR (LMF-XX094): Attempt to generate license with incompatible attributes.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX095): Network connect to THIS_HOST failed.

The license file indicates THIS_HOST, and the server is not running on this host. If it's running on a different host, THIS_HOST should be changed to the correct host.

ERROR (LMF-XX096): License server machine is down or not responding.

See the system administrator about starting the license server system, or make sure you're referring to the right host (see LM_LICENSE_FILE). Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX097): The desired vendor daemon is down.

Check the lmgrd log file, or try to restart the license daemon.

ERROR (LMF-XX098): This FEATURE line can't be converted to decimal format.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX099): The decimal format license is typed incorrectly.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX100): Cannot remove a linger license.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX101): All licenses are reserved for others.

The system administrator has reserved all the licenses for others. Reservations are made in the options file. The license server system must be restarted for options file changes to take effect.

ERROR (LMF-XX102): A FLEXid borrow error occurred.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX103): Terminal Server remote client not allowed.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX104): Cannot borrow that long.

Retry the checkout again for a shorter period.

ERROR (LMF-XX105): Feature already returned to license server system.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX106): License server system is out of network connections.

The vendor daemon can't handle any more users. See the license server manager (lmgrd) debug log for further information.

ERROR (LMF-XX107): Cannot borrow a PACKAGE component.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX110): Cannot read dongle: check dongle or driver.

Either the hardware dongle is not attached, or the necessary software driver for this dongle type is not installed. In order to read the dongle hostid, the correct driver must be installed. The drivers are included as part of the Cadence licensing software. You can also find these drivers at http://www.revenera.com. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX111): lmgr.res, Windows Resource file, not linked.

When linking Windows binaries, you must link with lmgr.lib as well as lmgr.res.

ERROR (LMF-XX112): Missing Dongle Driver.

In order to read the dongle hostid, the correct driver must be installed. These drivers are included as part of the Cadence licensing software. You can also find these drivers at http://www.revenera.com. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX114): SIGN= keyword required but missing from the license certificate.

This is probably because the license is older than the application. Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX115): Error in Public Key package.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX116): TRL not supported for this platform.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX117): BORROW failed.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX118): BORROW period expired.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX119): lmdown/lmreread must be run on the license server machine.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX120): Cannot lmdown the server when licenses are borrowed.

Use lmstat to find the users that have the licenses borrowed.

ERROR (LMF-XX121): FLOAT_OK requires exactly one dongle hostid.

Use one line per dongle.

ERROR (LMF-XX122): Unable to delete local borrow info.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX123): Returning a borrowed license early is not supported.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX124): Error returning borrowed license.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX125): A PACKAGE component must be specified.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX126): Composite hostid not initialized.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX127): An item needed for composite hostid missing or invalid.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX128): Error, borrowed license doesn't match any known server license.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX129): Internal Error (NULL pointer).

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX130): Internal Error (Bad handle).

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX131): Internal Error (Empty string).

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX132): Internal Error (Bad memory access).

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX133): Internal Error (Operation not supported).

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX134): Job handle is NULL. .

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX135): Error enabling event log.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX136): Event logging is disabled.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX137): Error writing to event log.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX138): Internal error (Bad index).

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX139): Timeout.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX140): Bad message command.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX141): Error writing to socket. Peer has closed socket.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX142): Error, cannot generate version specific license tied to a single hostid, which is composite.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX143): Version-specific signatures are not supported for uncounted licenses.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX144): License template contains redudant signature specifiers.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX145): Invalid V71_LK signature.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX146): Invalid V71_SIGN signature.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX147): Invalid V80_LK signature.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX148): Invalid V80_SIGN signature.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX149): Invalid V81_LK signature.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX150): Invalid V81_SIGN signature.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX151): Invalid V81_SIGN2 signature.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX152): Invalid V84_LK signature.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX153): Invalid V84_SIGN signature.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX154): Invalid V84_SIGN2 signature.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX155): License key required but missing from the license certificate.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX156): Invalid AUTH={} signature.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX157): Specified operation is not allowed.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX158): Cannot open TS.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX159): Invalid fulfillment record.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX160): Invalid activation request received.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX161): No fulfillment exists in trusted storage which matches the request.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX162): Invalid activation response received.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX163): Can't return the fulfillment.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX164): Return would exceed max count(s).

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX165): No repair count left.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX166): Specified operation is not allowed.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX167): User/host on EXCLUDE list for entitlement.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX168): User/host not in INCLUDE list for entitlement.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX169): Activation error.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX170): Invalid date format in trusted storage.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX171): Message encryption failed.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX172): Message decryption failed.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX173): Bad filter context.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX174): SUPERSEDE and SUPERSEDE_SIGN can't be used at the same time.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX175): Invalid SUPERSEDE_SIGN syntax.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX176): SUPERSEDE_SIGN does not contain any license signature.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX177): ONE_TS_OK is not supported in this Windows Platform.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX178): Failed to create or reopen the mutex. Terminal Server Remote Client checkout not allowed.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX179): Only One Terminal Server Remote Client checkout is allowed for this feature.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX180): Internal Error -180.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX181): Internal Error -181.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX182): Internal Error -182.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX183): More than one ethernet hostid not supported in composite hostid definition.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX184): The number of characters in the license file paths exeeds the permissible limit.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX185): Invalid TZ keyword syntax.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX186): Invalid time zone override specification in the client.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX187): The time zone information could not be obtained.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX188): License client time zone not authorized for license rights.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX189): Invalid VM_PLATFORMS syntax.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX190): Feature can be check-out from Physical machine only.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX191): Feature can be check-out from Virtual machine only.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX192): VM platform not authorized by license.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX193): FNP vendor keys do not support Virtualization feature.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX194): Checkout request denied as it exceeds the MAX limit specified in the options file.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX195): Binding agent API - Internal error.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX196): Binding agent communication error

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX197): Invalid Binding agent version.

Contact Cadence support at support@cadence.com for further assistance.

ERROR (LMF-XX201): Invalid IP address used while overriding.

The IP address specified for the LM_A_INTERNET_OVERRIDE attribute, used to override the existing IP address, is invalid.

Contact Cadence support at support@cadence.com for further assistance.

License Server/Configuration Error Messages

This section describes some of the server and license configuration errors.

For detailed description of the error messages reported in license server debug log file, refer to FlexNet End User Guide shipped as part of the SoftShare License Tools.

Cannot open daemon lock file MULTIPLE "cdslmd" servers running

The license daemons are already running. Shut down all license daemons and re start the license daemons. You are trying to start the licensing daemons on a diskless workstation. The license server must have its own operating system, file systems, and /usr/tmp directory on a local disk. Someone or something removed the lock file, usually located at /usr/tmp/lockcdslmd

If you use a script or cron job to delete zero-length files, edit the script so that it does not delete this one. If the /usr/tmp/lockcdslmd file is removed more than 5+ times, the license server will stop serving licenses and will need to be restarted.

Can't find the install_dir/tools link. Create it?

This message comes from the licensing utility you are using. The utility can create the link for you or you can create the tools link manually. You are required to use the tools link because it allows the Cadence software to easily find the appropriate executable files for your computer's architecture.

Can't read data

Applications can find the license server but you are using an older cdslmd. Verify the cdslmd version you are using by looking at the debu g log file (default location is /usr/tmp/license.log) or by running lmstat. Use the latest version of cdslmd that you have.

ERROR: license daemon: execl failed: …

The debug log file indicates that the cdslmd daemon is lost, does not exist, or is not executable. The license manager daemon (lmgrd) failed to start cdslmd. Verify that the path to the cdslmd daemon listed on the DAEMON line in the license file is correct. Correct the path to cdslmd in the license file. Next, shut down the license daemons. Start the license daemons by executing /etc/rc.lic. Finally, verify the existence and the permissions of the cdslmd daemon in install_dir/tools/bin.

If you are unable to find the cdslmd daemon in this directory, you must verify mounting of the file systems and existence of the links. You may need to reinstall the Cadence licensing software tools containing the Cadence daemons. Next, verify that the cdslmd daemon is executable. Use the chmod command to change the permissions if the cdslmd daemon is not executable. If you are still in the install_dir/tools/bin directory, type

chmod 755 cdslmd

If the cdslmd daemon exists and has the correct permissions, this error message comes up because the path to cdslmd, as listed in the license file, is incorrect. If you have moved install_dir/tools/bin to another location, edit your license file and correct the path to cdslmd.

ERROR: time (cdslmd) Retrying socket bind (address in use)

Another process is using the same TCP/IP port address. This error message indicates that the license daemon was already running when it started again or that the daemon improperly stopped recently and the daemon did not release the port.

To free up the ports faster run the following command before restarting the license server

/usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 2400

The command above resets the tcp_time_wait_interval to 2.4 seconds so that the OS can free up the ports in 2.4 seconds.

Determine if more than one lmgrd is running. If an lmgrd is already running for the Cadence software, usually lmgrd failed to start the cdslmd daemon. Use the ps command to list the license daemons and determine their process ID numbers (pid). If more than one version is running, use an editor to modify the license file and change the TCP/IP port number.

For example, if both license files use 5210 as the TCP/IP port, change one of them to 5220. See the FlexNet documentation available on the World Wide Web at https://www.flexera.com.

Use the lmstat utility to review the status of all Cadence features and determine if users are accessing a license.

cd install_dir/tools/bin

./lmstat -c license_file -a

If more than one lmgrd is running, shut the daemons down and restart them.

Do not kill the license manager daemon while licenses are in use because the users could lose their data. Do not use the -9 option of the kill command.

If users do not exit before you shut the license daemons down, they will see the WARNING (LM 100) waiting <num_sec> seconds to regain <feature> license message until the license server comes back up.

Check /etc/services to see if the socket should be busy.

ERROR: Using license file /usr/local/FLEXlm/licenses/license.dat

You did not use /etc/rc.lic to start the license daemons and you did not specify the license file (the lmgrd -c option) when you started the license daemons. Restart the license daemons with the following command:

nohup lmgrd -c license_file -l /usr/tmp/license.log

The lmgrd daemon cannot find the license file.

Verify that the /etc/rc.lic file has the correct license file and host ID.

When checking for the correct host ID, you must verify the entry exactly because license files are case sensitive.

Failed to checkout license for Lib Kit 'library '.

Received with ERROR (LM -24): can't find <license file> license_file and "Unable to check out feature feature" messages.

You tried to configure library before you configured licensing. When installing, loading, and configuring Cadence libraries, the license daemons must be running and they must be using the new license file before you configure library.

Configure the library from Cadence installation software by following the directions in the Cadence Installation Guide.

Inconsistent encryption code for feature

This problem can happen if you installed the license file manually, without Cadence installation software. Some mail systems wrap lines or reformat the message when forwarding your mail. You receive a license file, but you see a message similar to this in your license log file after you start to use the new file.

7:00:28 (lmgrd) Started cdslmd

7:00:29 (cdslmd) Inconsistent encryption code for feature

The mail system altered your file.

For Qualcomm's Eudora, if you still have the original Cadence mail in a Eudora folder, turn off the wordwrap + QP options from the tool bar before forwarding it to a UNIX system or saving the mail to a file again.

For ZMail from Network Computing Devices, Inc., users forwarding mail from the Compose screen must disable Autoformat in their Options menu.

Correct the e-mail you received and install the license file again with Cadence installation software.

license manager: Not a valid server host, exiting.

If you did not use /etc/rc.lic to start the license daemons and you did not specify the license file when you started the license daemons, restart the license daemons with the lmgrd -c command or with /etc/rc.lic

nohup lmgrd -c license_file > /usr/tmp/license.log

If you started the license daemons with /etc/rc.lic, verify the following:

If you use LM_LICENSE_FILE to locate the license file, it could be conflicting with other FlexNet-based products.

If the license daemons exist and have the correct permissions, check the path to the daemon.

Verify proper network communication.

No features to serve!

The cdslmd daemon has no features to serve. Verify if all the licenses have expired or not started yet.




 ⠀
X