Sentinel Error Codes
- Copy Page Tree
- W.Erber
This section describes important Sentinel error codes, their meaning, and possible remediation actions. There are several other documents on the Stromasys web-page dealing with specific Sentinel error codes in more detail (see Resources).
Common HASP error codes
The following table provides an overview of HASP error codes commonly seen in a Charon environment and their meaning.
A complete list with Sentinel License API status codes can also be found on the Sentinel web page under Sentinel Licensing API Status Codes.
Error code | Description | Solution | ||
|---|---|---|---|---|
| 4 | HASP_TMOF Too many open sessions. Displayed hasp_srm_view message: "Sentinel HASP key not found or of improper type (4). Warning! Program running on a terminal server, license access might be limited!" | This error occurs when trying to create a .c2v file via a remote connection. Possible workaround on Windows: See How to read a HASP key over RDP on Windows. Possible workaround on Linux: Run the command via ssh to localhost, for example:
| ||
| 7 | HASP_HASP_NOT_FOUND Sentinel protection key not available. Displayed hasp_srm_view message: "Sentinel HASP key not found or of improper type (7)." | Connect the license dongle or install a software license. Due to a software bug, this error can also occur when the license is connected. Please refer to Charon-AXP and Charon-VAX license not found error for a detailed description and a workaround. | ||
| 18 | HASP_KEYID_NOT_FOUND Sentinel protection key with the specified key ID not found. Displayed hasp_srm_view message: "Sentinel HASP key not found or of improper type (50)." | Connect the license dongle with the correct key ID or correct the parameter specifying the key ID. | ||
| 19 | HASP_INV_UPDATE_DATA Required XML tags not found, or contents in binary data are missing or invalid | If this error occurs when trying to apply a V2C file to a system, the most likely cause is a corruption of the V2C file content. For example, an XML tag may be invalid. In some cases it is possible to edit the V2C file and fix the problem. Please refer to Unable to apply license file, V2C file data is invalid for more details. | ||
| 27 | HASP_TS_DETECTED Program running on a terminal server. Displayed hasp_srm_view message: Sentinel HASP key not found or of improper type (27). | The Sentinel key content cannot be displayed when connected via a remote connection. Possible workaround on Windows: See How to read a HASP key over RDP on Windows. Possible workaround on Linux: Run the command via ssh to localhost, for example:
| ||
| 31 | HASP_FEATURE_NOT_FOUND Requested Feature not found | In addition to a required feature missing on the key, this error can also occur if proper connection to the key is lost. Removing and reinserting solves the problem in this case. A solution without removing the dongle is described in Charon for Linux - Detected removal of the license whereas dongle is connected. | ||
| 33 | HASP_LOCAL_COMM_ERR Communication error between API and local Sentinel License Manager | This error code indicates that the Sentinel license manager software is not running. | ||
| 38 | HASP_TOO_MANY_USERS | Too many users are currently connected. This error occurs, when more than the allowed number of license clients try to connect to a license (typically a network license). Workarounds:
| ||
| 39 | HASP_BROKEN_SESSION Session was interrupted. | This can occur when certain updates are applied to the license while a session is active. For example:
This may also indicate that the protection key is not available. | ||
| 42 | HASP_OLD_LM The Sentinel License Manager version is too old. | There is a version mismatch. Check if your Sentinel Runtime version is the correct one for your Charon product. In case of questions, contact your VAR or your Stromasys representative for guidance. | ||
| 43 | HASP_DEVICE_ERR For a Sentinel SL key, an input/output error occurred in the secure storage area. | For a hardware dongle, verify the USB connection. If the USB port works and the aksusbd is running, consider a possible failure of the dongle. For a software license, this very likely indicates a software license problem caused by a change on the host system. You can try to revert any changes, but this will not necessarily make the license operational again (see HASP Software Licensing restrictions). | ||
| 48 | HASP_NO_VLIB Unable to find Vendor library. | If this error occurs when you try to install a software license with the Sentinel Admin Control Center, refer to the following document for a possible workaround: HASP_NO_VLIB error 48 message when installing a software license. | ||
| 50 | HASP_SCOPE_RESULTS_EMPTY Unable to locate any Feature matching scope. | This error can occur when you have specified a license key id in the configuration file and this license key cannot be read (unplugged) Configuration file example:
Log file example:
Possible solutions:
| ||
| 54 | HASP_UPDATE_TOO_OLD Trying to install a V2C (vendor to customer) file with an update counter that is out of sequence with the update counter on the Sentinel protection key. The update counter value in the V2C file is lower than the value in Sentinel protection key. | Apply all other license key updates, even if they have expired, then attempt to reapply the failed update. If this still does not resolve the problem, contact Stromasys Orders Administration with a new C2V (customer to vendor) file. | ||
| 55 | HASP_UPDATE_TOO_NEW Trying to install a V2C file with an update counter that is out of sequence with update counter in the Sentinel protection key. The first value in the V2C file is greater than the value in the Sentinel protection key. | Apply the V2C files in the correct sequence or request an update which disregards the unapplied update. See also Sentinel Admin Control Center - Attach/Update errors. | ||
| 64 | HASP_CLONE_DETECTED Cloned Sentinel SL storage was detected. Feature is unavailable. | Indicates that the system on which the fingerprint was created was changed in a way that affects the validity of the license (e.g., cloning a VM). For more, see: | ||
| 65 | HASP_UPDATE_ALREADY_ADDED The message indicates you are trying to update the license with a V2C file that has already been applied, either the V2C format file ( _fmt ) or the update file. | Check the current applied license or request for new V2C files. See also License Update Service utility reports "update was already installed". | ||
| 78 | HASP_SECURE_STORE_ID_MISMATCH A secure storage ID mismatch occurred. If a software license is used, this error can occur if host system hardware characteristics are changed. | To avoid the problem, do not change any hardware characteristics of a host system when using software licenses. If the error occurs, try to revert any changes. However, this may not solve the problem. In this case, contact your partner or Stromasys support. | ||
| 84 | HASP_SHARING_VIOLATION An HL key is being shared between several systems. When this error occurs, a "sharing violation" message is also displayed on the relevant page in Admin Control Center. | This error can happen, for example, if a license key is passed through to a virtual machine and used by the Hypervisor system at the same time. |
© Stromasys, 1999-2024 - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.