@jyadav  I think the fix described here may well prevent the duplicate checked out licenses being held indefinitely like the article talks about, but it seemingly does not actually pervent the duplicate checkout in the first place which can cause significant issues in itself.  Based on the information provided and testing on our end, the fix applied in 11.18.3.0 may work if the duration of the disconnection is more than 300 seconds (300 seems to be the minimum value allowable for ' ls_server_override_client_tcp_timeout') But I think if the client reconnects within the 300 seconds then an additional license is still going to be consumed - which is problematic if there are no more licenses available, and FlexNet causes the application to close with a "Lost license, cannot re-connect: Licensed number of users already reached" error Logically, if the fix is only applied if the timeout is reached, then there will be no difference if the duration is less than the minimum timeout and the issue could still occur. Our testing also confirms that the license error can seemingly still occur for these short timeouts Is there any way to eliminate this duplicate checkout problem completely? Ideally, the server needs to be able to not consume another license even temporarily,  as otherwise it's possible to hit this error. I guess the server would need to do something like detect that the checkout requests occurred due to a re-connection, and if so kill the old connection (and freeing up the old license) before checking out a new license I appreciate that the above suggestion would need further software changes, but seems to me the current fix doesn't handle this scenario   Additionally - is there any exit handler that is called when the application exits due to a  "Lost license, cannot re-connect: Licensed number of users already reached" error?  If such a handler existed, it may at least be possible to save the application data before exiting - something that doesn't currently occur and thus data can be lost, however I can't see reference to any such handler. This could be a useful addition that would not address the root cause of this issue, but at least allow it to be less damaging Thanks PS I raised a support case for this issue and have been met with silence, hence why we're asking for support via this post. ... View more

Hi @sciencelab-22  , I believe you have already raised a case  02688300 with us and your questions have been taken care of. ... View more

Hi @mvanhorn  , You can do it as below INCLUDEALL INTERNET <on-site_ip_address_range> INCLUDE featurename USER  <off_site_username>   ... View more

Hi @RyScov  , The error states that their is a version incompatibility as stated above , this versioning order has to be followed . Can you tell me the version of FNLS , License server and client ? ... View more

Ok understood. It's a shame there's no mechanism to have a licence that simply proves the correct configuration of license file and host without actually providing any licenses for any products. Anyway, I have another idea that might serve sufficiently for my purposes. Perhaps you could say if you think it's reasonable? The host id in the license file binds the license to the host platform. In the FlexNetLicenseServerTools directory there's an "lmhostid" utility that returns the host id(s) as recognised by the FlexNet Publisher. $ ./FlexNetLicenseServerTools/lmhostid lmhostid - Copyright (c) 1989-2019 Flexera. All Rights Reserved. The FlexNet host ID of this machine is ""8cae4cde9540 58961d9494d1"" Only use ONE from the list of hostids. To validate a setup in any cloud environment would it suffice to ensure that these host id's remain consistent on the machine running the FlexNet Publisher? I think I can achieve this in AWS by creating the Network Interface as a separate entity to the host machine so that any failure of the host machine does not destroy the Network Interface, then I can create a new host and bind it to the existing Network Interface. I can let you know how it goes if you're interested? ... View more

Hi @MikeFlexQ  , Certificate based licensing comes with it's own limitations. Yes , VM MAC ID can be easily replicated so below are your options : 1. Use Trusted storage based licensing  2. In license file based you can go for composite hostid (A composite hostid combines hostids together to provide a more secure hostid.) 3. You can consider vendor defined hostid as well . ... View more

Hi @cadencelic  , The reference of "libpthread" can be seen in the makefile . You can do a quick search for it in the same file . All the libraries mentioned in the makefile have to be linked. ... View more

Please take a look at my previous question https://community.flexera.com/t5/FlexNet-Publisher-Forum/DPLT-terminating-due-to-failure-in-creation-of-AF-LOCAL-AF-UNIX/td-p/219167/ ... View more

Hi @ameganat  , The easiest way would be as what you suggested " re-compile older versions with new license keys" as this would ensure compatibility . You can also use a CVD Configuration , for example the vendor being served by Company A is "XYZ" and Company B can buy a new license key /new vendor say "ABC" altogether for serving new versions of the software . You can combine both the vendors to create a single license file that servers both the software .For further details you can have a look at "Creating a Common Vendor Daemon "in the programming reference guide .  ... View more

Hi @CraigJeffrey  , Depending on your FQDN , you might have a look at the attribute "LM_A_USE_FQDN" and see if it helps in your use case .  Apart from this below is the order ,of searching for a license . A FlexEnabled application looks for a license file as follows: 1. When the VENDOR_LICENSE_FILE environment variable has been set for the publisher of the application, then items in the license search path set in this environment variable are searched in order. 2. The items in a license search path set in the LM_LICENSE_FILE environment variable are searched in order. 3. When any license file specified in a license search path contains a USE_SERVER line, then a license is requested from the license server specified in the SERVER line. Any FEATURE and INCREMENT lines entries after the USE_SERVER line in the license file are ignored. 4. When the environment variables are not set and the FlexEnabled application does not specify the location of the license, then default location are used . You can always node lock the server to an IP Address, hostname or hostid . ... View more