No. | Status Code | Description |
---|---|---|
0 |
StatusOk |
Request was successfully completed |
1 |
InvalidAddress |
Request exceeds the Sentinel protection key memory range |
2 |
|
Legacy HASP HL Run-time API: Unknown/Invalid Feature ID option |
3 |
NotEnoughMemory |
System is out of memory |
4 |
TooManyOpenFeatures |
Too many open sessions exist |
5 |
AccessDenied |
Access to Feature was denied |
6 |
IncompatibleFeature |
|
7 |
ContainerNotFound |
Sentinel protection key is no longer available。读取不到指定的狗。 |
8 |
BufferTooShort |
Encrypted/decrypted data length too short to execute method call |
9 |
InvalidHandle |
Invalid handle was passed to method |
10 |
InvalidFile |
Specified File ID is not recognized by API |
11 |
DriverTooOld |
Installed driver is too old to execute method |
12 |
NoTime |
Real-time clock (RTC) not available |
13 |
SystemError |
Generic error from host system call |
14 |
|
Required driver is not installed |
15 |
InvalidFormat |
File format for update is not recognized |
16 |
RequestNotSupported |
Unable to execute method in this context |
17 |
InvalidUpdateObject |
Binary data that was passed to method does not contain an update |
18 |
KeyIdNotFound |
Sentinel protection key was not found |
19 |
InvalidUpdateData |
Required
XML tags were not found |
20 |
UpdateNotSupported |
Update request is not supported by Sentinel protection key |
21 |
InvalidUpdateCounter |
Update counter is not set correctly |
22 |
|
Invalid Vendor Code was passed |
23 |
EncryptionNotSupported |
Sentinel protection key does not support encryption type |
24 |
InvalidTime |
The time value that was passed is outside the supported value range |
25 |
NoBatteryPower |
The real-time clock battery has run out of power |
26 |
UpdateNoAckSpace |
Acknowledge data that was requested by the update ack_data parameter is NULL |
27 |
TerminalServiceDetected |
Program is running on a terminal server |
28 |
FeatureNoteImplemented |
Requested Feature type is not implemented |
29 |
UnknownAlgorithm |
Unknown algorithm used in V2C file |
30 |
InvalidSignature |
Signature verification operation failed |
31 |
FeatureNotFound |
Requested Feature not found |
32 |
|
Access log not enabled |
33 |
|
Communication error occurred between the API and the local Sentinel License Manager |
34 |
|
Vendor Code is not recognized by API |
35 |
|
Invalid XML specification exists |
36 |
|
Invalid XML scope exists |
37 |
|
Too many Sentinel protection keys are currently connected |
38 |
|
Too many users are currently connected |
39 |
|
Session was interrupted. This can occur when certain updates are applied to the license while a session is active. For example:
|
40 |
|
Communication error occurred between local and remote Sentinel License Managers |
41 |
|
Feature expired or no executions remain |
42 |
|
Sentinel License Manager版本过旧,需要更新。 |
43 |
|
For
a Sentinel SL key, an input/output error occurred in the secure
storage area |
44 |
|
Update installation not permitted |
45 |
|
System time has been tampered with |
46 |
|
Communication error occurred in the secure channel |
47 |
|
Corrupt data exists in secure storage area of Sentinel protection key |
48 |
|
The customized vendor library (haspvlib.vendorID.*) cannot be located |
49 |
|
Unable to load Vendor library |
50 |
|
Unable to locate any Feature that matches the scope |
51 |
|
Protected
application is running on a virtual machine, but one or more Features
are not enabled for virtual machines. |
52 |
|
Sentinel
SL key incompatible with machine hardware. Sentinel SL key locked
to different hardware. |
53 |
|
Login denied because of user restrictions |
54 |
|
Trying to install a V2C file with an update counter that is out of sequence with update counter in the Sentinel protection key. Values of update counter in file are lower than those in Sentinel protection key. |
55 |
|
Trying to install a V2C file with an update counter that is out of sequence with the update counter in the Sentinel protection key. First value in file is more-than-1 greater than value in Sentinel protection key. |
56 |
|
Vendor library is too old |
57 |
|
Check in of a file (such as V2C, H2R) using Admin Control Center failed, possibly because of illegal format |
58 |
|
Invalid XML RECIPIENT parameter |
59 |
|
Invalid XML action parameter |
60 |
|
The scope specified in the Transfer method does not specify a unique Product |
61 |
|
Invalid Product information |
62 |
|
Update can only be applied to recipient machine specified in the Detach method, not to this machine |
63 |
|
Invalid
detached license duration period specified. Duration must be less
than or equal to maximum allowed for this license. |
64 |
|
Cloned Sentinel SL storage was detected. Feature is unavailable. |
65 |
|
The specified V2C update was already installed in the License Manager service |
66 |
|
Specified Key ID is in Inactive state |
67 |
|
No detachable Feature exists in the specified key from which the detached license is requested |
68 |
|
The specified scope does not specify a unique host |
69 |
|
Rehost action is not allowed for the specified HASP ID |
70 |
|
Original license has been transferred to another machine. Therefore, the license cannot be returned to the source machine. |
71 |
|
Old rehost license cannot be applied. A rehost-counter mismatch occurred |
72 |
|
A V2C file was not found, or access was denied |
73 |
|
The license cannot be extended because the number of detached licenses is greater than the number of concurrent licenses allowed |
74 |
|
The user attempted to detach a Product from a network license hosted on a virtual machine. However, none of the Features included in the Product are enabled for virtual machines. |
75 |
|
The user attempted to rehost a protection key from a virtual machine. However, none of the Features contained in the protection key are enabled for virtual machines. |
76 |
|
The user attempted to format an SL-AdminMode key or to migrate an SL-Legacy key to an SL-AdminMode key. However, a Product is currently detached from the key. |
77 |
|
For a rehost operation: The fingerprint of the target machine was collected using tools (RUS utility or Licensing API) earlier than Sentinel LDK v.7.0. |
78 |
|
A secure storage ID mismatch occurred. |
79 |
|
The license fingerprint is bound to a specific hostname; however, two or more machines with this hostname were found in the network. As a result, the license cannot be used. |
80 |
|
A protected application tried to log in to a Feature that supports concurrency on a Sentinel HL (Driverless configuration) key. The Sentinel LDK License Manager service is not active on the computer where the key is located. |
81 |
|
A protected application tried to consume multiple executions while logging in to a Feature. However, the license does not contain the number of executions that were requested. |
|
|
Unable to locate dynamic library for API |
|
|
Dynamic library for API is invalid |
|
InvalidObject |
Object was incorrectly initialized |
|
InvalidParameter |
Scope string is too long (maximum length is 32 KB) |
|
AreadyLoggedIn |
Logging in twice to same object |
|
AlreadyLoggedOut |
Logging out twice from same object |
|
OperationFailed |
Incorrect use of system or platform |
652 | HaspDotNetDllBroken | .NET DLL found broken |
|
|
Requested
function was not implemented |
|
|
Internal error occurred in the API |