The HASP dongle can cause errors. The errors are listed below with a possible solution.
If the error keeps returning please create a JIRA issue or contact the Support department.
|
Error message |
Possible solution |
|---|---|
|
Invalid handle passed to function |
|
|
Communication error between API and local Sentinel License Manager |
|
|
Communication error between local and remote Sentinel License Manager |
|
|
Unrecognized file identifier |
|
|
Request exceeds the memory range of a Sentinel file |
|
|
Input/Output error in Sentinel secure storage, or, in case of a Sentinel HL key, USB communication error |
Replug dongle |
|
Session has been interrupted |
Replug dongle |
|
Out of memory |
Replug dongle |
|
Unrecognized format string |
Replug dongle |
|
System time has been tampered with |
Reboot and retry |
|
Required Sentinel protection key not found |
Replug dongle |
|
Cannot find requested Feature |
Buy new license |
|
Unable to locate a Feature matching the scope |
Replug dongle |
|
Too many open login sessions |
Reboot and retry |
|
Invalid Vendor Code |
Buy new license |
|
Driver not installed |
|
|
Driver too old |
|
|
Communication error occurred in secure channel OR Sentinel HL Firmware too old (update to 3.25 or later) |
|
|
Vendor Library cannot be found |
|
|
Vendor Library cannot be loaded |
|
|
Vendor Code not recognized |
Buy new license |
|
Scope string too long (max. length 32 kB) |
Replug dongle |
|
Feature has expired |
Buy new license |
|
Too many users currently connected |
Reboot and retry |
|
Sentinel License Manager version too old |
|
|
Program is running on a Terminal Server |
Reboot and retry |
|
Sentinel SL key incompatible with machine hardware; Sentinel SL key is locked to different hardware |
|
|
Vendor Library version too old |
|
|
Cloned Sentinel SL storage detected. Feature unavailable |
Replug dongle |
|
Unknown HASP result code |
Contact Support Department |
Return to: How-to View your Licenses