#!/bin/csh -f
set progName = $0
set inputVal = $1
if ( "$inputVal" == "" ) then
  echo "Usage: $progName <license_error_number>"
  exit 1
endif
echo "$progName" | grep "/" > /dev/null
if ( $status == 0 ) then
  # If there's a / in there somewhere, assume that we've been given a 
  # "reasonably" qualified path, and use it.
  set progPath = "$progName"
else
  # For those platforms that don't set arg 0 to the full path...
  # Look through the path to find out where this script is.
  set progPath = ""
  set fullPath = `echo $path | sed -e "s?:? ?g"`
  foreach pathElement ( $fullPath )
    if ( -x $pathElement/$progName ) then
      # Found it!  This is our value...
      set progPath = "$pathElement/$progName"
      break
    endif
  end
  if ( "$progPath" == "" ) then
    # Punt...
    set progPath = "$progName"
  endif
endif
set newError=`echo $inputVal | grep "LM"`
if ( "$newError" != "" ) then
  # v10.8 error code. Remove the API code from the error code.
  set inputVal=`echo $inputVal | awk 'BEGIN { FS = "-" } {print $1"-"substr($2,3) }'`
endif
grep "^$inputVal\:" $progPath > /dev/null
if ( $status == 0 ) then
  # Legitimate input - let 'em see the text
  if ( "$newError" != "" ) then
    # v10.8 error code. Replace the error code with the one the user passes in
    # that contains the API code.
    grep "^$inputVal\:" $progPath | sed -e "s?^$inputVal\:??" | sed -e "s?$inputVal?$1?"
  else
    grep "^$inputVal\:" $progPath | sed -e "s?^$inputVal\:??"
  endif
else
  echo "Sorry - error message $1 has no extended message."
endif
exit 0
# Pre 10.8 error codes
-1:ERROR (LM -1): license error (<error_number>) - contact Cadence CRC at 
-1:               1-877-CDS-4911
-1:
-1:This error occurs while you are running an application. Try to recall 
-1:the conditions under which the problem occurred. Contact the Customer 
-1:Response Center.
-2:ERROR (LM -2): encryption code in license file is inconsistent
-2:
-2:This error occurs when the license file contains a corrupted FEATURE
-2:line for the requested application. You need a new license file.
-2:Reinstall the license file with SoftLoad or contact the Customer 
-2:Response Center at 1-877-CDS-4911.
-3:ERROR (LM -3): license server communication error - try longer timeout
-3:
-3:Communications failed between the license daemons and the license server.
-3:Perhaps the daemon did not respond to the license server within the 
-3:timeout period because of a busy network or because the license file 
-3:contains more than (or close to) 2000 FEATURE lines..
-3:
-3:If the network is frequently busy,
-3:
-3:1. Increase the timeout between the license server and the application 
-3:   client with CDS_LIC_TIMEOUT.  The default timeout is ten seconds.
-3:
-3:   Platform                Command
-3:   --------                -------
-3:   UNIX                    setenv CDS_LIC_TIMEOUT <seconds>
-3:   Windows                 set CDS_LIC_TIMEOUT=<seconds>
-3:
-3:2. For fault-tolerant license servers, increase the timeout between the 
-3:   license servers by starting the license daemons with the -t option. 
-3:   The default timeout is ten seconds. To increase the timeout, follow
-3:   these steps:
-3:
-3:   - Modify the startup file, rc.lic, to specify the -t option of lmgrd.
-3:     Refer to the "lmgrd" man page or the lmgrd description in the 
-3:     'Cadence License Management' in CDSDoc for more information. 
-3:
-3:   - Restart the daemons.  See the "Stopping and Starting the License
-3:     Daemons" section in the 'Cadence License Manager' in CDSDoc for
-3:     more information.
-4:ERROR (LM -4): invalid date format in license file
-4:
-4:You need a new license file.  Reinstall the license file with SoftLoad, or 
-4:contact the Customer Response Center at 1-877-CDS-4911.
-5:ERROR (LM -5): attempted checkout of feature with incompatible types
-5:
-5:A feature was checked out with one license type (such as single job or
-5:single user), and then another attempt was made to check out the same 
-5:feature with a different license type.  A feature can only be checked out 
-5:using one license type.  Either the license file has two feature lines of 
-5:incompatible types, or two different applications are checking out the same
-5:feature in different ways.
-5:
-5:1. Identify the problem and correct the license file.
-5:
-5:   You might need to contact the Customer Response Center at 1-877-CDS-4911
-5:
-5:2. Ask all users on the network using the application to log out and 
-5:   complete one of the these steps. 
-5:
-5:   - Execute lmreread.
-5:
-5:   - Shut down and restart the license daemons.
-6:ERROR (LM -6): invalid license file syntax
-6:
-6:You need a new license file.  Reinstall the license file with SoftLoad, or 
-6:contact the Customer Response Center at 1-877-CDS-4911. 
-7:ERROR (LM -7): license server communication error - suspect bad daemons
-7:
-7:cdslmd performs an encryption handshake operation with lmgrd before any 
-7:licensing operations.  This handshake operation failed.  Use lmstat -a to 
-7:verify that the daemons are up and running properly on server.  
-7:
-7:lmstat might indicate that the daemons are not running. If so, you must
-7:restart the license daemons.
-8:ERROR (LM -8): can't find SERVER hostname in network database
-8:
-8:The license server host name as specified in the license file cannot be 
-8:contacted using network resources. 
-8:
-8:1. Verify the host name in the /etc/hosts file or equivalent database.
-8:
-8:2. If the license server is a UNIX system, verify that the application 
-8:   client can reach the license server using the command listed below, 
-8:   replacing <hostname> with the name of the license server listed in 
-8:   the license file. 
-8:
-8:   Platform         Command
-8:   --------         -------
-8:   HP Series 700    /usr/bin/telnet <hostname>
-8:   Other Unix       /usr/ucb/telnet <hostname>
-8:   Windows          telnet <hostname>
-8:
-8:Note: Do not use ping. It does not adequately ensure that the client can 
-8:reach the license server. If you are not using .rhosts and you are 
-8:prompted for a password on hostname, the network is configured correctly. 
-8:
-8:Type Control-d to exit from telnet. If the network is not configured
-8:correctly, see your operating system documentation.
-9:ERROR (LM -9): time difference between client and server is > 60 days
-9:
-9:The system date on the client does not agree closely enough with the date 
-9:on the license server.  The difference can be no greater than 60 days.
-10:ERROR (LM -10): license file does not support this version of the feature
-10:
-10:The version levels of the application in use and the license file on your 
-10:system do not match.  You need a new license file.  Contact the Customer 
-10:Response Center at 1-877-CDS-4911.
-11:ERROR (LM -11): the VMS logical CDS_ROOT is set to an invalid path
-11:
-11:The current setting of the CDS_ROOT VMS logical variable is incorrect.
-11:The daemon is unable to find the directory for the license and 
-11:administrative files.  Set the CDS_ROOT VMS logical variable by executing 
-11:the DCL command to point to the installation directory:
-11:
-11:    define/system CDS_ROOT <install_dir>
-12:ERROR (LM -12): unable to contact license server - check network
-12:
-12:The client cannot connect to the license server. If lmstat indicates the 
-12:daemons are running, this error message can indicate that the network 
-12:is not working properly. 
-12:
-12:1. Verify that the lmgrd daemon is running.
-12:
-12:   For Unix systems:
-12:   =================
-12:
-12:   Log into the license server and type the appropriate command. 
-12:
-12:   Platform                Command
-12:   --------                -------
-12:   HP Series 700           ps -edaf | grep lmgrd | grep -v grep
-12:   IBM RS/6000             ps waux  | grep lmgrd | grep -v grep
-12:   Linux                   ps -waux | grep lmgrd | grep -v grep
-12:                           ps -edaf | grep lmgrd | grep -v grep 
-12:   Solaris                 ps -waux | grep lmgrd | grep -v grep
-12:                           ps -edaf | grep lmgrd | grep -v grep 
-12:   SunOS 4.1.3             ps -waux | grep lmgrd | grep -v grep
-12:
-12:   The system should return a lmgrd process. If nothing is returned, 
-12:   the license manager daemon is not running. 
-12:
-12: 
-12:   For Windows NT:
-12:   ===============
-12:
-12:   Use Task Manager to check if lmgrd.exe is running. To run Task 
-12:   Manager, right-click on the toolbar, then click Task Manager.
-12:   and then click the Processes tab.
-12:
-12:   If the correct license daemon is not running, check the messages in 
-12:   the debug log file. Respond to the error messages. If cdslmd is not 
-12:   running, see "Daemons are not Running" section in the 'Cadence 
-12:   License Manager' in CDSDoc.
-12:
-12:2. Verify that the cdslmd license daemon is running. 
-12:
-12:   Replace lmgrd with cdslmd in the command listed above. The system 
-12:   should return a cdslmd process. If cdslmd is not running, see "Daemons
-12:   are not Running" section in the 'Cadence License License Manager' in
-12:   CDSDoc.
-12:
-12:3. If the license server is a UNIX system, use telnet to verify TCP/IP 
-12:   (the client can reach the license server). 
-12:
-12:   Platform         Command
-12:   --------         -------
-12:   HP Series 700    /usr/bin/telnet <hostname>
-12:   Others           /usr/ucb/telnet <hostname>
-12:
-12:   Use the host name listed in the license file. A UNIX license server 
-12:   must be able to telnet itself. Type Control-d to exit from telnet. 
-12:   
-12:   Note: Do not use ping. It does not adequately ensure that the client 
-12:   can reach the license server.  If you are not using .rhosts and you 
-12:   are prompted for a password on hostname, the network is configured 
-12:   correctly. 
-12:   
-12:   If connection to the license server cannot be established, the network 
-12:   is not configured correctly. See your operating system documentation.
-12:
-12:4. Verify that the host name of the license server is correct on the 
-12:   first line of the license file. The host name is case-sensitive.
-12:
-12:5. If the network is busy frequently, consider increasing the timeout 
-12:   value. 
-12:
-12:   -  Increase the timeout between the license server and the application 
-12:      client with CDS_LIC_TIMEOUT.  The default timeout is ten seconds.
-12:
-12:      Platform            Command
-12:      --------            -------
-12:      UNIX                setenv CDS_LIC_TIMEOUT <seconds>
-12:      Windows             set CDS_LIC_TIMEOUT=<seconds>
-12:
-12:   -  For fault-tolerant license servers, increase the timeout between 
-12:      the license servers by starting the license daemons with the -t 
-12:      option. The default timeout is ten seconds. To increase the timeout, 
-12:      follow these steps:
-12:
-12:      o Modify the startup file, rc.lic, to specify the -t option of 
-12:        lmgrd. Refer to the "lmgrd" man page or the lmgrd description in 
-12:        the 'Cadence License Manager' in CDSDoc for more information.
-12:
-12:      o Restart the daemons.  See the "Stopping and Starting the License
-12:        Daemons" section in the 'Cadence License Manager' in CDSDoc for
-12:        more information.
-13:ERROR (LM -13): can't find ethernet device
-13:
-13:The Ethernet device could not be located on this (VMS) system.
-14:ERROR (LM -14): license file path too long or unable to allocate memory
-14:
-14:The license manager could not allocate memory, usually because a license 
-14:file path is too long.  The combined length of all license file paths 
-14:cannot exceed 1024 characters. 
-15:ERROR (LM -15): license server communication error - try longer timeout
-15:
-15:The process could not read data from the daemon within the timeout 
-15:interval.
-15:
-15:1. Increase the timeout between the license server and the application 
-15:   client with CDS_LIC_TIMEOUT.  The default timeout is ten seconds.
-15:
-15:      Platform            Command
-15:      --------            -------
-15:      UNIX                setenv CDS_LIC_TIMEOUT <seconds>
-15:      Windows             set CDS_LIC_TIMEOUT=<seconds>
-15:
-15:2. For fault-tolerant license servers, increase the timeout between the 
-15:   license servers by starting the license daemons with the -t option.
-15:   The default timeout is ten seconds. To increase the timeout, follow
-15:   these steps:
-15:
-15:   - Modify the startup file, rc.lic, to specify the -t option of lmgrd.
-15:     Refer to the "lmgrd" man page or the lmgrd description in the 
-15:     'Cadence License Manager' in CDSDoc for more information.
-15:
-15:   - Restart the daemons.  See the "Stopping and Starting the License
-15:     Daemon" section in the 'Cadence License Manager' in CDSDoc for
-15:     more information.
-16:ERROR (LM -16): can't determine installation root from PATH
-16:
-16:The <install_dir>/tools/bin directory is not in your PATH.  The daemon
-16:cannot locate the installation root directory with its 
-16:<install_dir>/share/license/license.HOSTID files.
-16:
-16:1. Add the <install_dir>/tools/bin directory to the path. 
-16:
-16:   - For C shell, type
-16:
-16:     set path = ($path <install_dir>/tools/bin)
-16:
-16:   - For Bourne shell, type
-16:
-16:     PATH = $PATH:<install_dir>/tools/bin; export PATH
-16:
-16:2. Add the path to your .cshrc or .profile.
-16:
-16:The <install_dir> must be on the user's path.  Type "cds_root" to display
-16:the full path to the top Cadence directory.
-16:
-16:3. Verify that the tools link exists.
-17:ERROR (LM -17): license server communication error - try longer timeout
-17:
-17:The process could not write data to the daemon after the connection was 
-17:established.
-17:
-17:1. The process could not read data from the daemon within the timeout 
-17:   interval.
-17:
-17:   - Increase the timeout between the license server and the application 
-17:     client with CDS_LIC_TIMEOUT.  The default timeout is ten seconds.
-17:
-17:      Platform            Command
-17:      --------            -------
-17:      UNIX                setenv CDS_LIC_TIMEOUT <seconds>
-17:      Windows             set CDS_LIC_TIMEOUT=<seconds>
-17:
-17:   - For fault-tolerant license servers, increase the timeout between the 
-17:     license servers by starting the license daemons with the -t option.
-17:     The default timeout is ten seconds. To increase the timeout, follow 
-17:     these steps:
-17:
-17:     - Modify the startup file, rc.lic, to specify the -t option of lmgrd.
-17:       Refer to the "lmgrd" man page or the lmgrd description in the 
-17:       'Cadence License Manager' in CDSDoc for more information.
-17:
-17:     - Restart the daemons.  See the "Stopping and Starting the License
-17:       Daemon" section in the 'Cadence License Manager' in CDSDoc for
-17:       more information.
-17:
-17:2. The daemon was aborted during process operation.
-18:ERROR (LM -18): feature check-in failure detected
-18:
-18:The checkin request did not receive a proper reply from cdslmd.  The 
-18:license server might consider the license still in use or not checked
-18:out. You can ignore this message.
-19:ERROR (LM -19): user/host/display on option EXCLUDE list for feature
-19:
-19:The options file excludes the user, host, or display from using feature. 
-19:Contact your license administrator.
-20:ERROR (LM -20): user/host/display not on option INCLUDE list for feature
-20:
-20:The options file does not include the user, host, or display for this 
-20:feature.  Remember, if you have an INCLUDE line in the options file, you 
-20:automatically exclude everyone else unless you specifically include them.
-20:Contact your license administrator.
-21:ERROR (LM -21): no more licenses are available for this feature
-21:
-21:All available licenses for a particular application are in use.  You 
-21:might want to verify the timeout value for idle licenses in the options 
-21:file. To add more licenses, contact your Cadence sales representative. 
-22:ERROR (LM -22): clock setting check not available in daemon
-22:
-22:The daemon cannot verify compatible system clock settings. The system 
-22:date on the application client does not agree closely enough with the 
-22:date on the license server. The difference can be no greater than 60 days.
-23:ERROR (LM -23): license file doesn't include a license for this feature
-23:
-23:The license file does not contain a feature line for the requested 
-23:feature. 
-23:
-23:If licensing has not been configured or configured correctly, this
-23:problem can result from using the wrong license file.
-23:
-23:If licensing is configured correctly when you receive this message, 
-23:you need a new license file. Contact the Customer Response Center at 
-23:1-877-CDS-4911.
-24:ERROR (LM -24): can't find license file
-24:
-24:The application cannot find the license file.
-24:
-24:1. Use telnet to verify that the license server is not down.
-24:
-24:2. Verify that the first license file in the license file path exists. 
-24:   You see this error if the first file does not exist.
-24:
-24:3. If you are using the CDS_LIC_FILE or LM_LICENSE_FILE environment 
-24:   variable (and not using the clients file), verify that the variable 
-24:   points to the correct license file.
-24:
-24:4. The license file doesn't exist.
-24:
-24:   - Verify the existence of the license file.  If a license file does 
-24:     not exist in the share directory, mount the directory, copy the 
-24:     directory, or reinstall the license file using SoftLoad.
-24:
-24:5. For UNIX systems only:
-24:   If you are using a clients file to locate the license file, verify 
-24:   that the file is configured correctly.
-24:
-24:   - Verify that the install_dir/share/license/clients file exists.
-24:
-24:   - Verify that the location of the license file is correct in the 
-24:     install_dir/share/license/clients file.
-24:
-24:   - If a clients file does not exist in that directory, run the 
-24:     mkclients utility, or copy the clients.sample file and edit it.
-24:
-24:   - If an install_dir/share/license/clients file exists, verify that it 
-24:     includes either the correct host name of your client or an asterisk 
-24:     (*), and that the listed license file is accessible from that 
-24:     workstation.
-24:
-24:     If you do not use * as the host name in the clients file, each 
-24:     workstation running Cadence applications must have a separate entry 
-24:     in the clients file.
-24:
-24:   - Enter the correct host name (from /etc/hosts or equivalent file, not
-24:     an alias) and path information, then check out the feature again. 
-24:
-24:6. You might also see the Failed to checkout license for Lib Kit 
-24:   'library '. message.
-25:ERROR (LM -25): unable to determine search path - check PATH setting
-25:
-25:For some unknown reason, your PATH environment cannot be determined
-25:using conventional (UNIX) methods.
-25:
-25:1. Verify that the install_dir/tools/bin directory is in your PATH.
-25:
-25:2. Verify that PATH is exported (Bourne or Korn shell) or is a global
-25:   environment variable.
-26:ERROR (LM -26): can't read license file - check license file permissions
-26:
-26:1. The license file is not readable, probably because the system 
-26:   permissions of the license file prohibit read access.
-26:
-26:2. If you are using the clients file and the permissions on the license 
-26:   file are correct, check the permissions on the clients file because 
-26:   the license file cannot be found if the clients file is not readable.
-27:ERROR (LM -27): inconsistency detected in license file
-27:
-27:You need a new license file.  Reinstall the license file with SoftLoad, or
-27:contact the Customer Response Center at 1-877-CDS-4911. 
-28:ERROR (LM -28): no SERVER lines in license file
-28:
-28:You need a new license file.  Reinstall the license file with SoftLoad, or 
-28:contact the Customer Response Center at 1-877-CDS-4911. 
-29:ERROR (LM -29): TCP port not specified on license file SERVER line
-29:
-29:The SERVER line in the license file has no TCP/IP port number, and 
-29:no TCP/IP FLEXlm service exists in /etc/services. See the FLEXlm 
-29:documentation available on the World Wide Web, http://www.globetrotter.com.
-29:
-29:1. Add an unused port. 
-29:
-29:2. You might need a new license file. Reinstall the license file with 
-29:   SoftLoad, or contact the Customer Response Center at 1-877-CDS-4911
-30:ERROR (LM -30): license server does not support this feature
-30:
-30:1. Use the lmstat utility to verify that the license server daemons are
-30:   up and running.
-30:
-30:   lmstat -a -c license_file
-30:   		or
-30:   lmutil lmstat -a -c license_file
-30:
-30:2. The feature is not supported because
-30:
-30:   - The feature on the license server expired
-30:   - The feature has not yet started (the start date has not arrived)
-30:   - The version requested is greater than the highest supported version
-30:3. Contact the Customer Response Center at 1-877-CDS-4911.
-31:ERROR (LM -31): this host is not licensed to run this feature
-31:
-31:None of the host IDs specified in license files match the host ID
-31:of the system attempting to run the application.
-32:ERROR (LM -32): the VMS logical CDS_ROOT has not been set
-32:
-32:On a VAX/VMS system, the CDS_ROOT logical must point to the installation
-32:directory.  This variable identifies the directory in which the Cadence
-32:software is installed.
-33:ERROR (LM -33): license file does not support this version of the feature
-33:
-33:The version specified in the checkout request for this feature is higher
-33:than the version number of the feature the daemon supports.  Contact the 
-33:Customer Response Center at 1-877-CDS-4911.
-34:ERROR (LM -34): license for feature is not yet time-enabled
-34:
-34:The feature is not enabled yet.  The current date is before the feature 
-34:start date.
-35:ERROR (LM -35): license for feature has expired
-35:
-35:The feature has expired.  Today's date is after the expiration date in 
-35:the license file.  Contact the Customer Response Center at 1-877-CDS-4911.
-36:ERROR (LM -36): unable to contact license server - session exiting
-36:
-36:Cadence products revalidates licenses periodically and could not reconnect
-36:to the daemon within the specified threshold value.  The current process 
-36:is aborting.  The communication to the license server was interrupted for
-36:some reason while the program was executing.  
-36:
-36:1. Use telnet to verify TCP/IP (the client can reach the license server). 
-36:
-36:2. Use lmstat -a to verify that the license daemons are running correctly.
-37:ERROR (LM -37): more features are requested than are licensed
-37:
-37:An application attempted to check out more features than are in the 
-37:license file feature line, such as three licenses when only two licenses 
-37:are available in the license file.
-38:ERROR (LM -38): machine or process limitation - can't get <number> bytes)
-38:
-38:The license manager cannot allocate the specified number of bytes. 
-38:This problem is usually caused by computer or process limitations.
-38:
-38:The license file path might be too long. The combined length of all 
-38:license file paths in the license finder or in the list below cannot 
-38:exceed 1024 characters.
-38:
-38:1. CDS_LIC_FILE
-38:
-38:2. LM_LICENSE_FILE
-38:
-38:3. Applicable contents of the clients file
-38:
-38:4. Default location of install_dir/share/license/license.dat (for UNIX)
-38:   Default location of c:\cdslic\license.dat (for Windows)
-39:ERROR (LM -39): function/program set by CDS_SKILL_LICFLTR or CDS_LICFLTR 
-39:                is not defined or does not exist
-39:
-39:You have set the CDS_LICFLTR, CDS_SKILL_LICFLTR or both.
-39:
-39:1. If you have set the CDS_LICFLTR variable, then you must be able to 
-39:   access the program.  If the program is not in the current directory,
-39:   specify full path to the it.
-39:
-39:2. If you have set the CDS_SKILL_LICFLTR variable, then make sure the 
-39:   SKILL function specified is defined.
-39:
-39:3. If both the variables are set, then make sure the SKILL function 
-39:   specified by CDS_SKILL_LICFLTR is defined.
-39:
-39:Contact your license administrator.
-40:ERROR (LM -40): function/program set by CDS_SKILL_LICFLTR or CDS_LICFLTR 
-40:                returned an error status 
-40:
-40:1. If you have set the CDS_LICFLTR variable, then the program returned a 
-40:   non-zero status.
-40:
-40:2. If you have set the CDS_SKILL_LICFLTR variable, then the SKILL function
-40:    returned a nil status.
-40:
-40:3. If both the variables are set, then the SKILL function specified by
-40:   CDS_SKILL_LICFLTR returned a nil status.
-40:
-40:Contact your license administrator.
-41:ERROR (LM -41): program set by CDS_LICFLTR must have read and execute 
-41:                permissions
-41:
-41:You (as owner, group, or other) must have read and execute permission
-41:on this program.
-41:
-41:Contact your license administrator.
-42:ERROR (LM -42): program set by CDS_LICFLTR is not an executable file
-42:
-42:The program specified is not a regular executable/script file.
-42:- make sure it is not a directory, block device etc.
-42:
-42:Contact your license administrator.
-43:ERROR (LM -43): vfork failed while executing program set by CDS_LICFLTR
-43:
-43:Cannot fork a child process to run the program set by CDS_LICFLTR
-43:The vfork manual page describes some of the reasons why vfork might fail. 
-43:The solutions include increasing your swap space.
-43:
-43:See the fork man page or contact your system administrator.
-44:ERROR (LM -44): exec failed while executing program set by CDS_LICFLTR
-44:
-44:exec cannot load program set by CDS_LICFLTR
-44:
-44:Contact your license administrator.
-44:
-44:This could be due to the following:
-44:
-44:1. The program is a zero length file.
-44:
-44:2. The program specified is not of the correct format.  
-44:
-44:   - If the program is a script make sure it has the correct header, 
-44:     eg. #!/bin/sh, #!/bin/csh etc... 
-44:
-44:   - If the program is a binary, make sure it is for the platform it is 
-44:     being run.
-44:
-44:See the exec man page for more information.
-45:ERROR (LM -45): program set by CDS_LICFLTR was terminated by a signal
-45:
-45:The CDS_LICFLTR program received a signal, usually a kill signal from 
-45:the user. Try to start the application again.
-46:ERROR (LM -46): the protocol version used encode/decode the token is not 
-46:                supported
-46:
-46:This error occurs when an application creates/decodes a token.
-46:This is an internal error within the application.
-46:
-46:Refer to application specific documentation for more information.
-47:ERROR (LM -47): this token has expired. It can no longer be used
-47:
-47:This error occurs when an application decodes a token.
-47:This is an internal error within the application.
-47:
-47:Refer to application specific documentation for more information.
-48:ERROR (LM -48): the token input data exceeds the maximum allowed limit
-48:
-48:This error occurs when an application creates a token.
-48:This is an internal error within the application.
-48:
-48:Refer to application specific documentation for more information.
-49:ERROR (LM -49): the token input data is empty
-49:
-49:This error occurs when an application creates a token.
-49:This is an internal error within the application.
-49:
-49:Refer to application specific documentation for more information.
-50:ERROR (LM -50): the token is corrupted. Cannot decode
-50:
-50:This error occurs when an application decodes a token.
-50:This is an internal error within the application. 
-50:
-50:Refer to application specific documentation for more information.
-51:ERROR (LM -51): cannot decode token. Check user key
-51:
-51:This error occurs when an application decodes a token.
-51:This is an internal error within the application. 
-51:
-51:Refer to application specific documentation for more information.
-52:ERROR (LM -52): cannot read token
-52:
-52:This error occurs when an application decodes a token.
-52:This is an internal error within the application. 
-52:
-52:Refer to application specific documentation for more information.
-53:ERROR (LM -53): an internal error occurred while encoding/decoding the token
-53:
-53:This error occurs when an application creates/decodes a token.
-53:This is an internal error within the application.
-53:
-53:Refer to application specific documentation for more information.
-55:ERROR (LM -55): a different version of this feature had already been
-55:                checked out. Attempt to check out another version is not
-55:                allowed.
-55:
-55:This error occurs when an application checks out a different version of an
-55:already checked out feature.
-55:This is an internal error within the application.
-55:
-55:Refer to application specific documentation for more information.
-56:ERROR (LM -56): unable to validate licenses. No work can be done without
-56:                a valid license. Will wait and try again to validate the
-56:                licenses in <num_sec> seconds.
-56:
-56:This error occurs when an application is still unable to validate its
-56:licenses after two tries.
100:WARNING (LM 100): waiting <num_sec> seconds to regain <feature> license
100:
100:If the connection to the daemon is lost, num_sec increases as the 
100:application tries to reconnect.  If the daemons are running, this 
100:warning message can indicate the network is not operating properly. 
100:
100:1. Verify that the lmgrd daemon is running.
100:
100:   For Unix systems:
100:   =================
100:
100:   Log into the license server and type the appropriate command. 
100:
100:   Platform                Command
100:   --------                -------
100:   HP Series 700           ps -edaf | grep lmgrd | grep -v grep
100:   IBM RS/6000             ps waux  | grep lmgrd | grep -v grep
100:   Linux                   ps -waux | grep lmgrd | grep -v grep
100:                           ps -edaf | grep lmgrd | grep -v grep 
100:   Solaris                 ps -waux | grep lmgrd | grep -v grep
100:                           ps -edaf | grep lmgrd | grep -v grep 
100:   SunOS 4.1.3             ps -waux | grep lmgrd | grep -v grep
100:
100:   The system should return a lmgrd process. If nothing is returned, the 
100:   license manager daemon is not running. 
100:   
100:
100:   For Windows NT:
100:   ===============
100:
100:   Use Task Manager to check if lmgrd.exe is running. To run Task
100:   Manager, right-click on the toolbar, then click Task Manager.
100:   and then click the Processes tab.
100:
100:   If the correct license daemon is not running, check the messages in 
100:   the debug log file. Respond to the error messages. If cdslmd is not 
100:   running, see "Daemons are not Running" section in the 'Cadence 
100:   License Manager' in CDSDoc.
100:
100:2. Verify that the application client can reach the license server using 
100:   the command listed below, replacing <hostname> with the name of the 
100:   license server listed in the license file. 
100:
100:   Platform         Command
100:   --------         -------
100:   HP Series 700    /usr/bin/telnet <hostname>
100:   Others           /usr/ucb/telnet <hostname>
100:
100:   Note: Do not use ping. It does not adequately ensure that the client 
100:   can reach the license server. If you are not using .rhosts and you are 
100:   prompted for a password on hostname, the network is configured 
100:   correctly. 
100:   
100:   Type Control-d to exit from telnet. If the network is not configured
100:   correctly, see your operating system documentation.
100:
100:3. Increase the timeout between the license server and the application 
100:   client with CDS_LIC_TIMEOUT.  The default timeout is ten seconds.
100:
100:      Platform            Command
100:      --------            -------
100:      UNIX                setenv CDS_LIC_TIMEOUT <seconds>
100:      Windows             set CDS_LIC_TIMEOUT=<seconds>
100:
100:4. For fault-tolerant license servers, increase the timeout between the 
100:   license servers by starting the license daemons with the -t option.
100:   The default timeout is ten seconds. To increase the timeout, follow
100:   these steps:
100:
100:   - Modify the startup file, rc.lic, to specify the -t option of lmgrd.
100:     Refer to the "lmgrd" man page or the lmgrd description in the 
100:     'Cadence License Manager' in CDSDoc for more information.
100:
100:   - Restart the daemons.  See the "Stopping and Starting the License
100:     Daemons" section in the 'Cadence License Manager' in CDSDoc for
100:     more information.
101:WARNING (LM 101): maximum search path length of <max_length> exceeded - 
101:                  ignoring excess
101:
101:The combined length of license file names exceeds 1024 characters in the 
101:
101:1. CDS_LIC_FILE
101:
101:2. LM_LICENSE_FILE
101:
101:3. Applicable contents of the clients file
101:
101:4. Default location of install_dir/share/license/license.dat
101:
101:The excess data is ignored.
102:WARNING (LM 102): unable to validate licenses.
102:
102:This warning occurs when an application is unable to validate its licenses
102:the first time.
103:WARNING (LM 103): unable to validate licenses.
103:
103:This warning occurs when an application is unable to validate its licenses
103:the second time.
# 10.8 error codes
LMC-501:INFO (LMC-501): Regained all licenses. All licenses OK.
LMC-701:WARNING (LMC-701): Max search path length exceeded - extra ignored.
LMC-701:
LMC-701:The combined length of license server search path specified in the
LMC-701:   CDS_LIC_FILE,
LMC-701:   LM_LICENSE_FILE and
LMC-701:   Applicable contents of the clients file,
LMC-701:   the Default location of install_dir/share/license/license.dat
LMC-701:exceed the MAXPATHLEN on Unix systems. Typically this is 1024 chars.
LMC-701:For Windows the limit is hardcoded to 512. The excess data is ignored.
LMC-701:If you use LM_LICENSE_FILE to specify other vendors search path, Cadence
LMC-701:recommends that you use CDS_LIC_ONLY variable, which will limit your search
LMC-701:path to CDS_LIC_FILE for Cadence applications.
LMC-702:WARNING (LMC-702): Unable to validate license feature(s)(first attempt). After the third attempt the application will wait indefinitely until the licenses become available.
LMC-702:
LMC-702:Applications revalidate licenses periodically and could not reconnect to
LMC-702:the license daemon within the specified threshold value. This happens if the
LMC-702:application is unable to communicate with the license server or,
LMC-702:if the license was reclaimed by the server and allocated to another user.
LMC-702:  1. Use telnet to verify TCP/IP (the client can reach the license server).
LMC-702:  2. Use lmstat -a to verify that the license daemons are running correctly.
LMC-703:WARNING (LMC-703): Unable to validate license feature(s)(second attempt). After the third attempt the application will wait indefinitely until the licenses become available.
LMC-703:
LMC-703:Applications revalidate licenses periodically and could not reconnect to
LMC-703:the daemon within the specified threshold value. This happens if the
LMC-703:application is unable to communicate with the license server or,
LMC-703:if the license was reclaimed by the server and allocated to another user.
LMC-703:  1. Use telnet to verify TCP/IP (the client can reach the license server).
LMC-703:  2. Use lmstat -a to verify that the license daemons are running correctly.
LMC-801:ERROR (LMC-801): The protocol version used encode/decode the token is not supported.
LMC-801:
LMC-801:This error occurs when an application creates/decodes a token. This is an
LMC-801:internal error within the application. Refer to application specific
LMC-801:documentation for more information.
LMC-802:ERROR (LMC-802): This token has expired. It can no longer be used.
LMC-802:
LMC-802:This error occurs when an application decodes a token. This is an internal
LMC-802:error within the application. Refer to application specific documentation
LMC-802:for more information.
LMC-803:ERROR (LMC-803): The token input data exceeds the maximum allowed limit.
LMC-803:
LMC-803:This error occurs when an application creates a token. This is an internal
LMC-803:error within the application. Refer to application specific documentation
LMC-803:for more information.
LMC-804:ERROR (LMC-804): The token input data is empty.
LMC-804:
LMC-804:This error occurs when an application creates a token. This is an internal
LMC-804:error within the application. Refer to application specific documentation
LMC-804:for more information.
LMC-805:ERROR (LMC-805): The token is corrupted. Unable to decode.
LMC-805:
LMC-805:This error occurs when an application decodes a token. This is an internal
LMC-805:error within the application. Refer to application specific documentation
LMC-805:for more information.
LMC-806:ERROR (LMC-806): Cannot decode token. Check user key.
LMC-806:
LMC-806:This error occurs when an application decodes a token. This is an internal
LMC-806:error within the application. Refer to application specific documentation
LMC-806:for more information.
LMC-807:ERROR (LMC-807): Cannot read token.
LMC-807:
LMC-807:This error occurs when an application decodes a token. This is an internal
LMC-807:error within the application. Refer to application specific documentation
LMC-807:for more information.
LMC-808:ERROR (LMC-808): An internal error occurred while encoding/decoding the token.
LMC-808:
LMC-808:This error occurs when an application creates/decodes a token. This is an
LMC-808:internal error within the application. Refer to application specific
LMC-808:documentation for more information.
LMC-901:ERROR (LMC-901): Internal API error occured. Licensing API not initialized.
LMC-901:
LMC-901:This is a Cadence internal error. Contact Cadence support at
LMC-901:support@cadence.com for further assistance.
LMC-902:ERROR (LMC-902): Can't find license file.
LMC-902:
LMC-902:The application cannot find a valid license file or port@host address to
LMC-902:connect with the license server. Verify that the first license file or
LMC-902:port@host address in the license file path is valid. You see this error if
LMC-902:the first entry is not valid. Make sure your CDS_LIC_FILE and LM_LICENSE_FILE
LMC-902:environment variable is pointing to a correct license file or port@host
LMC-902:address.
LMC-903:ERROR (LMC-903): Malloc failed. Not enough memory.
LMC-903:
LMC-903:This is a Cadence internal error. Contact Cadence support at
LMC-903:support@cadence.com for further assistance.
LMC-904:ERROR (LMC-904): Function/program set by CDS_SKILL_LICFLTR or CDS_LICFLTR is not defined or does not exist.
LMC-904:
LMC-904:You have set the CDS_LICFLTR, CDS_SKILL_LICFLTR or both.
LMC-904:  1. If you have set the CDS_LICFLTR variable, then you must be able to
LMC-904:     access the program. If the program is not in the current directory,
LMC-904:     specify full path to it.
LMC-904:  2. If you have set the CDS_SKILL_LICFLTR variable, then make sure the
LMC-904:     SKILL function specified is defined.
LMC-904:  3. If both the variables are set, then make sure the SKILL function
LMC-904:     specified by CDS_SKILL_LICFLTR is defined. Contact your license
LMC-904:     administrator.
LMC-905:ERROR (LMC-905): Function/program set by CDS_SKILL_LICFLTR or CDS_LICFLTR returned an error status.
LMC-905:
LMC-905:Your filter program filed with a error status.
LMC-905:  1. If you have set the CDS_LICFLTR variable, then the program returned a
LMC-905:     non-zero status.
LMC-905:  2. If you have set the CDS_SKILL_LICFLTR variable, then the SKILL function
LMC-905:     returned a nil status.
LMC-905:  3. If both the variables are set, then the SKILL function specified by
LMC-905:     CDS_SKILL_LICFLTR returned a nil status. Contact your license
LMC-905:     administrator.
LMC-906:ERROR (LMC-906): Program set by CDS_LICFLTR must have read and execute permissions.
LMC-906:
LMC-906:You (as owner, group, or other) must have read and execute permission on
LMC-906:this program. Contact your license administrator.
LMC-907:ERROR (LMC-907): Program set by CDS_LICFLTR is not an executable file.
LMC-907:
LMC-907:The program specified is not a regular executable/script file. Make sure it
LMC-907:is not a directory, block device etc.
LMC-908:ERROR (LMC-908): vfork() failed while executing program set by CDS_LICFLTR.
LMC-908:
LMC-908:Cannot fork a child process to run the program set by CDS_LICFLTR.
LMC-908:The vfork manual page describes some of the reasons why vfork might fail.
LMC-908:The solutions include increasing your swap space. See the fork man page or
LMC-908:contact your system administrator.
LMC-909:ERROR (LMC-909): exec() failed while executing program set by CDS_LICFLTR.
LMC-909:
LMC-909:exec cannot load program set by CDS_LICFLTR
LMC-909:
LMC-909:This could be due to the following:
LMC-909:  1. The program is a zero length file.
LMC-909:  2. The program specified is not of the correct format.
LMC-909:     - If the program is a script make sure it has the correct header,
LMC-909:       eg. #!/bin/sh, #!/bin/csh etc... 
LMC-909:     - If the program is a binary, make sure it is for the platform it is
LMC-909:       being run.
LMC-909:
LMC-909:See the exec man page for more information. Contact your license administrator.
LMC-910:ERROR (LMC-910): Program set by CDS_LICFLTR was terminated by a signal.
LMC-910:
LMC-910:The CDS_LICFLTR program received a signal, usually a kill signal from the
LMC-910:user. Try to start the application again.
LMC-911:ERROR (LMC-911): A different version of this feature has already been checked out. Attempt to check out another version is not allowed.
LMC-911:
LMC-911:Contact Cadence support at support@cadence.com for further assistance.
LMC-912:ERROR (LMC-912): Unable to validate license features checked out by the application.
LMC-912:
LMC-912:The application is unable to validate the license features it had checked
LMC-912:out earlier. This happens if the application is unable to communicate with
LMC-912:the license server or, if the license was reclaimed by the server and
LMC-912:allocated to another user. Cadence applications validate the license features
LMC-912:with the license server periodically. If the application cannot validate all
LMC-912:the licenses, the application will block indefinitely ( and queue ) until it
LMC-912:can regain all the licenses.
LMC-913:ERROR (LMC-913): Attempting to regain lost licenses.
LMC-914:ERROR (LMC-914): Unable to validate license features checked out by the application. Application will now wait until all the licenses become available again.
LMC-914:
LMC-914:Even the third attempt to regaing the licenses failed. The application will
LMC-914:now block indefinetely ( and queue ) for a license until it can regain all
LMC-914:the licenses.
LMC-915:ERROR (LMC-915): Unable to contact license server - session exiting.
LMC-915:
LMC-915:Applications revalidate licenses periodically and could not reconnect
LMC-915:to the daemon within the specified threshold value. The current process
LMC-915:is aborting. The communication to the license server was interrupted for
LMC-915:some reason while the program was executing.
LMC-915:  1. Use telnet to verify TCP/IP (the client can reach the license server).
LMC-915:  2. Use lmstat -a to verify that the license daemons are running correctly.
LMC-916:ERROR (LMC-916): Wrong quantity specified during check-in. The check-in quantity must match the checkout quantity.
LMC-916:
LMC-916:This is a Cadence internal error. Contact Cadence support at
LMC-916:support@cadence.com for further assistance.
LMF-001:ERROR (LMF-001): Cannot find license file.
LMF-001:
LMF-001:The application cannot find a valid license file or port@host address to
LMF-001:connect with the license server. Verify that the first license file or
LMF-001:port@host address in the license file path is valid. You see this error if
LMF-001:the first entry is not valid. Make sure your CDS_LIC_FILE and LM_LICENSE_FILE
LMF-001:environment variable is pointing to a correct license file or port@host address.
LMF-002:ERROR (LMF-002): Invalid license file syntax.
LMF-002:
LMF-002:You need a new license file.
LMF-002:Reinstall the license file with Cadence Installation Software or contact
LMF-002:Cadence support at support@cadence.com for further assistance.
LMF-003:ERROR (LMF-003): No license server system for this feature.
LMF-003:
LMF-003:The daemon name specified in the license file FEATURE line does not match
LMF-003:the vendor daemon name specified in the VENDOR or DAEMON line.
LMF-003:
LMF-003:Contact Cadence support at support@cadence.com for further assistance.
LMF-004:ERROR (LMF-004): Licensed number of users already reached.
LMF-004:
LMF-004:All available licenses for a particular application are in use.
LMF-004:To add more licenses, contact your Cadence Sales Representative or Cadence
LMF-004:support at support@cadence.com for further assistance.
LMF-005:ERROR (LMF-005): No such feature exists.
LMF-005:
LMF-005:The license server does not serve the requested feature.
LMF-005:If licensing has not been configured correctly, this problem can result from
LMF-005:using the wrong license file. If licensing is configured correctly when you
LMF-005:receive this message, you need a new license file.
LMF-005:
LMF-005:Contact Cadence support at support@cadence.com for further assistance.
LMF-006:ERROR (LMF-006): No port number in license file and \"FLEXlm\" service does not exist.
LMF-006:
LMF-006:This happens if the SERVER line does not specify a TCP/IP port number,
LMF-006:and the TCP/IP license service does not exist in /etc/services.
LMF-006:Make sure you specify an unused port ( Cadence ships with 5280 as default )
LMF-006:in the SERVER line. See the FLEXnet Users Guide for more information on
LMF-006:specifying the TCP/IP FLEXlm service in the /etc/services file.
LMF-007:ERROR (LMF-007): No socket connection to license server manager.
LMF-007:
LMF-007:Application attempted to diconnect from the server after the process had
LMF-007:already been disconnected from the license server.
LMF-007:
LMF-007:Contact Cadence support at support@cadence.com for further assistance.
LMF-008:ERROR (LMF-008): Invalid (inconsistent) license key.
LMF-008:
LMF-008:The encryption code in license file is inconsistent.
LMF-008:This error occurs when the license file contains a corrupted FEATURE line for
LMF-008:the requested application. You need a new license file. Reinstall the license
LMF-008:file with Cadence Installation Software or contact Cadence support at
LMF-008:support@cadence.com for further assistance.
LMF-009:ERROR (LMF-009): Invalid host.
LMF-009:
LMF-009:The nodelocked hostid specified in the license server for the feature the
LMF-009:application requested, does not match the hostid of the machine where the
LMF-009:application is running.
LMF-010:ERROR (LMF-010): Feature has expired.
LMF-010:
LMF-010:The feature has expired. Today's date is after the expiration date in the
LMF-010:license file.
LMF-010:
LMF-010:Contact Cadence support at support@cadence.com for further assistance.
LMF-011:ERROR (LMF-011): Invalid date format in license file.
LMF-011:
LMF-011:The start date, expiration date or the issue date specified in the license
LMF-011:file is not valid. You need a new license file.
LMF-011:
LMF-011:Contact Cadence support at support@cadence.com for further assistance.
LMF-012:ERROR (LMF-012): Invalid returned data from license server system.
LMF-012:
LMF-012:Communication failed between the application and the license server.
LMF-012:Perhaps, the license server did not respond to the application within the
LMF-012:timeout period because of a busy network or due to server being busy due to
LMF-012:a high volume of checkouts. If the license server is busy and not responding
LMF-012:you need to restart the license server. If the network is frequently busy
LMF-012:and your application is timing out, consider the following options,
LMF-012:
LMF-012:  1. The amount of data sent between the license server and the client
LMF-012:     is minimal. But Cadence applications check with the license server
LMF-012:     periodically. So it is important that the connectivity time between the
LMF-012:     license server and the client is fast.
LMF-012:
LMF-012:  2. A local license server as the primary license server and a central
LMF-012:     server as a backup is also recommended.
LMF-012:  3. For fault-tolerant license servers, increase the heartbeat interval
LMF-012:     between the license servers by specifying the interval value in the
LMF-012:     SERVER line in the license file. For more information on setting the
LMF-012:     heartbeat interval refer to FLEXnet Users Guide.
LMF-013:ERROR (LMF-013): No SERVER lines in license file.
LMF-013:
LMF-013:There should be at least one SERVER line in the license file. Reinstall
LMF-013:the license file with Cadence Installation Software or contact
LMF-013:Cadence support at support@cadence.com for further assistance.
LMF-014:ERROR (LMF-014): Cannot find SERVER hostname in network database.
LMF-014:
LMF-014: The application cannot contact the hostname specified in the SERVER line
LMF-014:of the license file. Verify the host name in the /etc/hosts file, NIS and
LMF-014:DNS entries. Also verify that the client can reach the license server using
LMF-014:the telnet command. The workaround is to use IP-Address
LMF-014:(e.g., 123.456.789.123) instead of hostname.
LMF-015:ERROR (LMF-015): Cannot connect to license server system.
LMF-015:
LMF-015:The client cannot connect to the license server. If lmstat indicates the
LMF-015:daemons are running, this error message can indicate that the network is not
LMF-015:working properly. Verify that the client can reach the license server using
LMF-015:the telnet command. You can also encounter this problem in a busy network.
LMF-015:If the network is frequently busy and your application is timing out,
LMF-015:consider the following options,
LMF-015:
LMF-015:  1. The amount of data sent between the license server and the client
LMF-015:     is minimal. But Cadence applications check with the license server
LMF-015:     periodically. So it is important that the connectivity time between the
LMF-015:     license server and the client is fast.
LMF-015:
LMF-015:  2. A local license server as the primary license server and a central
LMF-015:     server as a backup is also recommended.
LMF-015:
LMF-015:  3. For fault-tolerant license servers, increase the heartbeat interval
LMF-015:     between the license servers by specifying the interval value in the
LMF-015:     SERVER line in the license file. For more information on setting the
LMF-015:     heartbeat interval refer to FLEXnet Users Guide.
LMF-016:ERROR (LMF-016): Cannot read data from license server system.
LMF-016:
LMF-016:Communication failed between the application and the license server.
LMF-016:Perhaps, the license server did not respond to the application within the
LMF-016:timeout period because of a busy network or due to server being busy due to
LMF-016:a high volume of checkouts. The license server could have also died before
LMF-016:the application attempted to read data from it. If the license server is
LMF-016:busy and not responding or if the vendor daemon died, you may need to
LMF-016:restart the license server. If the network is frequently busy and the
LMF-016:application is timing out, consider the following options,
LMF-016:
LMF-016:  1. The amount of data transferred between the license server and the client
LMF-016:     is minimal. But Cadence applications check with the license server
LMF-016:     periodically. So it is important that the connectivity time between the
LMF-016:     license server and the client is fast.
LMF-016:
LMF-016:  2. A local license server as the primary license server and a central
LMF-016:     server as a backup is also recommended.
LMF-016:
LMF-016:  3. For fault-tolerant license servers, increase the heartbeat interval
LMF-016:     between the license servers by specifying the interval value in the
LMF-016:     SERVER line in the license file. For more information on setting the
LMF-016:     heartbeat interval refer to FLEXnet Users Guide.
LMF-017:ERROR (LMF-017): Cannot write data to license server system.
LMF-017:
LMF-017:Communication failed between the application and the license server.
LMF-017:Perhaps, the license server did not respond to the application within the
LMF-017:timeout period because of a busy network or due to server being busy due to
LMF-017:a high volume of checkouts. The license server could have also died before
LMF-017:the application attempted to read data from it. If the license server is
LMF-017:busy and not responding or if the vendor daemon died, you may need to
LMF-017:restart the license server. If the network is frequently busy and the
LMF-017:application is timing out, consider the following options,
LMF-017:
LMF-017:  1. The amount of data transferred between the license server and the client
LMF-017:     is minimal. But Cadence applications check with the license server
LMF-017:     periodically. So it is important that the connectivity time between the
LMF-017:     license server and the client is fast.
LMF-017:
LMF-017:  2. A local license server as the primary license server and a central
LMF-017:     server as a backup is also recommended.
LMF-017:
LMF-017:  3. For fault-tolerant license servers, increase the heartbeat interval
LMF-017:     between the license servers by specifying the interval value in the
LMF-017:     SERVER line in the license file. For more information on setting the
LMF-017:     heartbeat interval refer to FLEXnet Users Guide.
LMF-018:ERROR (LMF-018): License server system does not support this feature.
LMF-018:
LMF-018:The feature is probably not supported because
LMF-018:  - the feature on the license server expired or,
LMF-018:  - the feature has not yet started (the start date has not arrived) or,
LMF-018:  - the version requested is greater than the highest supported version
LMF-018:
LMF-018:Contact Cadence support at support@cadence.com for further assistance.
LMF-019:ERROR (LMF-019): Error in select system call.
LMF-019:
LMF-019:The select system call failed.
LMF-020:ERROR (LMF-020): License server system busy (no majority).
LMF-020:
LMF-020:The license server is busy establishing a quorum in fault-tolerant
LMF-020:configration so that licensing can start. This error is very rare, and
LMF-020:checkout should be retried if this occurs.
LMF-021:ERROR (LMF-021): License file does not support this version.
LMF-021:
LMF-021:The version requested by the application for this feature is higher than
LMF-021:the version number of the feature the daemon supports.
LMF-021:
LMF-021:Contact Cadence support at support@cadence.com for further assistance.
LMF-022:ERROR (LMF-022): Feature checkin failure detected with license server system.
LMF-022:
LMF-022:The checkin request did not receive a proper reply from the license server.
LMF-022:You can ignore this message.
LMF-023:ERROR (LMF-023): License server system temporarily busy (new server connecting).
LMF-023:
LMF-023:The license server is busy establishing a quorum in fault-tolerant
LMF-023:configration so that licensing can start. New requests from applications are
LMF-023:deferred during this period. This request should be retried.
LMF-025:ERROR (LMF-025): License server system does not support this version of this feature.
LMF-025:
LMF-025:The version requested by the application for this feature is higher than
LMF-025:the version number of the feature the daemon supports.
LMF-025:
LMF-025:Contact Cadence support at support@cadence.com for further assistance.
LMF-026:ERROR (LMF-026): Request for more licenses than this feature supports.
LMF-026:
LMF-026:Application attempted to check out more features than there are in the
LMF-026:license file feature line, such as, three licenses when only two licenses
LMF-026:are available in the license file.
LMF-027:ERROR (LMF-027): Cannot read /dev/kmem.
LMF-027:
LMF-027:Application attempted to read /dev/kmem and failed.
LMF-028:ERROR (LMF-028): Cannot read /vmunix.
LMF-028:
LMF-028:Application cannot read /vmunix and failed.
LMF-029:ERROR (LMF-029): Cannot find ethernet device.
LMF-029:
LMF-029:Application cannot locate the ethernet device on the machine.
LMF-030:ERROR (LMF-030): Cannot read license file.
LMF-030:
LMF-030:The license file is not readable, probably because the system permissions
LMF-030:of the license file prohibit read access. If you are using the clients file
LMF-030:and the permissions on the license file are correct, check the permissions
LMF-030:on the clients file because the license file cannot be found if the clients
LMF-030:file is not readable.
LMF-031:ERROR (LMF-031): Feature start date is in the future.
LMF-031:
LMF-031:The feature is not enabled yet. The current date is before the feature start
LMF-031:date.
LMF-032:ERROR (LMF-032): No such attribute.
LMF-032:
LMF-032:Application used a unknown attribute with the FLEXnet get and set attribute
LMF-032:API's.
LMF-032:
LMF-032:Contact Cadence support at support@cadence.com for further assistance.
LMF-033:ERROR (LMF-033): Bad encryption handshake with vendor daemon.
LMF-033:
LMF-033:This handshake operation between Cadence vendor daemon and lmgrd failed.
LMF-033:Use lmstat -a to verify that the daemons are up and running properly on
LMF-033:server. If lmstat indicates that the daemons are not running, you must
LMF-033:restart the license daemons.
LMF-034:ERROR (LMF-034): Clock difference too large between client and license server system.
LMF-034:
LMF-034:The system date on the client does not agree closely enough with the date
LMF-034:on the license server.
LMF-034:
LMF-034:Contact Cadence support at support@cadence.com for further assistance.
LMF-036:ERROR (LMF-036): Feature database corrupted in vendor daemon.
LMF-036:
LMF-036:The daemon's run-time feature data structures have become corrupted. This
LMF-036:is an internal daemon error.
LMF-036:
LMF-036:Contact Cadence support at support@cadence.com for further assistance.
LMF-037:ERROR (LMF-037): Duplicate selection mismatch for this feature.
LMF-037:
LMF-037:A feature was checked out with one license type (dupgroup), and then another
LMF-037:attempt was made to check out the same feature with a different license type.
LMF-037:A feature can only be checked out using one license type. Either the license
LMF-037:file has two feature lines of incompatible types, or two different
LMF-037:applications are checking out the same feature in different ways.
LMF-037:
LMF-037:Contact Cadence support at support@cadence.com for further assistance.
LMF-038:ERROR (LMF-038): User/host on EXCLUDE list for feature.
LMF-038:
LMF-038:The options file excludes the user, host, or display from using feature.
LMF-038:
LMF-038:Contact your license administrator or contact Cadence support at
LMF-038:support@cadence.com for further assistance.
LMF-039:ERROR (LMF-039): User/host not on INCLUDE list for feature.
LMF-039:
LMF-039:The options file does not include the user, host, or display for this
LMF-039:feature. If you have an INCLUDE line in the options file you automatically
LMF-039:exclude everyone else unless you specifically include them.
LMF-039:
LMF-039:Contact your license administrator or contact Cadence support at
LMF-039:support@cadence.com for further assistance.
LMF-040:ERROR (LMF-040): Cannot allocate dynamic memory.
LMF-040:
LMF-040:malloc failed to allocate sufficient memory.
LMF-040:
LMF-040:Contact Cadence support at support@cadence.com for further assistance.
LMF-041:ERROR (LMF-041): Feature was never checked out.
LMF-041:
LMF-041:Application attempted to check the status of a feature that was never
LMF-041:checked out.
LMF-041:
LMF-041:Contact Cadence support at support@cadence.com for further assistance.
LMF-042:ERROR (LMF-042): Invalid parameter.
LMF-042:
LMF-042:Application specified an invalid attribute with the FLEXnet get and set
LMF-042:attribute API's.
LMF-042:
LMF-042:Contact Cadence support at support@cadence.com for further assistance.
LMF-043:ERROR (LMF-043): No key data supplied in call to lc_new_job() or lc_init().
LMF-043:
LMF-043:Application specified no key data during FLEXnet initialization.
LMF-043:
LMF-043:Contact Cadence support at support@cadence.com for further assistance.
LMF-044:ERROR (LMF-044): Invalid key data supplied.
LMF-044:
LMF-044:Application specified incorrect key data during FLEXnet initialization.
LMF-044:
LMF-044:Contact Cadence support at support@cadence.com for further assistance.
LMF-045:ERROR (LMF-045): Function not available in this version.
LMF-045:
LMF-045:This FLEXnet Licensing client function is not available. This could be due
LMF-045:to incorrect initialization.
LMF-045:
LMF-045:Contact Cadence support at support@cadence.com for further assistance.
LMF-046:ERROR (LMF-046): Software is evaluation version.
LMF-046:
LMF-046:Contact Cadence support at support@cadence.com for further assistance.
LMF-047:ERROR (LMF-047): Clock setting check not available in vendor daemon.
LMF-047:
LMF-047:The license server cannot verify compatible system clock settings. The
LMF-047:system date on the application client does not agree closely enough with the
LMF-047:date on the license server.
LMF-048:ERROR (LMF-048): Platform not enabled.
LMF-048:
LMF-048:Contact Cadence support at support@cadence.com for further assistance.
LMF-049:ERROR (LMF-049): Date invalid for binary format.
LMF-049:
LMF-049:Contact Cadence support at support@cadence.com for further assistance.
LMF-050:ERROR (LMF-050): Key data has expired.
LMF-050:
LMF-050:Contact Cadence support at support@cadence.com for further assistance.
LMF-051:ERROR (LMF-051): Not initialized.
LMF-051:
LMF-051:Contact Cadence support at support@cadence.com for further assistance.
LMF-052:ERROR (LMF-052): Vendor daemon did not respond within timeout interval.
LMF-052:
LMF-052:Contact Cadence support at support@cadence.com for further assistance.
LMF-053:ERROR (LMF-053): Checkout request rejected by vendor-defined checkout filter.
LMF-053:
LMF-053:Contact Cadence support at support@cadence.com for further assistance.
LMF-054:ERROR (LMF-054): No FEATURESET line in license file.
LMF-054:
LMF-054:Contact Cadence support at support@cadence.com for further assistance.
LMF-055:ERROR (LMF-055): Incorrect FEATURESET line in license file.
LMF-055:
LMF-055:Contact Cadence support at support@cadence.com for further assistance.
LMF-056:ERROR (LMF-056): Cannot compute FEATURESET data from license file.
LMF-056:
LMF-056:Contact Cadence support at support@cadence.com for further assistance.
LMF-057:ERROR (LMF-057): socket() call failed.
LMF-057:
LMF-057:Contact Cadence support at support@cadence.com for further assistance.
LMF-058:ERROR (LMF-058): setsockopt() call failed.
LMF-058:
LMF-058:Contact Cadence support at support@cadence.com for further assistance.
LMF-059:ERROR (LMF-059): Message checksum failure.
LMF-059:
LMF-059:Communications error messages between the FLEXenabled application and
LMF-059:license server are encrypted and checksummed for security and integrity.
LMF-059:The checksum will usually fail because of poor networking communications.
LMF-059:
LMF-059:Contact Cadence support at support@cadence.com for further assistance.
LMF-060:ERROR (LMF-060): License server system message checksum failure.
LMF-060:
LMF-060:Contact Cadence support at support@cadence.com for further assistance.
LMF-061:ERROR (LMF-061): Cannot read license file data from license server system.
LMF-061:
LMF-061:Contact Cadence support at support@cadence.com for further assistance.
LMF-062:ERROR (LMF-062): Network software (tcp/ip) not available.
LMF-062:
LMF-062:Contact Cadence support at support@cadence.com for further assistance.
LMF-063:ERROR (LMF-063): You are not a license administrator.
LMF-063:
LMF-063:Contact Cadence support at support@cadence.com for further assistance.
LMF-064:ERROR (LMF-064): lmremove request before the minimum lmremove interval.
LMF-064:
LMF-064:Contact Cadence support at support@cadence.com for further assistance.
LMF-065:ERROR (LMF-065): Unknown VENDORCODE struct type passed to lc_new_job() or lc_init().
LMF-065:
LMF-065:Contact Cadence support at support@cadence.com for further assistance.
LMF-066:ERROR (LMF-066): Include file/library version mismatch.
LMF-066:
LMF-066:Contact Cadence support at support@cadence.com for further assistance.
LMF-067:ERROR (LMF-067): No licenses available to borrow.
LMF-067:
LMF-067:Contact Cadence support at support@cadence.com for further assistance.
LMF-068:ERROR (LMF-068): License BORROW support not enabled.
LMF-068:
LMF-068:Contact Cadence support at support@cadence.com for further assistance.
LMF-069:ERROR (LMF-069): FLOAT_OK can't run standalone on license server system.
LMF-069:
LMF-069: This error can occur because the license server isn't running, or the
LMF-069:application needs to add @localhost with the lmpath command.
LMF-070:ERROR (LMF-070): Meter already being updated, locked.
LMF-070:
LMF-070: lmutil lmborrow -startupdate was issued but not updated yet. To override
LMF-070:this, stop and restart the license server system.
LMF-070:WARNING: overriding may cause loss of licenses.
LMF-071:ERROR (LMF-071): Invalid TZ environment variable.
LMF-071:
LMF-071:Contact Cadence support at support@cadence.com for further assistance.
LMF-072:ERROR (LMF-072): Old VENDORCODE (3-word) struct type passed to lc_new_job() or lc_init().
LMF-072:
LMF-072:Contact Cadence support at support@cadence.com for further assistance.
LMF-073:ERROR (LMF-073): Local checkout filter rejected request.
LMF-073:
LMF-073:Contact Cadence support at support@cadence.com for further assistance.
LMF-074:ERROR (LMF-074): Attempt to read beyond end of license file path.
LMF-074:
LMF-074:Contact Cadence support at support@cadence.com for further assistance.
LMF-075:ERROR (LMF-075): SYS$SETIMR call failed.
LMF-075:
LMF-075:Contact Cadence support at support@cadence.com for further assistance.
LMF-076:ERROR (LMF-076): Internal Error - Please report to Macrovision Corporation.
LMF-076:
LMF-076:Contact Cadence support at support@cadence.com for further assistance.
LMF-077:ERROR (LMF-077): Bad version number - must be floating point number, with no letters.
LMF-077:
LMF-077:Contact Cadence support at support@cadence.com for further assistance.
LMF-078:ERROR (LMF-078): FLEXadmin API functions not available.
LMF-078:
LMF-078:Contact Cadence support at support@cadence.com for further assistance.
LMF-079:ERROR (LMF-079): Internal error -79.
LMF-079:
LMF-079:Contact Cadence support at support@cadence.com for further assistance.
LMF-080:ERROR (LMF-080): Internal error -80.
LMF-080:
LMF-080:Contact Cadence support at support@cadence.com for further assistance.
LMF-081:ERROR (LMF-081): Internal error -81.
LMF-081:
LMF-081:Contact Cadence support at support@cadence.com for further assistance.
LMF-082:ERROR (LMF-082): Invalid PACKAGE line in license file.
LMF-082:
LMF-082:Contact Cadence support at support@cadence.com for further assistance.
LMF-083:ERROR (LMF-083): Version of vendor daemon is too old.
LMF-083:
LMF-083:Vendor daemon version is older than the application's FLEXnet Licensing
LMF-083:version.
LMF-083:
LMF-083:Contact Cadence support at support@cadence.com for further assistance.
LMF-084:ERROR (LMF-084): USER_BASED license has no specified users -- see license server system log.
LMF-084:
LMF-084:Contact Cadence support at support@cadence.com for further assistance.
LMF-085:ERROR (LMF-085): License server system does not support this request.
LMF-085:
LMF-085:Contact Cadence support at support@cadence.com for further assistance.
LMF-086:ERROR (LMF-086): License object already in use.
LMF-086:
LMF-086:Contact Cadence support at support@cadence.com for further assistance.
LMF-087:ERROR (LMF-087): Checkout exceeds MAX specified in options file.
LMF-087:
LMF-087:Contact Cadence support at support@cadence.com for further assistance.
LMF-088:ERROR (LMF-088): System clock has been set back.
LMF-088:
LMF-088:Contact Cadence support at support@cadence.com for further assistance.
LMF-089:ERROR (LMF-089): This platform not authorized by license.
LMF-089:
LMF-089:Contact Cadence support at support@cadence.com for further assistance.
LMF-090:ERROR (LMF-090): Future license file format or misspelling in license file.
LMF-090:
LMF-090:The file was issued for a later version of FLEXnet Licensing than this
LMF-090:program understands.
LMF-090:
LMF-090:Contact Cadence support at support@cadence.com for further assistance.
LMF-091:ERROR (LMF-091): Encryption seeds are non-unique.
LMF-091:
LMF-091:Contact Cadence support at support@cadence.com for further assistance.
LMF-092:ERROR (LMF-092): Feature removed during lmreread, or wrong SERVER line hostid.
LMF-092:
LMF-092:Checkout failure due to two possible causes.
LMF-092:  1) The feature is removed during lmreread, but the FLEXenabled application
LMF-092:     is reading an old copy of the license file which still has removed feature.
LMF-092:  2) The hostid on the SERVER line is for a different host, so all features
LMF-092:     in this license file were removed.
LMF-092:
LMF-092:Contact Cadence support at support@cadence.com for further assistance.
LMF-093:ERROR (LMF-093): This feature is available in a different license pool.
LMF-093:
LMF-093:This is a warning condition. The license server system has pooled one or
LMF-093:more INCREMENT lines into a single pool, and the request was made on an
LMF-093:INCREMENT line that has been pooled. If this is reported as an error, it's an
LMF-093:internal error.
LMF-094:ERROR (LMF-094): Attempt to generate license with incompatible attributes.
LMF-094:
LMF-094:Contact Cadence support at support@cadence.com for further assistance.
LMF-095:ERROR (LMF-095): Network connect to THIS_HOST failed.
LMF-095:
LMF-095:The license file indicates THIS_HOST, and the server is not running on this
LMF-095:host. If it's running on a different host, THIS_HOST should be changed to the
LMF-095:correct host.
LMF-096:ERROR (LMF-096): License server machine is down or not responding.
LMF-096:
LMF-096:See the system adminstrator about starting the license server system, or
LMF-096:make sure you're referring to the right host (see LM_LICENSE_FILE).
LMF-096:
LMF-096:Contact Cadence support at support@cadence.com for further assistance.
LMF-097:ERROR (LMF-097): The desired vendor daemon is down.
LMF-097:
LMF-097:Check the lmgrd log file, or try lmreread.
LMF-098:ERROR (LMF-098): This FEATURE line can't be converted to decimal format.
LMF-098:
LMF-098:Contact Cadence support at support@cadence.com for further assistance.
LMF-099:ERROR (LMF-099): The decimal format license is typed incorrectly.
LMF-099:
LMF-099:Contact Cadence support at support@cadence.com for further assistance.
LMF-100:ERROR (LMF-100): Cannot remove a linger license.
LMF-100:
LMF-100:Contact Cadence support at support@cadence.com for further assistance.
LMF-101:ERROR (LMF-101): All licenses are reserved for others.
LMF-101:
LMF-101:The system administrator has reserved all the licenses for others.
LMF-101:Reservations are made in the options file. The license server system must be
LMF-101:restarted for options file changes to take effect.
LMF-102:ERROR (LMF-102): A FLEXid borrow error occurred.
LMF-102:
LMF-102:Contact Cadence support at support@cadence.com for further assistance.
LMF-103:ERROR (LMF-103): Terminal Server remote client not allowed.
LMF-103:
LMF-103:Contact Cadence support at support@cadence.com for further assistance.
LMF-104:ERROR (LMF-104): Cannot borrow that long.
LMF-104:
LMF-104:Retry the checkout again for a shorter period.
LMF-105:ERROR (LMF-105): Feature already returned to license server system.
LMF-105:
LMF-105:Contact Cadence support at support@cadence.com for further assistance.
LMF-106:ERROR (LMF-106): License server system is out of network connections.
LMF-106:
LMF-106: The vendor daemon can't handle any more users.
LMF-106:See the license server manager (lmgrd) debug log for further information.
LMF-107:ERROR (LMF-107): Cannot borrow a PACKAGE component.
LMF-107:
LMF-107:Contact Cadence support at support@cadence.com for further assistance.
LMF-110:ERROR (LMF-110): Cannot read dongle: check dongle or driver.
LMF-110:
LMF-110:Either the hardware dongle is not attached, or the necessary software driver
LMF-110:for this dongle type is not installed. In order to read the dongle hostid,
LMF-110:the correct driver must be installed. The drivers are included as part of the
LMF-110:Cadence licensing software. You can also find these drivers at
LMF-110:http://www.macrovision.com.
LMF-110:
LMF-110:Contact Cadence support at support@cadence.com for further assistance.
LMF-111:ERROR (LMF-111): lmgr.res, Windows Resource file, not linked.
LMF-111:
LMF-111:When linking Windows binaries, you must link with lmgr.lib as well as lmgr.res.
LMF-112:ERROR (LMF-112): Missing Dongle Driver.
LMF-112:
LMF-112:In order to read the dongle hostid, the correct driver must be installed.
LMF-112: These drivers are included as part of the Cadence licensing software.
LMF-112:You can also find these drivers at http://www.macrovision.com.
LMF-112:
LMF-112:Contact Cadence support at support@cadence.com for further assistance.
LMF-114:ERROR (LMF-114): SIGN= keyword required but missing from the license certificate.
LMF-114:
LMF-114:This is probably because the license is older than the application
LMF-114:
LMF-114:Contact Cadence support at support@cadence.com for further assistance.
LMF-115:ERROR (LMF-115): Error in Public Key package.
LMF-115:
LMF-115:Contact Cadence support at support@cadence.com for further assistance.
LMF-116:ERROR (LMF-116): TRL not supported for this platform."
LMF-116:
LMF-116:Contact Cadence support at support@cadence.com for further assistance.
LMF-117:ERROR (LMF-117): BORROW failed.
LMF-117:
LMF-117:Contact Cadence support at support@cadence.com for further assistance.
LMF-118:ERROR (LMF-118): BORROW period expired.
LMF-118:
LMF-118:Contact Cadence support at support@cadence.com for further assistance.
LMF-119:ERROR (LMF-119): lmdown/lmreread must be run on the license server machine.
LMF-119:
LMF-119:Contact Cadence support at support@cadence.com for further assistance.
LMF-120:ERROR (LMF-120): Cannot lmdown the server when licenses are borrowed.
LMF-120:
LMF-120:Use lmstat to find the users that have the licenses borrowed.
LMF-121:ERROR (LMF-121): FLOAT_OK requires exactly one dongle hostid.
LMF-121:
LMF-121:Use one line per dongle.
LMF-122:ERROR (LMF-122): Unable to delete local borrow info.
LMF-122:
LMF-122:Contact Cadence support at support@cadence.com for further assistance.
LMF-123:ERROR (LMF-123): Returning a borrowed license early is not supported.
LMF-123:
LMF-123:Contact Cadence support at support@cadence.com for further assistance.
LMF-124:ERROR (LMF-124): Error returning borrowed license.
LMF-124:
LMF-124:Contact Cadence support at support@cadence.com for further assistance.
LMF-125:ERROR (LMF-125): A PACKAGE component must be specified.
LMF-125:
LMF-125:Contact Cadence support at support@cadence.com for further assistance.
LMF-126:ERROR (LMF-126): Composite hostid not initialized.
LMF-126:
LMF-126:Contact Cadence support at support@cadence.com for further assistance.
LMF-127:ERROR (LMF-127): An item needed for composite hostid missing or invalid.
LMF-127:
LMF-127:Contact Cadence support at support@cadence.com for further assistance.
LMF-128:ERROR (LMF-128): Error, borrowed license doesn't match any known server license.
LMF-128:
LMF-128:Contact Cadence support at support@cadence.com for further assistance.
LMF-129:ERROR (LMF-129): Internal Error (NULL pointer).
LMF-129:
LMF-129:Contact Cadence support at support@cadence.com for further assistance.
LMF-130:ERROR (LMF-130): Internal Error (Bad handle).
LMF-130:
LMF-130:Contact Cadence support at support@cadence.com for further assistance.
LMF-131:ERROR (LMF-131): Internal Error (Empty string).
LMF-131:
LMF-131:Contact Cadence support at support@cadence.com for further assistance.
LMF-132:ERROR (LMF-132): Internal Error (Bad memory access).
LMF-132:
LMF-132:Contact Cadence support at support@cadence.com for further assistance.
LMF-133:ERROR (LMF-133): Internal Error (Operation not supported).
LMF-133:
LMF-133:Contact Cadence support at support@cadence.com for further assistance.
LMF-134:ERROR (LMF-134): Job handle is NULL.   .
LMF-134:
LMF-134:Contact Cadence support at support@cadence.com for further assistance.
LMF-135:ERROR (LMF-135): Error enabling event log.
LMF-135:
LMF-135:Contact Cadence support at support@cadence.com for further assistance.
LMF-136:ERROR (LMF-136): Event logging is disabled.
LMF-136:
LMF-136:Contact Cadence support at support@cadence.com for further assistance.
LMF-137:ERROR (LMF-137): Error writing to event log.
LMF-137:
LMF-137:Contact Cadence support at support@cadence.com for further assistance.
LMF-138:ERROR (LMF-138): Internal error (Bad index).
LMF-138:
LMF-138:Contact Cadence support at support@cadence.com for further assistance.
LMF-139:ERROR (LMF-139): Timeout.
LMF-139:
LMF-139:Contact Cadence support at support@cadence.com for further assistance.
LMF-140:ERROR (LMF-140): Bad message command.
LMF-140:
LMF-140:Contact Cadence support at support@cadence.com for further assistance.
LMF-141:ERROR (LMF-141): Error writing to socket.  Peer has closed socket.
LMF-141:
LMF-141:Contact Cadence support at support@cadence.com for further assistance.
LMF-142:ERROR (LMF-142): Error, cannot generate version specific license tied to a single hostid, which is composite.
LMF-142:
LMF-142:Contact Cadence support at support@cadence.com for further assistance.
LMF-143:ERROR (LMF-143): Version-specific signatures are not supported for uncounted licenses.
LMF-143:
LMF-143:Contact Cadence support at support@cadence.com for further assistance.
LMF-144:ERROR (LMF-144): License template contains redudant signature specifiers.
LMF-144:
LMF-144:Contact Cadence support at support@cadence.com for further assistance.
LMF-145:ERROR (LMF-145): Invalid V71_LK signature.
LMF-145:
LMF-145:Contact Cadence support at support@cadence.com for further assistance.
LMF-146:ERROR (LMF-146): Invalid V71_SIGN signature.
LMF-146:
LMF-146:Contact Cadence support at support@cadence.com for further assistance.
LMF-147:ERROR (LMF-147): Invalid V80_LK signature.
LMF-147:
LMF-147:Contact Cadence support at support@cadence.com for further assistance.
LMF-148:ERROR (LMF-148): Invalid V80_SIGN signature.
LMF-148:
LMF-148:Contact Cadence support at support@cadence.com for further assistance.
LMF-149:ERROR (LMF-149): Invalid V81_LK signature.
LMF-149:
LMF-149:Contact Cadence support at support@cadence.com for further assistance.
LMF-150:ERROR (LMF-150): Invalid V81_SIGN signature.
LMF-150:
LMF-150:Contact Cadence support at support@cadence.com for further assistance.
LMF-151:ERROR (LMF-151): Invalid V81_SIGN2 signature.
LMF-151:
LMF-151:Contact Cadence support at support@cadence.com for further assistance.
LMF-152:ERROR (LMF-152): Invalid V84_LK signature.
LMF-152:
LMF-152:Contact Cadence support at support@cadence.com for further assistance.
LMF-153:ERROR (LMF-153): Invalid V84_SIGN signature.
LMF-153:
LMF-153:Contact Cadence support at support@cadence.com for further assistance.
LMF-154:ERROR (LMF-154): Invalid V84_SIGN2 signature.
LMF-154:
LMF-154:Contact Cadence support at support@cadence.com for further assistance.
LMF-155:ERROR (LMF-155): License key required but missing from the license certificate.
LMF-155:
LMF-155:Contact Cadence support at support@cadence.com for further assistance.
LMF-156:ERROR (LMF-156): Invalid AUTH={} signature.
LMF-156:
LMF-156:Contact Cadence support at support@cadence.com for further assistance.
LMF-157:ERROR (LMF-157): Specified operation is not allowed.
LMF-157:
LMF-157:Contact Cadence support at support@cadence.com for further assistance.
