QUESTION: What do the status/error codes returned from licensing mean? ANSWER: Following is a listing of the error/status numbers in version 7.0x, followed by the message and its meaning: -1 "cannot find license file" The license file cannot be opened. FLEXlm will attempt to open the standard file /usr/local/flexlm/licenses/license.dat,(or C:\FLEXLM\LICENSE.DAT on Windows and Windows NT) or the file specified by the vendor (via lc_set_attr()), or the file specified by the user in LM_LICENSE_FILE. -2 "invalid license file syntax" A feature specifies no hostid and # of licenses is <= 0. -3 "cannot connect to a license server" The daemon name specified in the license file FEATURE line does not match the vendor daemon name. -4 "licensed number of users already reached",The licenses number of users has been reached. -5 "no such feature exists" The feature could not be found in the license file. -6 "no TCP "license" service exists" This happens if a SERVER line does not specify a TCP port number, and the TCP license service does not exist in /etc/services. -7 "no socket connection to license manager server" lc_disconn() was called after the process had been disconnected from the socket. This error can also occur if an internal error happens within l_sndmsg() or l_rcvmsg(). -8 "encryption code in license file is inconsistent" The code in a license file line does not match the other data in the license file. This is usually the result of not building all the software components with the same encryption seeds. Check makekey.c, lsvendor.c, and your application code carefully to insure that they are all built with the same encryption seeds. (Note, this can also happen when importing Windows licenses incorrectly onto a UNIX license server) -9 "invalid host" The hostid specified in the license file does not match the node on which the software is running. -10 "feature has expired" The feature has expired, i.e., today's date is after the expiration date in the license file. -11 "invalid date format in license file" The start or expiration date in the license file is invalid. -12 "invalid returned data from license server" The port number returned from lmgrd is invalid. An attempted connection to a vendor daemon did not result in a correct acknowledgment from the daemon. The daemon did not send back a message within the timeout interval. A message from the daemon had an invalid checksum. An lc_userlist() request did not receive the correct data. -13 "no SERVER lines in license file" There is no SERVER line in the license file. All non-zero license count features need at least one SERVER line. -14 "cannot find SERVER hostname in network database" The gethostbyname() system call failed for the SERVER nodename in the license file. -15 "cannot connect to license server" The connect() system call failed, while attempting to connect to the daemon. The attempt to connect to the vendor daemon on all SERVER nodes was unsuccessful. lc_status() returns LM_CANTCONNECT if the feature had been checked out but the program is in the process of reconnecting. If reconnection fails, the final status return is LM_CANTCONNECT. -16 "cannot read data from license server" The process cannot read data from the daemon within the timeout interval. The connection was reset by the daemon (usually because the daemon exited) before the process attempted to read data. -17 "cannot write data to license server" The process could not write data to the daemon after the connection was established. -18 "license server does not support this feature" The feature has expired (on the server), or has not yet started, or the version is greater than the highest supported version. -19 "error in select system call" The select() system call failed. -20 "license server busy (no majority)", The license server is busy establishing a quorum of server nodes so that licensing can start. This error is very rare, and checkout should be retried if this occurs. -21 "license file does not support this version" The version requested is greater than the highest version supported in the license file FEATURE line. -22 "feature checkin failure detected at license server" The checkin request did not receive a good reply from the vendor daemon (the license might still be considered in use). -23 "license server temporarily busy (new server connecting)", The vendor daemon is in the process of establishing a quorum condition. New requests from clients are deferred during this period. This request should be retried. -24 "users are queued for this feature" This error is similar to MAXUSERS, but supplies the additional information that there are other users in the queue for this feature. -25 "license server does not support this version of this feature" The version specified in the checkout request is greater than the highest version number the daemon supports. -26 "request for more licenses than this feature supports" A checkout request was made for more licenses than are available. This request will never succeed. -29 "cannot find ethernet device" The ethernet device could not be located on this system. -30 "cannot read license file" The license file cannot be read (errno == EPERM or EACCES). -31 "feature not yet available" The feature is not enabled yet (current date is before the feature start date). -32 "No such attribute" A call to lc_get_attr() or lc_set_attr() specified an unknown attribute code. -33"Bad encryption handshake with daemon" The client performs an encryption handshake operation with the daemon prior to any licensing operations. This handshake operation failed. -34 "Clock difference too large between client and server" The date on the client system does not agree closely enough with the date on the server (daemon) system. The amount of difference allowed is set by the software vendor with lc_set_attr(LM_A_MAX_TIMEDIFF, ...). -35 "In the queue for this feature" This checkout request has resulted in the process being placed in the queue for this feature. Subsequent calls to lc_status() will yield the status of this queued request. -36 "Feature database corrupted in daemon" The daemon's run-time feature data structures have become corrupted. This is an internal daemon error. -37 "Duplicate selection mismatch for this feature" The checkout request for this feature has specified a duplicate mask that does not match the mask specified by an earlier checkout. This is probably the result of using different versions of your client software, or from having an uninitialized variable in the dup_group field for lc_checkout(). -38 "User/host on EXCLUDE list for feature" The user/host/display has been excluded from this feature by an end-user's daemon option file. -39 "User/host not on INCLUDE list for feature" The user/host/display has NOT been included in this feature by an end-user's daemon option file. -40 "Cannot allocate dynamic memory" The malloc() call failed to return sufficient memory. -41 "Feature was never checked out" This code is returned by lc_status() if the feature requested has never been checked out. -42 "Invalid parameter" A call to lc_set_attr() specified an invalid value for its attribute.lc_get_attr(LM_A_MASTER,...) called without connection already established to server. -43 "No FLEXlm key data supplied in lc_new_job() call" No FLEXlm key data was supplied to the lc_new_job() call. Some FLEXlm functions will be disabled. -44 "Invalid FLEXlm key data supplied" Invalid FLEXlm key data was supplied to the lc_new_job() call. Some FLEXlm functions will be disabled. -45 "FLEXlm function not available in this version" This FLEXlm function is not available. This could be a result of a BADKEYDATA, NOKEYDATA, or DEMOKIT return from lc_new_job(). -47 "Clock setting check not available in daemon" lc_checkout() returns this code when the CLOCK SETTING check between client and daemon is not supported in this daemon. To disable the clock check: lc_set_attr(LM_A_MAX_TIMEDIFF, -1) -48 "FLEXlm platform not enabled" The software is running on a platform which is not supported by the vendor keys you have purchased. -49 "Date too late for binary format" The start date format in FLEXlm licenses are good until the year 2027. This is probably a bad date. -50 "FLEXlm key data has expired" The FLEXlm Demo vendor keys have expired. -51 "FLEXlm not initialized" A FLEXlm function was called before lc_new_job() was called. Always call lc_new_job() first. -52 "Server did not respond to message" UDP communications failure. UDP communications are not guaranteed. FLEXlm makes a best effort to recover from lost and garbled messages, but this indicates a failure. -53 "Request rejected by vendor-defined filter" lc_checkout() failed because of the vendor defined routine which is set in lsvendor.c: ls_outfilter. -54 "No FEATURESET line present in license file" lc_ck_feats() called, but no FEATURESET line in license file. -55 "Incorrect FEATURESET line in license file" Error return from lc_ck_feats() -56 "Cannot compute FEATURESET line" Error return from lc_ck_feats(), which occurs because lc_feat_set() can not compute the FEATURESET line. This can happen because there are no FEATUREs in the file. -57 "socket() call failed" This can occur when the Unix OS runs out of system resources. -58 "setsockopt() failed" The setsockopt() call has failed. This is likely due to an OS error. -59 "message checksum failure" Communications error -- messages between client and server are encrypted and checksummed for security and integrity. The checksum will usually fail because of poor networking communications. -61 "Cannot read license file from server" This occurs when the license file, via LM_LICENSE_FILE,or lc_set_attr(LM_A_LICENSE_FILE, path), is incorrectly defined. This only occurs in lmutil when LM_LICENSE_FILE is set to port@host or @host. -62 "Network software (tcp/ip) not available" This is reported on systems where this is detectable. Some systems may have this problem, but the error will not be reported as LM_NONETWORK - system calls will simply fail. -63 "Not a license administrator" Various functions, such as lc_remove() and lc_shutdown(), require that the user be an license administrator, depending on how lmgrd was started. -64 "lmremove request too soon" An lc_remove request occurred, but ls_min_lmremove (defined in lsvendor.c) seconds have not elapsed since the license was checked out. -65 "Bad VENDORCODE struct passed to lc_new_job()" LM_CODE macro was not used to define the VENDORCODE argument for lc_new_job. See lm_code.h and lmflex.c for an example of how to use the LM_CODE macro. -66 "FLEXlm include file/library mismatch" An attempt was made to create a licensed binary with mismatching source/header files and liblmgr.a. The source code version must match the linking libraries. -71 "Invalid TZ environment variable" On some operating systems, the end-user can significantly change the date using the TZ environment variable. This error detects this type of change. -72 "'Old-style' vendor keys (3-word)" lm_init() detected that an old LM_CODE macro was used. -73 "Local checkout filter requested request" Request was denied by filter specified in lc_set_attr(LM_A_CHECKOUTFILTER, filter). -74 "Attempt to read beyond the end of LF path" An error occurred with the list of license files. -75 "SYS$SETIMR call failed" SYS$SETIMR is used on VMS to time out certain FLEXlm system calls. -76 "Internal FLEXlm Error - Please report to Globetrotter Software" -77 "Bad version number - must be floating point number, with no letters" A line in the license file has an invalid version number.lc_checkout() was called with an invalid version character string. -78 "FLEXadmin API functions not available" An attempt to get information from another company's vendor daemon was made via lc_get_attr(LM_A_VD_*, ...). This function call is only allowed for the ISV's own vendor daemon. -82 "Invalid PACKAGE line in license file" PACKAGE missing or invalid COMPONENTS. A COMPONENT has number of licenses set, with OPTIONS=SUITE. A COMPONENT has number of licenses==0 -83 "Server FLEXlm version older than client's" Vendor daemon FLEXlm version is older than the client's FLEXlm version. This is only supported with a v5.0+ client. -84 "Incorrect number of USERS/HOSTS INCLUDED in options file -- see server log" When a feature has the USER_BASED attribute, this error occurs when there no INCLUDE line in the end-user options file for this feature, or the number of users included exceeds the number authorized. -85 "Server doesn't support this request" This occurs when a vendor daemon with a FLEXlm version older than the client is being used. The daemon didn't understand and respond to the request made by the application. -86 "This license object already in use" Java only. A second checkout against a license object generates this error. If multiple checkouts are needed, multiple license objects need to be created. -87 "Checkout exceeds MAX specified in options file" End-user option MAX has been specified for this feature. -88 "System clock has been set back" Returned from checkout call. -89 "This platform not authorized by license" Returned from checkout call where FEATURE line specifies PLATFORMS='...'. -90 "Future license file format or misspelling in license file" Returned from checkout call when license file attribute was introduced in a later FLEXlm version than the client. -91 "ENCRYPTION_SEEDs are non-unique" Returned from lc_new_job or lp_checkout() when vendor name is not `demo', but seeds are default seeds. -92 "Feature removed during lmreread,or wrong SERVER line hostid" Checkout failure due to 2 possible causes. 1) the feature is removed during lmreread, but the client is reading an old copy of the license file which still has removed feature. 2) The hostid on the SERVER line is for a different host, so all features in this license file were removed. -93 "This feature is available in a different license pool" This is a possible response to LM_A_VD_FEATURE_INFO request,indicating that this INCREMENT line can be ignored, as it has been pooled with another line. -94 "Attempt to generate license with incompatible attributes" Occurs with -verfmt arguments to lmcrypt or makekey, or for lminstall, -overfmt. Also set by lc_cryptstr() and lc_chk_conf(). -95 "Network connect to THIS_HOST failed" Returned by checkout. When `this_host' is used as a hostname. Replace this_host with a real hostname to resolve this error. -96 "Server node is down or not responding" Returned by checkout; indicates the whole license-server system is not up, not just the lmgrd process. -97 "The desired vendor daemon is down" Returned by checkout; indicates lmgrd is running, but not the vendor daemon. -98 "The FEATURE line can't be converted to decimal format" Returned by lc_cryptstr(), or lmcrypt/makekey/lminstall. See the section on Decimal Format for information on what can't be converted to decimal format. -99 "The decimal format license is typed incorrectly" The internal checksum on the decimal line has indicated the line has been typed in incorrectly. -100 "Cannot remove a lingering license" Returned to lmremove command. User has already exited, but license is lingering. lmremove doesn't remove the linger time. -101 "All licenses are reserved for others" Checkout return value when a checkout will never succeed, since the end-user options file has all licenses reserved for others. -106 "License server out of network connections" The vendor daemon can't handle any more users. See the lmgrd debug log for further information. -111 "lmgr.res, Windows Resource file, not linked" When linking Windows binaries, you must link with lmgr.lib as well as lmgr.res -113 "2 FLEXlock checkouts attempted" Only 1 checkout is allowed with FLEXlock enabled apps.Subsequent checkout attempts will fail. They should be disabled if first checkout succeeded in FLEXlock mode. Rational Customer Service Policies and Information: http://www.rational.com/support/info.jsp