System Initialization Error Codes

The LSINIT functions will return the ORed value of the [first-level status code] and [second-level status code]. For example, for first-level status code 0x10000000 and second-level status code - 0x00001000, the ORed value returned will be 0x10001000.

This indicates initialization failure for a time tampering enabled license because the file could not be written.

You can decipher these status codes as described below:

Hexadecimal Code	Status Code	Description
First Level Status Codes
0x10000000	ERR_TIME_TAMPER_INIT_FAIL	Failed to create time tamper-related persistence
0x20000000	ERR_COMMUTER_PRS_INIT_FAIL	Failed to create commuter license-related persistence
0x40000000	ERR_GRACE_PRS_INIT_FAIL	Failed to create grace license-related persistence
0x80000000	ERR_TRIAL_INIT_FAIL	Failed to create trial license-related persistence
0xF0000000	ERR_STDRVK_INIT_FAIL	Failed to create standalone revocation-related persistence
0x01000000	ERR_CONSUME_INIT_FAIL	Failed to create volume transaction license-related persistence
0x04000000	ERR_CANCEL_LEASE_INIT_FAIL	Failed to create cancel lease license-related persistence

Second Level Status Codes
0x00000000	ERR_KEY_INFO_SUCCESS	Success
0x00000001	ERR_INVALID_INPUT	Verify the inputs passed to the API.
0x00000002	ERR_INIT_LIB_FAIL	Library not serialized properly. This can come if the installation of the RMS SDK is not proper or an incorrect serial number is used for installation.
0x00000004	ERR_NO_PERSISTENCE_DEVICE	The initialization library is initialized to run in VLS_CPD_NO_DEVICE mode.
0x00000008	ERR_INIT_INFO_EXISTS	Already initialized
0x00000010	ERR_INIT_SEC_FAIL	Initialization of security descriptor in registry failed 2
0x00000020	ERR_INIT_KEY_FAIL	Failed to create registry information (only for Windows).
0x00000040	ERR_INIT_KEY_SEC_FAIL	Permission failure for secure registry (only for Windows)
0x00000080	ERR_INIT_OPEN_KEY_FAIL	Registry open failure (only for Windows)
0x00000100	ERR_INIT_SET_VALUE_FAIL	Error in modifying values in registry key (only for Windows)
0x00000400	ERR_INIT_FILE_FAIL	Error in creating file or setting security
0x00000800	ERR_INIT_FILE_OPEN_FAIL	Error in opening file
0x00100000	ERR_INIT_FILE_READ_FAIL	Error in reading file
0x00001000	ERR_INIT_FILE_WRITE_FAIL	Error in writing into file
0x00002000	ERR_INIT_FILE_SEC_FAIL	Error in setting file security
0x00020000	ERR_INSUFFICIENT_PERMISIONS	Do not have sufficient rights to access the file
0x00100000	ERR_INIT_FILE_READ_FAIL	Error in reading file
0x00001000	ERR_INIT_FILE_WRITE_FAIL	Error in writing into file
0x00002000	ERR_INIT_FILE_SEC_FAIL	Error in setting file security
0x00020000	ERR_INSUFFICIENT_PERMISIONS	Do not have sufficient rights to access the file
0x00000200	ERR_INIT_QUERY_FAIL	Read failure on secure registry (only for Windows). Can occur due to permission problems.
0x00004000	ERR_EXCEPTION_OCCURED/ ERR_EXCEPTION_OCCURRED	An exception occurred during execution. The ERR_EXCEPTION_OCCURRED error has been added in 8.5.3
0x00008000	ERR_INIT_FILE_INFO_EXISTS	Initialization file information (full or partial) exists.
0x00010000	ERR_INTERNAL_FAIL	Internal error. Contact Technical Support with details about the scenario in which the error is being observed.
0x00040000	ERR_TAMPER_DETECTED	Secure data is tampered (only for UNIX)
0x00080000	ERR_INIT_PATH_FAILED	Error in retrieving persistence database location
0x00200000	ERR_NORESOURCES	Failure in obtaining system resources
0x00400000	ERR_LOCK_ERROR	The resource lock required by the application was not available or already busy. Either retry or restart the system.
0x00800000	ERR_INIT_CONFIG_FAIL	Error encountered in setting persistence file location.

1 - These error codes can be ignored if you are not dealing with the specific type of persistence type. Otherwise, you can perform persistence cleaning\repairing using the appropriate API or utilities.

2 - Errors from 0x00000010 to 0x00020000 in the table above are file\folder permission problems that can be encountered when API not executed as administrator.