Common licensing errors are listed in the tables below.
License not found though LM servers are running. Additional details and resolution for error # 10.
User-defined license not found - level defined in level.txt or program.ini file not found. Additional details and resolution for error # 11.
LM servers are not running. Additional details and resolution for error # 17.
License found but update failed. May need to check their network connect or check out the license so there is no interruption. Additional details and resolution for error # 20.
License found but license is not valid. Confirm system date on machine is correct and then send lservrc file to CSI to determine why license file is not valid.
|40, 50||License not served or provided/issued by CSI.|
|110||License file may be corrupted. Please contact CSI.|
|120||License file incomplete. For standalone licenses, deactivate license and then reactivate the license.|
Error when checking out license. Instructions to resolve error # 75.
Error when installing authorization code for remote machine. Additional details and resolution for error # 84.
Error when adding license. Usually related to the wrong version of LM (older version than required by license file). Additional details and resolution for error # 92.
|150||Error when adding license. "Error 150: The specified lock code is invalid." This error occurs when the locking code of the machine does not match the locking code of the license file. Run wechoid to check the locking code of the machine and compare it to the license file. If the license is locked to a USB key, the USB key driver may not be installed. To download the latest version of the Sentinel Driver, please visit here.|
Error when running activation tool for web-activated license . Additional details and resolution for error # 403.
|"Internal Error, Please contact..."||Received when running Standalonekey.exe. This is most likely due to the PC date/number format on the machine. Please change the PC date/number format to US mm/dd/yyyy to resolve.|
|":VLSrevokeByPermissionTicket"||Issue can occur when activating/deactivating license and may prevent any further activation/deactivations. May have multiple error numbers (such as error 143, ...). Instructions to resolve VLSrevokeByPermissionTicket.|
To troubleshoot licensing problems, you may find it useful to review the Sentinel RMS License Manager log file, given as CSI_SentinelLM.log in the application data directory.