The Connection to the Licensing Server Timed Out
The error messages listed higher up point that PLECS cannot communicate with the license manager and/or the vendor daemon running on the server estimator. Possible reasons include:
- The server machine is not running at all.
- The license director is not running.
- A firewall blocks the communication between the customer and the license manager.
The following steps enable you lot to pinpoint whatsoever of these problems.
Affirm that the license server is really running
Examine the debug log file of the license server. If you practice not know what the debug log file is or where to find it, please review our installation instructions (for Windows and Linux).
If the license server has started successfully, y'all volition encounter lines similar to these (summary log lines (SLOG) omitted):
12:32:10 (lmgrd) FlexNet Licensing (v11.13.one.3 build 176543 x64_n6) started on AMPERE (IBM PC) 12:32:ten (lmgrd) Copyright (c) 1988-2015 Flexera Software LLC. All Rights Reserved. 12:32:10 (lmgrd) Www: http://world wide web.flexerasoftware.com 12:32:ten (lmgrd) License file(s): C:\PLECS_License_Manager\plexim.lic 12:32:x (lmgrd) lmgrd tcp-port 27000 12:32:10 (lmgrd) Starting vendor daemons ... 12:32:ten (lmgrd) Starting vendor daemon at port 51112 12:32:10 (lmgrd) Using vendor daemon port 1702 specified in license file 12:32:10 (lmgrd) Started plexim (pid 2644) 12:32:10 (plexim) FlexNet Licensing version v11.xiii.1.3 build 176543 x64_n6 12:32:12 (plexim) Server started on AMPERE for: plecsedit 12:32:12 (plexim) EXTERNAL FILTERS are OFF 12:32:12 (lmgrd) plexim using TCP-port 51112
Verify that license manager and vendor daemon have been updated to the latest version published on our download page. (The license director may as well have a newer version e.g. if it is shared with another awarding.)
Accept note of the port numbers highlighted in bold as you lot will need them further below.
If the debug log file reports a problem like to the lines below, you need to address this trouble first.
12:32:12 (lmgrd) plexim exited with status 34 (Invalid host) 12:32:12 (lmgrd) Please right problem and restart daemons
Assert that the client license file points to the correct license server
The client file network.lic has the following syntax:
SERVER <licenseserver> Any <port> USE_SERVER
The placeholder <licenseserver> may exist an IP accost or a hostname — either a uncomplicated name or the fully qualified domain proper noun (FQDN). If an IP address is used, verify that information technology is that of the license server. If a hostname is used, verify that the customer computer can resolve the name to the IP accost of the license server. This is done with the NSLOOKUP command in the Command Prompt on Windows, the Terminal app on macOS or a last on Linux:
> nslookup <licenseserver> Server: <something> Address: <something> Name: <licenseserver> Address: <IP address>
If you get the response Non-existent domain or NXDOMAIN, contact your network administrator for aid or supplant the hostname in the customer license file with the IP address.
The placeholder <port> is optional. If it is omitted, the TCP port of lmgrd (as shown in the debug log file above) must exist in the range 27000-27009. If <port> is given, it must match the TCP port of lmgrd.
Assert that the client computer can connect to the TCP ports used past the license server
Use the TELNET command on the customer to check whether the client can connect to the TCP ports used by the license director and the vendor daemon. On Windows, you may commencement demand to enable the Telnet client (see Windows 7: Enabling Telnet Client or Windows 10: Enabling Telnet Client). Enter the following commands (replacing the numbers 27000 and 51112 with the actual TCP port numbers of lmgrd and plexim):
> telnet <IP address> 27000 > telnet <IP address> 51112
On Windows, a successful connection is indicated by the Command Prompt window going blank. Pressing Enter or Ctrl-C will cease the connexion.
On macOS and Linux, a successful connection will produce the following output:
Trying <IP address>... Continued to <IP accost>. Escape character is '^]'.
Pressing Ctrl-C or Ctrl-] followed by the command quit will terminate the connectedness.
If instead you go an fault Connection refused or Connect failed for either command, there is a trouble in your computer network, most likely due to a firewall that blocks the connection. Please contact your network administrator for assistance.
Additional considerations
If all of the diagnostic steps above succeed and PLECS still reports connectedness errors, ane of the post-obit two cases might utilise.
- Conflict with other license managers running on the aforementioned server
If you are running multiple license managers with different software revisions on one server, it may happen that 2 license managers utilise the same TPC port number — one for IPv4 and the other for IPv6. In this situation, the PLECS client might always connect to the wrong license managing director.
To resolve the problem, use dedicated port numbers for the license manager lmgrd and the vendor daemon. For details please review the installation instructions (for Windows and Linux). - TPC timeout due to boring network communication
By default, TCP connections between the client and the license server time out afterwards 0.1 seconds. This may be as well short if you lot have a slow network or if client and server are far autonomously. On Windows clients you tin can ascertain an environment variable FLEXLM_TIMEOUT specifying the TPC timeout in microseconds.
To increase the timeout to i second, set FLEXLM_TIMEOUT to 1000000.
However need help?
If y'all still demand help, send an email to
Delight include the following information:
- The server license file plexim.lic equally installed on the license server
- The license server debug log file
- The customer license file network.lic as installed on the client
- The exact mistake bulletin on the client
- A protocol of the diagnostic steps described above
Source: https://www.plexim.com/support/solutions/1303
Post a Comment for "The Connection to the Licensing Server Timed Out"