Sentinel Licensing API Status Codes
Below is a list of possible return codes related to the operation of the Sentinel Licensing API functions.
No. | Status Code | Description |
---|---|---|
0 |
Request was successfully completed |
|
1 |
Request exceeds the Sentinel protection key memory range |
|
2 |
Legacy HASP HL Run-time API: Unknown/Invalid Feature ID option |
|
3 |
System is out of memory |
|
4 |
Too many open sessions exist |
|
5 |
Access to Feature was denied |
|
6 |
||
7 |
Sentinel protection key is no longer available |
|
8 |
Encrypted/decrypted data length too short to execute function call |
|
9 |
Invalid handle was passed to function |
|
10 |
Specified File ID is not recognized by API |
|
11 |
Installed driver is too old to execute function |
|
12 |
Real-time clock (RTC) not available |
|
13 |
Generic error from host system call |
|
14 |
Required driver is not installed |
|
15 |
File format for update is not recognized |
|
16 |
Unable to execute function in this context |
|
17 |
Binary data that was passed to function does not contain an update |
|
18 |
Sentinel protection key was not found |
|
19 |
Required
XML tags were not found |
|
20 |
Update request is not supported by Sentinel protection key |
|
21 |
Update counter is not set correctly |
|
22 |
Invalid Vendor Code was passed |
|
23 |
Sentinel protection key does not support encryption type |
|
24 |
The time value that was passed is outside the supported value range |
|
25 |
The real-time clock battery has run out of power |
|
26 |
Acknowledge
data that was requested by the update |
|
27 |
Program is running on a terminal server |
|
28 |
Requested Feature type is not implemented |
|
29 |
Unknown algorithm used in V2C or V2CP file |
|
30 |
Signature verification operation failed |
|
31 |
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: >A Feature required by the session was deleted. >The license was canceled. >The network (remote license) support setting for a required Feature was changed. (In this case, all sessions will be interrupted, including local sessions.) This may also indicate that the protection key is not available or that the user is attempting to bypass the application protection by using a protection key emulator. |
|
40 |
Communication error occurred between local and remote Sentinel License Managers |
|
41 |
Feature has expired |
|
42 |
Sentinel License Manager version is too old. Update Sentinel Run-time Environment to the latest version. |
|
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 or V2CP 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 or V2CP file with an update counter that is out of sequence with the update counter in the Sentinel protection key. The gap between the first value in the file and the value in Sentinel protection key is greater than 1. |
|
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 function does not specify a unique Product |
|
61 |
Invalid Product information |
|
62 |
Update can only be applied to recipient machine specified in the Detach function, 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 or or V2CP 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 Key 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 or V2CP 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 or reserve multiple executions while logging in to a Feature. However, the license does not contain the number of executions that were requested. |
82 |
|
The function is attempting to perform an operation that is not compatible with the target platform |
83 |
|
A Sentinel HL (Driverless configuration) key was disabled because a user attempted to tamper with the key or with the protected application |
84 |
|
An HL key is being shared by the use of a USB splitter device (such as Smart X). When this error occurs, a "sharing violation" message is also displayed on the relevant page in Admin Control Center. |
85 |
|
The session was interrupted manually from Admin Control Center or was interrupted due a network malfunction |
86 |
|
The function detected that the operation is being performed in virtual storage. The machine is using computer restoration software. |
87 |
|
(For identity-based licenses) An identity string is required |
88 |
|
(For identity-based licenses) The identity string is not authenticated |
89 |
|
(For identity-based licenses) The identity string is disabled |
90 |
|
(For identity-based licenses) The client identity does not have enough permission for the operation |
91 |
|
(For identity-based licenses) The session was killed because the identity string used to create the session was acquired by another machine. |
92 |
|
(For identity-based licenses) The maximum number of machines to which the identity string can be assigned was reached |
93 |
|
(For identity-based licenses) The option to store identity secrets with encryption was selected in Admin Control Center, but the authentication key was not yet defined (using Sentinel Admin API). |
94 |
|
You attempted to install a V2C file with an update counter that is out of sync with the update counter in the Sentinel protection key. The vendor should obtain a new C2V file from the customer and then generate a new V2C file. |
95 |
|
There were multiple attempts to access the key from a remote machine using a proxy. The user is attempting to access a license that does not support concurrency from a remote machine, using a proxy to make the remote machine appear as local. |
96 |
|
A cloud licensing session was released because the client requested the seat from a different location |
97 |
|
Cloud licensing authorization is required to use this license |
98 |
|
Invalid seat value in detach of seats with concurrency. Seat count cannot be decreased when modifying a detach |
99 |
|
Detach of seats with concurrency is disabled on a Product with only unlimited-concurrency features |
100 |
|
The requested cloud functionality is not supported |
101 |
|
Only a vendor who satisfied the documented requirements can install a license in trusted license storage |
102 |
|
A communication error occurred with the license storage |
103 |
|
The client identity has expired |
104 |
|
The option value specified for hasp_updateSession is not valid |
105 |
|
The license server is overloaded. The user should retry the operation in a few seconds. |
106 |
|
Login denied because the fingerprint cannot be fetched from this machine or the fingerprint fetched from this machine is not in the correct format |
107 |
|
Login denied because this machine is disabled |
108 |
|
The rate at which identity requests are received exceeds the contracted limit. |
109 |
|
Login denied because feature start date not yet reached. |
110 |
(For identity-based licenses) The identity string is currently not accessible because the server received too many requests to access the license. This is a temporary condition. The user should retry later. |
|
111 |
You cannot use both an identity string and a JWT for the same server address. | |
112 |
The JWT or LM access token is invalid. Restart the operation. | |
113 |
The JWT or LM access token has expired. Restart the operation. | |
|
Unable to locate dynamic library for API |
|
|
Dynamic library for API is invalid |
|
|
Requested
function was not found |
|
|
Object was incorrectly initialized |
|
|
Scope string is too long (maximum length is 32 KB) |
|
|
Logging in twice to same object |
|
|
Logging out twice from same object |
|
|
Incorrect use of system or platform |
|
|
Internal error occurred: No classic memory extension block available | |
|
Internal error occurred: Invalid port type | |
|
Internal error occurred: Invalid port value | |
|
Requested
function was not implemented |
|
|
Internal error occurred in the API |