Troubleshooting License Problems

Previous Next

See Also

If the license manager is not functioning properly, you may see one of the following:

· The USoft Binder can be opened normally but the response time will be slower.


· When an existing project (*.usb file) is opened in the USoft Binder, all of the icons are shown as broken icons.


· On startup of the USoft Binder a message may be displayed, stating that the license file could not be found.


Most of the problems listed below refer to a license server configuration.

· A 'space' in the directory name of the license file is not permitted. An underscore should be used instead.


· Problem: There is no license file resident on the client. This is shown as a message under the logo on startup of the binder containing your company name.

Solution: Copy the LICENSE.DAT file to the installation directory (the directory defined during the installation of USoft).

· Problem: The license manager was started in the wrong directory on the server. The license server will function normally, but clients will not be able to use USoft. This can be checked with the lmutil tool as described below. The directory on the server where the license file is actually running from is shown.

Solution: Start the license manager from the correct directory.

· Problem: The license manager has been shut down on the server.

Solution: Re-start the license manager.

· Problem: The client PC that has a license problem does not have 'access' to the server. This is a network problem that can be checked in the 'network neighborhood' of the client Windows Explorer. Look for the server and if you cannot locate it, you do not have access.

Solution: The systems manager has to grant access to this client/user, or a different server has to be chosen as the license server.

· Problem: The server and client use different versions of the LICENSE.DAT file.

Solution: Copy the LICENSE.DAT file from the server to the installation directory of the client.

· Problem: A license file from the wrong USoft version is being used. When moving to newer releases the so-called feature names are changed. As a result you will need a new license file.

Solution: Contact the USoft Orders Desk to get a new LICENSE.DAT file for the current USoft version.

· Problem: After renewing the license file on the License Server, installed as a NT Service, the License server does not seem to work.

Solution: Reboot your machine.

To check if your license manager is running and that the server can be reached, type the command line:

lmutil lmstat -a -c <path to license.dat on the client>\license.dat |more.

To run this command you need the files: lmutil.exe, lmgrd325a.dll and a correct LICENSE.DAT file. In principle, this command can be run from any client in the network but if you are experiencing problems with just one client, it can best be run from that particular machine.

· Problem: When running the ORAPI under Internet Information Server (IIS), with ODBC, an incorrect IIS security setting can lead to failure of the license check. The message that is shown reads: 'terminal remote client not allowed'.

Solution: In IIS go to the properties of your defined virtual directory. Select the tab, Directory Security and click Edit. In the Authentication Methods dialog, uncheck 'Anonymous access' and check, 'Integrated Windows authentication'.

· Problem: Can I use USoft 8 with my old FLEXlm version?

Solution: No.

· Problem: Can I use USoft 8 with the new FLEXlm version?

Solution: Yes.

· Problem: Can I use one license server for both USoft 7 and USoft 8?

Solution: Yes, but you need to use the license server shipped with USoft 8, as both USoft 7 and USoft 8 work with this license server.

· Problem: Having upgraded to USoft version 8, none of my USoft applications will run?

Solution: Reinstall the License Server.

· Problem: The registry entry is corrupt.

Solution: Before attempting to edit the registry, make sure that you make a backup copy. Check the following registry entry:


and make sure that the associated key points to a valid location for the correct LICENSE.DAT file. You can either edit the registry key or move the LICENSE.DAT file to solve the problem. You could also delete the registry entry and restart USoft so that a new, correct entry is made.