Error and Result Codes
The table below contains the licensing library error messages:
| Error Code | Error Message | Action Owner | Suggested Action |
|---|---|---|---|
| Common Licensing Errors | |||
|
1001 |
No authorization server mapped to given vendor ID |
Thales/Software Vendor |
Thales - Ensure that the Sentinel Cloud Connect is up and running. Software Vendor - Initialize the client library again (by creating an instance of the ApplicationContext class). |
|
1002 |
Customer is invalid |
Software Vendor | While creating an instance of the Identity class, ensure to provide a correct value in the SNTL_ATTR_IDENTITY_CUSTOMER_ID attribute. |
|
1003 |
Value of identity string passed in input parameter is invalid |
Software Vendor | Either customer or user has not provided in Identity or the provided value is incorrect. Provide the correct details. |
|
1004 |
User is invalid |
Software Vendor | While creating an instance of the Identity class, ensure to provide a correct value in the SNTL_ATTR_IDENTITY_USERNAME attribute. |
|
1005 |
Error in calling the API function. Check the calling parameters |
Software Vendor | Check the API calling parameters. |
|
1006 |
Authentication Failed |
Software Vendor |
Authentication failed due to any of the following reasons: >Mismatch in Secret Key >Mismatch in Secret Key ID >Incorrect Vendor ID >Time mismatch Open the configuration file and ensure that correct values are specified in the following properties: >SecretKey >SecretKeyId >VendorID Also, ensure that the machine time is in sync with the global UTC time. |
|
1008 |
The feature cannot run anymore because the license expiration date has reached. |
Software Vendor |
Make sure that your machine's date and time zone are correct. Otherwise, contact your vendor for a new license. Also, the request should have a valid license start date and end date. It is recommended to use getInfo to check details of all license attributes. |
|
1009 |
License is disabled. |
Software Vendor |
The state of the entitlement or line item is disabled. Set the state from disabled to enabled from EMS. |
|
1010 |
License does not exist or license is not in active state. |
Software Vendor |
The license start date is not reached, or the feature name - version or customer passed during the login API call does not belong to an activated entitlement. Use getInfo to check the license state (usabilityStatus). |
|
1011 |
Concurrency limit is reached. |
Software Vendor |
Either terminate an existing concurrency session of a license using logout, or wait for it to be released by some other session. If it is released, the concurrency count will be available for consumption. Use getInfo to obtain details about running sessions. |
|
1012 |
Usage limit is reached. |
Software Vendor | Create a new entitlement to issue license or increase the usage limit from EMS. |
|
1013 |
Internal system error. |
Software Vendor, Thales |
Software Vendor - Change the log level and , run the application again for the same scenario, and contact Thales with the related logs for troubleshooting. Thales - Check if all the backend components including databases are up and running. Also ensure that licensing libraries and license generator belong to the same vendor. |
|
1015 |
Session terminated. |
Software Vendor |
This error is returned when refresh is called for an abandoned session. If the refresh API is called after a session has been closed by the background thread, the API returns this error. Ensure to call the refresh API periodically. |
|
1016 |
Authentication Failed due to time mismatch. |
Software Vendor |
The authentication error occurs due to time mismatch between the Sentinel Cloud Connect and the machine requesting the license. Ensure that the machine time is in sync with the global UTC time. |
| 1017 | Sufficient license count not available. | Software Vendor |
When counts requested in login call is greater than the available counts for a license. Use getInfo to check the available counts. Pass a lesser value in login, or reconfigure the entitlement from EMS and increase the usage limit. |
| 1018 | Sufficient concurrency count not available. | Software Vendor | When current concurrent user count is greater than maximum number of concurrent users. |
| 1019 | You can’t return more usage count than requested in the license session. | Software Vendor | When count returned in refresh call is greater than the consumed count in login call. |
| Runtime Errors | |||
|
2002 |
Error in calling the API function. Check the calling parameters. |
Software Vendor | If the issue persists, contact Thales. |
|
2003 |
Unable to de-initialize runtime library |
Software Vendor | Calling the API again may solve this. If the issue persists, contact Thales. |
|
2004 |
Error in network communication. Please check YPS address (in configuration file), internet connection and proxy settings. |
Software Vendor | If the issue persists, contact Thales. |
|
2005 |
Problem in configuration file reading. |
Software Vendor |
Please the configuration file at the correct location. |
|
2006 |
Invalid YPS address in configuration file. |
Software Vendor | Set the corresponding property correctly in the configuration file. |
|
2009 |
This operation is not supported. |
Software Vendor | Refer to the API specification for help on the correct use of the API. |
|
2010 |
Invalid library. |
Thales |
Please validate the library details. |
|
2011 |
Value of session handle passed in input parameter is invalid. |
Software Vendor |
The session handle is invalid or null during the refresh or logout API call. Ensure that the session handle returned from login is passed to refresh or logout. |
|
2012 |
Please initialize licensing library. |
Software Vendor |
The licensing library is not initialized. Initialize the ApplicationContext. Ensure that the license has been acquired successfully. |
|
2013 |
Value of query passed in input parameter is invalid. |
Software Vendor | The query string passed in getInfo is invalid. Please provide the correct details. |
|
2014 |
Value of scope passed in input parameter is invalid. |
Software Vendor | The scope string passed in getInfo is invalid. Please provide the correct details. |
|
2015 |
Units are not supported with limited concurrency. |
Software Vendor |
The SNTL_ATTR_LOGIN_UNITS_REQUIRED attribute in the login API is supported with only unlimited concurrency. Do not set this attribute for licenses where the concurrency limit is set. |
|
2016 |
Value of units passed in input parameter is invalid. Valid range is 1 to 2147483647. |
Software Vendor | Provide the inputs value in the valid range. |
|
2017 |
Configuration file not found. |
Software Vendor | Make sure that the configuration file is placed at the correct location and is accessible by the application. |
| 2018 | Value of usage count passed in input parameter is invalid. Valid range is 1 to 2147483647. | Software Vendor | Pass valid values in SNTL_ATTR_LOGIN_USAGE_COUNT_MULTIPLIER. |
| 2019 | Value of feature name passed in input parameter is invalid. | Software Vendor |
Ensure that the feature name is not passed as null in login or getInfo. |
| 2020 | Invalid value of UsageSyncFrequency in configuration file. | Software Vendor | Ensure that the UsageSyncFrequency property (in configuration file) has a valid value. |
|
2021 |
Feature version should be accompanied with feature name. |
Software Vendor | |
|
2022 |
Product version should be accompanied with product name. |
Software Vendor | |
|
2023 |
userSpecificEntitlement is invalid, allowed values are either true or false. |
Software Vendor | |
| 2024 | Value of usage count passed in input parameter is invalid. Except 0, valid range is -2147483647 to 2147483647. | Software Vendor | Provide valid values in SNTL_ATTR_REFRESH_USAGE_COUNT_MULTIPLIER and SNTL_ATTR_LOGOUT_USAGE_COUNT_MULTIPLIER. |