Solution: The following articles address the most common FlexNet error conditions: • • • • • • • • The following table lists the most common FlexNet error codes that may be displayed by the Autodesk Network License Manager. Error codes typically display as Error[1.5. ###] where ### corresponds to the error codes listed in the table. Error Code Description 21 lc_flexinit failed because there were insufficient rights to start the FlexNet Publisher Service. Resolve this by setting the service to start automatically. 20 FlexNet Publisher Service is not installed.
FLEXnet Licensing Error Codes. -82 Invalid PACKAGE line in license file. The server has pooled one or more INCREMENT lines into a single pool. Troubleshoot Common Problems. Returns or tabs in your license file. To avoid this, ensure that each line begins. With at least one of the.
13 Computed path to required file is too long for Mac OS X operating system. 12 Invalid bundle ID on Mac OS X operating system. 11 Framework specified by bundle ID was not loaded. 10 Error creating path from URL. 9 Error creating URL. 8 Path string not specified in UTF-8 format. 7 A call to lc_flexinit is not allowed after a call to lc_flexinit_cleanup.
6 Activation application has not been processed using the preptool 5 Unable to allocate resources. 4 Initialization failed. 3 Unsupported version of the operating system. 2 Unable to load activation library.
1 Unable to find activation library. -1 Cannot find license file. -2 Invalid license file syntax. -3 No license server system for this feature. 48 Volt Dc 12 Volt Dc Converter Circuit Diagram here.
-4 Licensed number of users already reached. -5 No such feature exists. -6 No TCP/IP port number in license file and FLEXnet Licensing Service does not exist. (pre-v6 only) -7 No socket connection to license server manager service. -8 Invalid (inconsistent) license key or signature.
The license key/signature and data for the feature do not match. This usually happens when a license file has been altered.
-9 Invalid host. The hostid of this system does not match the hostid specified in the license file. -10 Feature has expired. -11 Invalid date format in license file. -12 Invalid returned data from license server system. -13 No SERVER lines in license file.
-14 Cannot find SERVER host name in network database. The lookup for the host name on the SERVER line in the license file failed. This often happens when NIS or DNS or the hosts file is incorrect. Work around: Use IP address (for example, 123.456.789.123) instead of host name. -15 Cannot connect to license server system. The server (lmadmin or lmgrd) has not been started yet, or the wrong port@host or license file is being used, or the TCP/IP port or host name in the license file has been changed.
Windows XP SP2 platforms have a limit on the number of TCP/IP connection attempts per second that can be made, which your application may have exceeded. Refer to the manufacturer's documentation on how to change this limit. -16 Cannot read data from license server system. -17 Cannot write data to license server system.
-18 License server system does not support this feature. -19 Error in select system call. -20 License server system busy (no majority). -21 License file does not support this version. -22 Feature checkin failure detected at license server system. -23 License server system temporarily busy (new server connecting).
-24 Users are queued for this feature. -25 License server system does not support this version of this feature. -26 Request for more licenses than this feature supports. -29 Cannot find ethernet device.