Answers Database
M1 License :FLEXlm error message: Invalid returned data from license server(-12,122)
Record #2795
Product Family: Software
Product Line: M1 Graphical/General
Problem Title:
M1 License :FLEXlm error message: Invalid returned data from license
server(-12,122)
Problem Description:
Keyword : Flexlm, license, basnb, invalid, returned, data,
floating
Urgency: Hot
General Description:
When typing :
C:\>lmutil lmdiag
lmutil - Copyright (C) 1989-1994 Globetrotter Software, Inc.
FLEXlm diagnostics on Fri 9/5/97 18:23
-----------------------------------------------------
License file: X:\FlexLM\license.dat
-----------------------------------------------------
"ALI-STD-PC" v1.000, vendor: xilinxd
License server: cad1
2 floating licenses starts: 19-aug-97, no expiration date
This license cannot be checked out because: (FLEXlm error:
-12/122)
->FLEXlm error message: Invalid returned data from license
server (-12,122)
When running M1, ngdbuild gave the same error.
Solution 1:
This could mean either of these 2 cases.
1. Server name in the floating license could be set to a
dot(.). This happens when somehow the server name was unknown
at the time the license file was generated. Make sure the
server name in SERVER line is correct. If IP address is
available, use IP address instead of server name.
2. FLEX error code -12 is LM_BADCOM.
The " invalid returned data from the license server" could be
caused by one of the following situations:
1. The port number returned from lmgrd is invalid.
2. An attempted connection to a vendor daemon did not result
in a correct acknowledgement from the daemon.
3. The daemon did not send back a message within the timeout
interval.
4. A message from the daemon had an invalid checksum.
5. An lc_userlist() request did not receive the correct data.
The above information is from Globetrotter programmer's Guide,
section D under FLEXlm Status Return Values.
This error usually indicate that there is a network
problem at the user end. It could be invalid IP addresses, or
all the IP addresses have been used up, or if some
machines in the network have the same addresses. or just
excessive network delay.
End of Record #2795
For the latest news, design tips, and patch information on the Xilinx design environment, check out the Xilinx Expert Journals! |