FlexNet Publisher

This exception occurred when I tried to checkout the license.

1. Which key's expiration caused this? The vendor key or something else?
2. Is the expiration date within `flexlm.jar`?
3. If so, does this mean that the `flexlm.jar` file already purchased will become unusable once the FlexLM expiration date has passed?
4. If not, what checks the FlexLM expiration date?

Windows server 2016 license servers.

From server01 (TIMESTAMP 5/18/2026):

 3:20:07 (lmgrd) Attempting connection to primary redundant server server02

 3:20:29 (lmgrd) Disconnected from primary redundant server server02

 3:20:53 (lmgrd) Attempting connection to primary redundant server server02

 3:20:53 (lmgrd) Disconnected from primary redundant server server02

 3:21:15 (lmgrd) Attempting connection to primary redundant server server02

 3:21:19 (lmgrd) Established connection to primary redundant server server02

 3:21:19 (lmgrd) Disconnected from secondary redundant server server03

 3:21:19 (lmgrd) Redundant server quorum established. Master is server02

 3:21:19 (lmgrd) Starting vendor daemons ...

 3:21:19 (lmgrd) Starting vendor daemon at port 10306

 3:21:19 (lmgrd) Using vendor daemon port 10306 specified in license file

 3:21:19 (lmgrd) Started MLM (pid 4532)

server03: (TIMESTAMP 5/18/2026)

 3:21:19 (lmgrd) Disconnected from tertiary redundant server server01

 3:21:40 (lmgrd) Attempting connection to tertiary redundant server server01

 3:21:41 (lmgrd) Established connection to tertiary redundant server server01

server02: (TIMESTAMP 5/18/2026)

3:20:08 (lmgrd) Warning: Maximum connections to the server has reached. Please disconnect some clients from the server

...

3:21:11 (lmgrd) Redundant server heartbeat to server01 timed out

3:21:11 ((lmgrd)) Loop info: MT:3 VD_HB:58 reset:3 clients:1 fd:1 main:0

3:21:11 (lmgrd) Disconnected from tertiary redundant server server01

3:21:19 (lmgrd) Established connection from tertiary redundant server server01

There are many references to https://docs.revenera.com/fnp/2025r1/LicAdmin_Guide/Content/helplibrary/Maximum_Client_Connections_to_License_Server.htm to increase LM_SERVER_HIGHEST_FD but it does not seem relevant here clients:1 fd:1 suggests one client and 1 file descriptor? When server02 is looping there was a maximum of 300 ESTABLISHED TCP connections.

What is interesting is that "Maximum connections" message appears before heartbeat and loop info message on server02? So is "Maximum connections" a catch all error? If heartbeat connection is lost to redundant license servers and a license query is received from a client server02 has to queue as it cannot process when heartbeat is lost?, so in this case could a single query cause "Maximum connections" message to be logged as lmgrd knows due to missing heartbeats its not able to process requests?

Is "Maximum connections" message a catch all error? LM_SERVER_HIGHEST_FD link only seems relevant to genuinely busy license servers and doesn't seem to apply to us.

Up until failure occurred the vendor daemon was running on server02 (it was the master?), we don't understand server01 logs in same second server02 is identified as master it tried to also start the vendor daemon?

From the time the first "maximum connections" message is logged, to the "heartbeat timeout" being logged there is nominally a 60+ second time difference. So the question is setting HEARTBEAT_INTERVAL more relevant where network or server latency spikes might occur? (https://docs.revenera.com/fnp/2022r3/LicAdmin_Guide/Content/helplibrary/SERVER_Lines.htm).

Anyone have any ideas please, this is a long outstanding issue for us.

Best Regards - Colin

Installsheild cannot contact the FlexNet license server at this time. This may be due to server or network issues. you can try to reestablish the connection or exit Installsheild