Troubleshooting License Problems
If the license manager is not functioning properly, you may see one of the following:
Most of the problems listed below refer to a license server configuration.
Solution: Copy the LICENSE.DAT file to the installation directory (the directory defined during the installation of USoft).
Solution: Start the license manager from the correct directory.
Solution: Re-start the license manager.
Solution: The systems manager has to grant access to this client/user, or a different server has to be chosen as the license server.
Solution: Copy the LICENSE.DAT file from the server to the installation directory of the client.
Solution: Contact the USoft Orders Desk to get a new LICENSE.DAT file for the current USoft version.
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.
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'.
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.
Solution: Reinstall the License Server.
Solution: Before attempting to edit the registry, make sure that you make a backup copy. Check the following registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager\USOFT_LICENSE_FILE
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.