Server Manager (lmgrd) communication issue

[IPE_KK]

Our customer uses an Windows Server 2022 Standard, version 21H2.

The License server manager (lmgrd) stops communicating nearly every day and needs to be restarted.

When the client can't connect anymore, we check the server status and its always:

[Detecting lmgrd processes...]

License server status: 27000@SERVER

    License file(s) on SERVER: C:\Users\SVC-FlexNet01\Desktop\Flexnet-Server\Customer_Test_FixedPort_2022.lic:

   SERVER: license server UP (MASTER) v11.10

Vendor daemon status (on SERVER):

       IPE: Cannot read data from license server system.

The license server system appears to be running, but is not

responding.  If this persists, notify the System Administrator.

(The license server manager (lmgrd) and vendor daemon processes

should be terminated and restarted.)

Hostname:      SERVER

License path:  27000@SERVER;

FlexNet Licensing error:-16,287

Using the "Shut down” command in “LMTOOLS” he gets this error:

------------------------

Finding License Server

------------------------

License Server Detected:

IPE : 27000@SERVER

------------------------

Finding License Server

------------------------

License Server Detected:

IPE : 27000@SERVER

----------------------------

Shutting Down License Server

----------------------------

Shutdown Failed:

Cannot read data from license server system. (-16,216)

What can cause this behaviour? 🤔

[jyadav]

Hi @IPE_KK  ,

The error -16, 287 can occur when the Vendor Daemon is unable to talk to the lmgrd and represents that functionality is timed out while waiting for the descriptor to be ready for read.

This can also be caused by using ports in the license file that are already in use.

Make sure both lmgrd and vendor daemon have ports specified in the license file 


For example:

SERVER this_host ANY 27005
VENDOR flexera PORT=27010
USE_SERVER
FEATURE...

Where 27005 in the license server port and 27010 is the vendor daemon port. 

Change the port numbers in the license file and restart the license server.

[IPE_KK]

Hi @jyadav ,

thanks for the quick reply. We haven't specified the server port yet, but we configured the vendor deamon port already.

Addionally we have checked the network traffic on this port with Wireshark and we cannot see any blocking by another application.

Do you have any advice for further investigation? Meanwhile we will set a dedicated server port.

[jyadav]

Hi @IPE_KK  ,

Another thing to point out is that you are using FNP Version 11.10 which is end of life already and also it is not supported in Windows Server 2022 which you are currently using , this could be the reason for this behavior as well . Please move to a supported FNP and OS version .