Please find below information to help you troubleshoot a GWB floating license installation.
1. Common error messages
1.1 On a client in the GWB Activation Utility
- License server machine is down or not responding
The client cannot connect to the server machine at all.
An incorrect hostname may have been specified, or a firewall may be blocking access.
- Cannot connect to license server system
The client can find the server machine, but it cannot connect to the specified port.
An incorrect hostname or port was specified, or there may be firewall issues.
- Cannot read data from the license server system
The client connected to the server on the specified port, but a non-FLEXlm service is running there,
the FLEXlm service needs to be restarted, or possibly it is a drastically different LMGRD version running.
Double check the hostname and port are correct and that you are using the provided version of lmgrd.exe.
- License server system does not support this feature
The client connected to a FLEXlm service, but could not find any GWB packages.
Verify the license is activated on the server, check the LMGRD log file to see if any errors show,
and make sure LMGRD is set to use the correct license file.
- The desired vendor daemon is down
The client connected to a FLEXlm service, but the HYDROKEY daemon is not available.
Check the LMGRD log file for errors and verify that LMGRD is set to use the correct license file.
1.2 On the server in the debug log
- (time) (hydrokey) Unable to initialize access to trusted storage: 15
This error can appear if the service does not have proper rights to access the FlexNet Licensing service.
Make sure that "FlexNet Licensing Service Required" was checked when configuring the service.
If it is already checked, toggle it by unchecking the box, saving the service, rechecking the box,
and then saving the service again.
- (time) (hydrokey) Unable to initialize access to trusted storage: (not 15)
This error can occur if the hydrokey.exe file was moved from the default installation location without the other files that it depends on.
If the vendor daemon needs to be moved to a different location, all files in the GwbLicenseServer folder should be moved along with it.
2. Running LMGRD and HYDROKEY directly
You may find it useful at times to run LMGRD directly, rather than from the LMTOOLS program.
Follow these steps to do so:
- Open a command prompt:
press +r, enter cmd, and click OK or hit the return key
- Change to the GwbLicenseServer installation folder:
cd "\Program Files\GwbLicenseServer"
- Start LMGRD:
lmgrd.exe -c gwb.lic -z
- To stop LMGRD and HYDROKEY, hit ctrl+c or close the command prompt
3. Service won't stop
If for some reason the licensing service will not shut down correctly from LMTOOLS, you can stop it manually.
To do this,
- open the Windows task manager "taskmgr.exe",
- find "lmgrd.exe" and "hydrokey.exe" in the list of running processes, and
- select End task.
4. Slow license checkout
Licenses should check out from a server quickly, with the network speed being the limiting factor.
If checkout seems to be taking a long time, please check the following:
- The server hostname needs to be set correctly.
Compare the result of the “hostname” command on the server to the name the clients are using.
If they are not the same, adjust the server's license file accordingly, as set under
- Remove any license servers from the client that have errors, are not needed, or are not current.
5. Connecting to HYDROKEY directly
While the FLEXlm documentation doesn't mention this setup, it is possible to have clients connect directly
with the HYDROKEY vendor daemon.
This process is most useful if you are unable to get the hostname specified in the server license file to match the hostname the clients use.
To do this you need to set an explicit port for HYDROKEY (see Server ports)
and then specify that port when setting up the client.
6. Antivirus programs
Antivirus programs have been known to interfere with license checkout, on both the server and client sides.
The conflicts have for the most part been resolved, but if you encounter issues not otherwise addressed in this guide,
check whether temporarily disabling the antivirus program resolves the problem.