The licence database is full

Question

Users are unable to logon, the error 'licence database is full' is displayed

Symptoms

User logons fails with the following error 'the licence database is full' or 'the licence server did not respond in a timely manner'.

In addition the system event logs are full with the following critical error messages from the Ranger Licence Server 'The maximum number of licence's is reached' or the 'licence database is full'.

The logon error messages can be reported for a number of different reasons. To isolate the fault is specific to this article check the application event logs and make sure they refer to the licence database being full. The solution in this article only applied to this particular error.

Cause

The error is caused by a corruption in the Ranger Licence Server database. The corruption was caused by either the server or client workstation crashing or turning off when it was writing to the database. The corruption affects the database index which is used to count the amount of licences used.

In the event the database gets corrupted the Ranger Licence server is unable to identify how many licences are being used and therefore how many are free. This results in LAN Ranger reporting that no licences are used or available and no users on a Ranger client can logon.

Resolution

We have developed a fix for this problem and have included it in the Service Release Pack (4.4SR1). This update can be downloaded from the downloads section.

Instructions

If you are unable to download the file or need an immediate solution then the following work-around can be applied.

1. Close LAN Ranger (if running)
2. Stop the Ranger Services start programs ranger stop ranger services
3. Open the Ranger folder and find rgrshdbconnections.tab and delete it.
4. Start the Ranger Services start programs ranger start ranger services
5. Open LAN Ranger start programs Ranger LAN Ranger

Testing

First check LAN Ranger computer lists. This should show you when computers are turned on. If no computers are listed then check on the Network Explorer Your Network node for licence details. If all totals are 0 except for the licences owned the licence database is corrupt. Repeat the deletion process.

If computers are shown in LAN Ranger, try logging on as a user. If the error appears again but the values are not 0 and the error is not reported in the event logs the logon failure is being caused by something else.

Verify that you have not actually reached the maximum amount of licence LAN Ranger View Unlicensed machines and then review the licence details. If you confirm that the site has indeed reached the licence limit then try removing Ranger client from a few machines or turn them off to see if the connections reduces within LAN Ranger.

If the connection drop then try logging on again. If you get a successful logon, it would confirm that the limit was reached and you should get in touch with your Ranger dealer to buy some more Ranger licences.