[edit] Server Log

The first stop for all problems is the hlserver log file, found in the hlserver install directory on the server. By default there will be two log files, rotated weekly; check their last modified dates to see which one is currently active.

If your users have problems accessing the floating licenses, you should first check the log file to see if any errors have been reported. The following is an explanation of the log messages.

Config - Couldnt find config file 

The config file wasn't found. (Linix) Check the server startup script for the correct setting of the HEADUS_HOME variable. (Windows) Check hlserver.ini for correct setting of "-c" argument. (OS X) Have you run the setup script?

Config - Problems reading config file 

The config file was found, but it couldn't be opened for reading. Check file permissions.

Config - starting hlserver 

So far so good.

Connect - INVALID: host [xxx.xxx.xxx.xxx] 

Someone from host (with IP xxx.xxx.xxx.xxx) connected to the server's port, but it wasn't talking the right protocol. This could mean one of a couple of things; there's some sort of port overlap with other installed software; you can change the PORT used by hlserver by editing the config file and restarting. Or someone's doing a port scan attack to find a way into the system; you might need to install a firewall, or if you already have one, configure it to block connects to port 11668 from outside the LAN.

Connect - INVALID: host [xxx.xxx.xxx.xxx] using newer protocol 

This will appear if someone on host is trying to run an application that's compiled with a newer incompatible version of the license request protocol. This means you need to install a newer version of hlserver.

Connect - manager login user@host 

user@host is running hlmanager.

Denied - manager access to user@host hlmanager 

user@host tried to run hlmanager without access being given in the config file.

Denied - access to user@host appname 

user@host, running appname, tried to grab a floating license without access being given in the config file.

DeniedIP ip [range] - access to user@host appname 

user@host, running appname, tried to grab a floating license, but their ip was out of the allowed range. Check the IP ranges defined in the config file.

DeniedCG [name] - access to user@host appname 

user@host was denied access because of a client side group definition.

Reload - by user@host 

Manager user@host told hlserver to reload its key and config files. This would need to be done whenever the files have been edited while the server is running.

Grabbed - product user@host appname 

user@host, running appname, grabbed one of the product floating licenses.

Attach - product user@host appname 

user@host, running appname, attached to an existing product floating licenses.

Freed - product from host 

All applications on host using the product floating license have exited, and so its freed for others to use.

Booted - product on host by user@host 

Manager user@host told hlserver to withdraw the product floating license from host.

Lost - product for host 

This would occur after a server reload if a change in the key or config files have withdraw access to product for host.

Shutdown - by user@host 

Manager user@host told hlserver to shut itself down.

Shutdown - at server 

hlserver shut itself down. Under Windows that would usually be because the service was stopped. Under IRIX/Linux it could happen if the hlserver process couldn't write to /usr/tmp/hlserver.pid, or if two hlserver processes tried to run at the same time, or if the PID file is deleted manually or via a cron job.

[edit] Checking the Server

If the log file recorded no errors, you can run these tests to check that the server is running OK.

1. Look for hlserver in the list of running processes (Linux, OS X) or services (Windows). If its not there, have another read of the setup instructions (Linux, Windows or OS X) to make sure you've done all that's required.
   
   
2. Run hlmanager, and check that the licenses have been loaded. If hlmanager can't connect to hlserver, check the log file for possible problems. If hlmanager runs OK, but no licenses are listed, check the keys file for possible problems. Each key should be on a single separate line, with no leading spaces or tabs.

[edit] Checking Clients

You can run these tests to check that the client (i.e. user) is configured properly.

1. Run the headus licensing GUI and check that there's a "Floating Keys" entry above the "Hardware Keys" label. If not, then the HLServer setting hasn't been defined properly; check Application Config for details.
   
   
2. Are any valid (i.e. green colored) licenses shown in the "about headus 3D tools" window? If yes, then the client is talking to the server OK. Click on the Test button next to the application you are having problems with; if it works, but your other methods for starting the application fail, check your methods. If the test doesn't work, check the hlserver log file for errors.
   
   
3. If no valid licenses are shown in the "about headus 3D tools" window, then you need to check the TCP/IP connection between the client and hlserver. You can do this by running telnet from the client side; use the command line so you can define the port to connect to. That is, run "telnet server 11668", where server is the name of the host running hlserver.
   
   If all is OK then nothing will happen; hit enter and telnet will exit. The log file should show a "Connect - INVALID" error, which is what's its supposed to do.
   
   If, on the other hand, telnet gives an error, that'll indicate there's some problem with the TCP/IP connection between the client and hlserver. It might be that the server itself is blocking connects to that PORT; if you are running a firewall, check its settings. It might be that the client is confused about who server really is; run "ping server" from the client side and check the IP address.
   
   
4. If you have a "Build Status Report" button in the headus licensing GUI, click that for more debugging information.

If none of the above tests sheds any more light on the problem, contact your vendor for further directions, and attach the status report if you have one from step 4 above.