Technical Knowledgebase

Skip to end of metadata
Go to start of metadata

This error can occur for both standalone licenses and network licenses and is typically caused by the fact that the program could not verify the license file, because the license file is missing or is invalid.

On this page:

Troubleshooting

Conventional standalone licenses

Licenses locked to Disk ID

  • Make sure that the lservrc license file provided to you by CSI has been saved in the program installation directory.
  • Verify that the license file locking code matches the Disk ID locking code. The license file locking code can be obtained by running lsdecode.exe utility. The Disk ID locking code can be obtained by running the echoid.exe or wechoid.exe utilities.

Licenses locked to USB key

  • Make sure that the lservrc license file provided to you by CSI has been saved in the program installation directory.
  • Verify that the license file locking code matches the Computer ID (USB key) locking code. The license file locking code can be obtained by running lsdecode.exe utility. The Computer ID locking code can be obtained by running the echoid.exe or wechoid.exe utilities.
  • If you are unable to obtain the Computer ID (USB key} locking code, it may indicate the USB key driver has not been installed properly. Try reinstalling the USB key driver to resolve the issue.

Conventional network licenses

  • Make sure that the license manager is running on the license server. This can be done either via WlmAdmin.exe utility or by checking the services running on the license server and ensuring that the Sentinel RMS License Manager service is running.
  • Check that the required licenses have been installed on the license manager. This can be done via WlmAdmin.exe.
  • Follow the procedures on the Network license lookup page to point the client machine that is running the software to the license server. This helps in situations when the client machine is unable to automatically locate the license server on the network.
  • No labels