Home > |
|
---|
In Windows systems, the local events, related to applications and services are displayed in the Event Viewer. To open the Event Viewer:
>From the Start menu, point to Settings > Control Panel > Administrative Tools.
>Double-click the Event Viewer icon. The Event Viewer dialog box appears.
>Click the Application icon to view the events for all the applications run on your system.
NOTE Sort the list as per Source. The RMS-specific messages are labeled as Sentinel RMS Development Kit License Manager. The event properties can be seen by right-clicking an event in the list.
The following operations (categorized into errors, information, and warnings) related to the Sentinel RMS License Manager are shown:
Category |
Event ID |
Message |
Comment |
Error ![]() |
29 |
The Sentinel RMS License Manager was unable to open the specified log file. |
During the License Manager initialization—opening of log files (usage and trace) failed. |
Error ![]() |
30 |
The Sentinel RMS License Manager was unable to open a socket. |
During the License Manager initialization, could not find a socket. |
Error ![]() |
31 |
The Sentinel RMS License Manager detected another license manager running on the same port. |
During the License Manager initialization, the specified port is already in use. |
Error ![]() |
32 |
The Sentinel RMS License Manager was unable to bind to its socket. |
During the License Manager initialization, socket bind error occurred. |
Error
![]() |
33 | The Sentinel RMS License Manager was unable to open file <filepath>. The Windows system error number is 5. | During the License Manager initialization. |
Error ![]() |
71 |
The Sentinel RMS License Manager failed to start because option <invalid-option> is invalid parameter. Valid parameters are: <option-symbol option-name>Example:The Sentinel RMS License Manager failed to start because option <invalid-option> is invalid parameter. Valid parameters are: [-s License-file] [-e License-configuration-file] [-l Usage-log-file] [-z Log-file-size] [-x No-log-file-truncation] [-u Group-reservations-file] [-port Port-number] [-rlf Redundant-license-file] [-com Percentage-of-commuter-keys-allowed] [-lfe Encryption-level <1..4>] [-us Upgrade-license-file] [-f Trace-message-file] [-tr Trace-level] |
During the License Manager startup, invalid startup option. |
Information |
76 |
Sentinel RMS License Manager, Version <8.x.x> Copyright (c) SafeNet, Inc. The license manager was successfully started on host <host name>. |
Successful service start. |
Error ![]() |
77 |
The Sentinel RMS License Manager was unable to start because an unknown error has occurred. |
During the License Manager initialization, an unknown error occurred. |
Warning
|
80 |
The Sentinel RMS License Manager service on host <host name> has been paused. |
Successful service pause. |
Information |
81 |
The Sentinel RMS License Manager service on host <host name> has been resumed. |
Successful service resume (after pause). |
Error ![]() |
82 |
The Sentinel RMS License Manager service on host <host name> has been stopped. |
The License Manager stopped due to an error. Note this message will be printed |
Warning
|
83 |
The Sentinel RMS License Manager was unable to open the license file <license store file name>. No applications are licensed. |
During the License Manager initialization or adding/validating the client library API function, the license could not be installed due to failure in accessing license store, such as inability to access the file. |
Warning
|
84 |
The Sentinel RMS License Manager received the following invalid license: <license code>. Reason: <Reason>. |
When the license table is being loaded after the License Manager initialization, the license is found invalid. This could be due to many reasons, such as: an invalid license version, a standalone license being added on a License Manager, vendor ID mismatch, a redundant license being added to a non-redundant License Manager, clock tampering detected and so on. |
Warning
|
85 |
The Sentinel RMS License Manager was unable to initialize from the license code <license code>. |
During the License Manager initialization or adding/validating the client library API function—the license could not be installed due to an internal error. |
Warning
|
86 |
The Sentinel RMS License Manager is not authorized to license the feature <feature name> on this machine. The license key code <license code> has not been added to the license manager registry. |
During the License Manager initialization or adding/validating the client library API function, the license could not be installed due to some reason(s), such locking code mismatch. |
Information |
90 |
The Sentinel RMS License Manager shut down. |
Successful service shut-down. |
Warning
|
108 |
In Sentinel RMS License Manager, license revocation-related initialization failed. |
During the License Manager startup when a revoke license request is made, the revoke persistence database is found corrupt and unrecoverable. |
Error ![]() |
109 |
The Sentinel RMS License Manager failed to start.No value is specified for option <invalid-option> |
During the License Manager startup, the startup option was passed without a value. For example, the -z option is passed without any value. |
Error ![]() |
110 |
The Sentinel RMS License Manager failed to start.Invalid value is specified for option <invalid-option>. |
During the License Manager startup, the startup option value passed is incorrect, which led to initialization failure. |
Information |
111 |
The Sentinel RMS License Manager has set default value <default value> for server option <server option> because of invalid value specified. |
During the License Manager startup, the option was not set, or an invalid value was passed. Hence, the default value is used. For example, for port 5093 is used. |
Error ![]() |
112 |
The Sentinel RMS License Manager was unable to compute machine locking code. |
When the license table is being loaded after the License Manager initialization, failed to compute the locking code of the system, where the License Manager is running. |
Information |
113 |
The Sentinel RMS License Manager is switching over the trace file because of maximum size reached. Backed up file name is <backed up file name>. |
During the License Manager execution, if tracing is enabled and -z option is set, the maximum file size is reached. The automatic switchover of files takes place. |
Warning
|
114 |
The License Manager (service) has faced input output error during tracing. |
During execution, if tracing is enabled, an input/output error occurs. |
Information |
115 |
The Sentinel RMS License Manager is starting as non-redundant License Manager. |
During execution, if no/invalid redundant file is specified in -rlf server option. |
Error ![]() |
116 |
The Sentinel RMS License Manager was stopped by the license install policy |
The license installation policy of the customized License Manager chose to stop the License Manager. The corresponding license string (that could not be installed/loaded) can be found under the Event details. |
Error ![]() |
117 |
NT_SERVER_SHUTDOWN_SERVER_NOT_BUILD_PROPERLY |
The Sentinel RMS License Manager failed to start, either vendor identifier not set or the server has been built with incorrect server library. |
Information |
118 |
The Sentinel RMS License Manager has started with the default socket buffer(IPv6) size value set to 8192 bytes.
|
An invalid value was specified as the multiplier with -sbm option.
Use non zero, positive numerical values with this License Manager Startup option. |