Introduction
Current system health status is reported in the vSEC:CMS Admin console. Depending on what version you currently run this information will be displayed in different ways. This article will describe the different system health IDs along with ways on how to resolve them.
From versions prior to 7.0 the system health status can be seen from the Home page where you will see a circle on the bottom right of the console. The circle can be either green, yellow or red.
- Green: System health is good and nothing needs to be resolved
- Yellow: System health has some issues reported that are not critical but should be evaluated as to whether they need to be resolved or not
- Red: System health has some issues that should be looked into and resolved as they may be critical to the operations of your system.
vSEC:CMS versions from 7.0 and later will display their system health status directly from the Home page to make it more obvious to Admin's. Double click an entry to see more details. Also there will be a link to a Web page with even more details as to what the particular entries mean and how to resolve them.
System Health IDs
Below is full table of all the IDs and brief description of the different types of issues that can be encountered. Some IDs will have a tip on how to resolve them. If you don't find a resolution then please open a support ticket from here.
The ID as shown in the table corresponds to the ID as shown in the System Status dialog.
ID |
System Health Message |
Detailed description |
Status |
001 |
Backup failed. |
Reports problems when scheduled backup fails. Tip: Check the Options – Settings – Backup Settings to ensure configuration is correct. |
Red |
002 |
No Operator Service Card available. |
If the keystore operator is configured, but the OSC is not functioning. Tip: Check the Options – Operators page to ensure the keystore operator is available and activated. |
Yellow |
003 |
No automatic backup. |
If backup is enabled but no backup folder configured. Tip: Check the Options – Settings – Backup Settings to ensure configuration is correct. |
Red |
004 |
Pending certificate revocation requests. |
There are pending revocation requests in the application cache. Tip: Check the Options – Connections page and in the Certificate Authorities section click the link for Number of certificates to revoke. Also check that connectivity to the CA is functioning. |
Yellow |
005 |
Pending data export records. |
There are pending data export requests in the application cache. Tip: Check the Options – Connections page and in the Data Export section click the link for Number of pending requests. |
Yellow |
006 |
Pending events. |
There are pending Window events that exist in the application cache. Tip: Check the Options – Connections page and in the External Trace section click the link for Pending packages. |
Yellow |
007 |
Photo capturing not configured. |
Check all card templates available for the current logged on operator. If there are templates which do contain photo capturing but there is no photo capture device configured for the current client machine. Tip: Check the Options – Connections page and click the Configure button for Photo Capture from where the photo capture device can be configured. |
Yellow |
008 |
Enrollment agent certificate problem. |
Checks all card templates available for the current logged on operator. If there are templates which are configured to do certificate enrollment using MS CA with signed requests but the configured EA certificate cannot be found and/or is not on current operator token. Tip: Check the Options – Connections page and click the Configure button for Certificate Authorities. Select the CA template and ensure that an EA certificate is configured in the Enrollment Agent section. |
Yellow |
009 |
Smart card printer not configured. |
Checks all card templates available for the current logged on operator. If there are templates which are configured for card printing but there is no printer configured and/or online for the current client machine. Tip: Check the Options – Connections page and click the Configure button for Smart Card Printer and ensure that the configuration is correct. |
Yellow |
010 |
User license low |
If the user license count is less than 10% this will be flagged as a warning to the operator. Tip: Purchase additional user licenses if required. |
Yellow |
011 |
License problem. |
If the user license count is zero this will be flagged as an error to the operator. Tip: It will not be possible to manage any additional smart card tokens when in this state. It will be necessary to purchase additional user licenses. |
Red |
012 |
Operator license low |
If the operator license count is less than 10% this will be flagged as a warning to the operator. Tip: Purchase additional operator licenses if required. |
Yellow |
013 |
License problem. |
If the operator license count is zero this will be flagged as an error to the operator. Tip: It will not be possible to add additional operators when in this state. It will be necessary to purchase additional operator licenses. |
Red |
014 |
User failed to logon. |
User failed to logon because the signature was not valid. |
Yellow |
015 |
No smart card driver found. |
If the attached operator card is available and it is a PC/SC smart card, the application checks if a minidriver is available for this smart card. In addition, checks for Gemalto .NET and IDPrime smart cards are performed. Tip: It will be necessary to install the latest Gemalto minidriver on the machine. |
Yellow |
016 |
DB Disk Space Low |
If the disk space available on the server where vSEC:CMS is installed is 2 times the size of the current database size then this will be flagged as a warning to the operator. Tip: Remove and/or clean up the file system to create more space if required. |
Yellow |
017 |
DB Disk Space Out |
If the hard disk space available on the machine where vSEC:CMS is installed is 1 times the size of the current database size then this will be flagged as an error to the operator. Tip: Remove and/or clean up the file system to create more space if required. |
Red |
018 |
Not enough space on database disk. |
If the space available on the operator token smart card is less than 4500 bytes this will be flagged as a warning to the operator. Tip: Remove and/or clean up the file system on the operator smart card token. |
Yellow |
019 |
Not enough space on database disk. |
If the space available on the operator token smart card is less than 2000 bytes this will be flagged as an error to the operator. Tip: Remove and/or clean up the file system on the operator smart card token. |
Red |
020 |
Not enough space on Operator token. |
If there is no available minidriver for the attached user smart card that is to be managed by the vSEC:CMS. Tip: It will be necessary to install the smart card vendor minidriver on the machine where the vSEC:CMS is running. |
Yellow |
021 |
Error occurred in self-service session. |
An invalid session has been detected in USS-SOAP communication. Tip: Try restarting the vSEC:CMS User Self-Service on the server. |
Red |
022 |
Invalid authentication attempt through self-service. |
An internal problem has been detected in USS-SOAP communication around user authentication. Tip: Try restarting the vSEC:CMS User Self-Service on the server. |
Red |
023 |
Self-service server problem detected. |
If self-service is licensed and configured but the service is not running. Tip: Check the Windows services and ensure that vSEC:CMS - User Self-Service service is running. |
Yellow |
024 |
Self-service server not configured. |
If the self-service featured is licensed but not configured. Tip: Check the Options – Connections page and click the Configure button for User Self-Service and ensure that the configuration is correct. |
Yellow |
025 |
A problem has been detected with a variable. |
If an imported variable is configured but the imported database is not available. Tip: Check the Options – Connections page and click the Configure button for Variables and ensure that the configuration is correct for the reported variable. |
Red |
026 |
Updating repository table. |
If vSEC:CMS has been upgraded from version 3.1 the certificate expiry field in the smart card repository table in the database for version 3.1 was not set correctly. Therefore, it is necessary to update the table in version 3.2 to the correct expiry date for the issued certificates. Tip: Operator should allow this update to complete. This update will run in a background thread. |
Yellow |
027 |
Plugin security warning. |
If the loading of unsigned DLL plugins is configured from the Options – Security page this warning will be displayed. Typically, unsigned DLLs would be enabled when testing a plugin. Tip: It is recommended to not have this feature enabled in a production environment |
Yellow |
028 |
Using unsigned library extensions Dynamic Link Libraries. |
The system is using unsigned library extension Dynamic Link Libraries. This will occur because of a missing or invalid signature file. Tip: Make sure that the library is signed and that the SHA-1 hash of the library has been provide to Versasec. |
Yellow |
029 |
Tried to loaded an untrusted plugin. |
If the loading of unsigned DLL plugins is configured from the Options – Security page and an unsigned DLL is loaded then this warning will be displayed. Tip: It is recommended to not have an unsigned DLL loaded in a production environment. |
Yellow |
030 |
Key archival not working. |
If the key archival mechanism is not initialized correctly an error will appear. Tip: Contact Versasec if this message appears for details on how to resolve. |
Red |
031 |
Failed to load certificate(s). |
This warning message will appear if a card template is configured to import root and/or sub CA files or PKCS#12 files incorrectly. Tip: Make sure the instructions as described in the online help guides are followed when configuring import of root and/or sub CA files or PKCS#12 files. |
Yellow |
032 |
Issuance is not allowed because of short validity time. |
This warning message will appear if management of supported PIV cards are configured but a short expiration period is set. Tip: Go to the Options – PIV page and ensure that the selected signing certificate is valid for the configuration set. |
Yellow |
033 |
PIV smart card issuance is not possible. |
PIV smart card issuance is not possible. Tip: Make sure you have followed the online guides on how to configure PIV supported credentials in vSEC:CMS. |
Yellow |
034 |
PIV smart card issuance is not possible because of short validity time. |
PIV smart card issuance is not possible because of short validity time. Tip: Check that in the Issue Card section of the credential template that the expiration is not set to a short period. By default it is set to 1 year. |
Yellow |
035 |
Failed to initialize Operator Service Key Store. |
This error message will appear if the system fails to initialize Operator Service Key Store (OSKS). Tip: Activate the OSKS from Options – Operators page. |
Red |
036 |
Connection to Certification Authority (CA) has no Issuer DN configured. |
This warning will appear if there is no issuer DN configured for the CAs connection listed. Tip: Navigate to Options – Connections and select the CA template that is reported in the message and click the Edit button. Click the Get button and select the DN and click Ok. |
Yellow |
037 |
No CMS authentication keys configured for some operator cards. |
This warning message will appear if there are no authentication keys configured for the operator card(s) list. Tip: Attach the listed operator card and go to the Options – Operators page and click the Update Keys button to add. It will be necessary to have a key, such as a certificate, on the operator card to complete the update. |
Yellow |
038 |
Operator console server not configured. |
Operator console server has not been configured yet. Tip: Make sure to add a connector from Options – Connections page. |
Yellow |
039 |
Operator console server problem detected. |
This warning message will appear if the Operator console server is configured but not running. Tip: From Windows service ensure that vSEC:CMS – Operator Console Service is running. |
Yellow |
040 |
Requesting file export location during data export has been removed. |
This warning will appear if the Ask for file feature was configured previously for data export. This feature is no longer available therefore this message will appear only to inform the operator. |
Yellow |
041 |
No certificate request signing certificate(s) configured. |
This warning message will appear if there are no certificate request signing certificate(s) configured. Tip: Go to the Options – Operators page and click the Cert request signing button to configure. |
Yellow |
042 |
Configured certificate request signing certificate not found. |
This warning message will appear if the configured certificate request signing certificate was not found. Tip: Go to the Options – Operators page and click the Cert request signing button and ensure that the configured certificate is correct. |
Yellow |
043 |
Certificate request signing is not possible. |
Issuance of smart cards for the following template(s) is not allowed because the request signing certificate cannot be used. Tip: This is usually shown when Microsoft CA is used. Check your CA connection settings in the Enrollment Agent section. |
Yellow |
044 |
Certificate request signing is not possible because of short validity time. |
Issuance of smart cards for the following template(s) is not allowed because of short validity time of the request signing certificate. Tip: Go to the Options – Operators page and click the Cert request signing button and ensure that the configuration settings are correct. |
Yellow |
045 |
Only one (1) system owner. |
This warning message will appear if there is just one operator with the system administrator role configured on the system. If this operator card is lost, destroyed or broken, there is no operator with access rights to assign a new one and therefore the only recovery procedure then is to do a system backup restore. Tip: Add an additional operator token with system administrator role to the system. |
Yellow |
046 |
Template ID's not unique. |
If a card template(s) ID(s) are not unique this error message will appear. Tip: Contact Versasec if this message appears for details on how to resolve. |
Red |
047 |
A problem with the database has been detected. |
A problem with the specific used database tables has been detected. Tip: Open a Support ticket with Versasec if this should appear. |
Red |
048 |
A problem with the database has been detected. |
Specific used database tables have been set to read only. Tip: Open a Support ticket with Versasec if this should appear. |
Red |
049 |
Automatic backup did fail. |
The automatic backup failed. Tip: You should see additional details as to why the backup failed. Normally this is a Windows permission issue. The vSEC:CMS service is performing the backup so check that the service account has appropriate permissions to create and write the backup to the location configured. |
Red |
050 |
API server not configured. |
API server has not been configured yet. Tip: Add the connector from Options – Connections page. |
Yellow |
051 |
API server problem detected. |
API server is configured but not running. Tip: Make sure that the Windows service vSEC:CMS - API Service is running on the server where vSEC:CMS is running. |
Yellow |
052 |
Index in certificate expiration table is corrupt. |
The system has detected that the index in the certificate expiration table needs to be rebuilt. Tip: Open a Support ticket with Versasec if this should appear. |
Red |
053 |
Client console version does not correspond with server version. |
The client console version that you are running is different from the server version. It is recommended to update the client console version. Tip: It is recommended that the vSEC:CMS client components should be the same version as the server-side. |
Yellow |
054 |
Problem with CA template configuration. |
A problem with the template configuration at the CA has been detected. Some template(s) are not working correctly. Tip: Additional information should be shown in the dialog to help understand what is the root cause. |
Yellow |
055 |
Failed to initialize HSM connector. |
Failed to initialize the HSM connector while starting the service. This may impact the functionality of the system. Tip: You should resolve this as this will impact the system from functioning correctly. If it is not an obvious issue to resolve then open a Support ticket with Versasec. |
Red |
056 |
Problem with configuration of a variable. |
A problem with the configuration of a variable has been detected. Tip: check that the variable is configured correctly. |
Red |
057 |
Problem with local configuration cache has been detected. |
A problem with local configuration cache has been detected. The cache has been deactivated. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Yellow |
058 |
Remote secure device management server not configured. |
Remote secure device management server has not been configured yet. Tip: Add the connector from Options – Connections page. |
Yellow |
059 |
Remote secure device management server problem detected. |
Remote secure device management server is configured but not running. Tip: Make sure that the Windows service vSEC:CMS - RSDM Service is running on the server where vSEC:CMS is running. |
Yellow |
060 |
Problem with exclusive access locking has been detected. |
Thread already requested shared access and is not trying to get exclusive access to SRW lock. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
061 |
Problems(s) occurred during application startup. |
Some problems occurred during application startup. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
062 |
API authentication failed. |
API authentication failed. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
063 |
API server security warning. |
API server is configured to use authentication tickets, but no SSL is enabled to encrypt the transport. Tip: From Options – Connections make sure that in the API Service that SSL is enabled. |
Yellow |
064 |
Problems(s) occurred during SQL write. |
A problem has been detected during SQL write operations. Please raise a support ticket if this error is reported. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
065 |
Failed to load card applications configuration. |
A problem has been detected when loading the smart card application configuration file. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
066 |
Failed to load card applications configuration. |
A problem has been detected when loading the card application configuration file. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Yellow |
067 |
Database schema version is newer than the application does support. |
The schema version of the database is x.x.x but the application does only support x.x.x.Please consider to upgrade your CMS application. Tip: You should always update the schema version. |
Yellow |
068 |
Database schema needs to be updated. |
The schema version of the database is x.x.x but the application does support x.x.x. Please consider to perform a schema upgrade on your database. Tip: You should always update the schema version. |
Yellow |
069 |
This is reserved for internal use. |
Internal use for load balancing heartbeat therefore this would never be reported in the Admin console. |
|
070 |
HSM Failure |
An error has occurred when accessing the HSM. Tip: You should resolve this as this will impact the system from functioning correctly. If it is not an obvious issue to resolve then open a Support ticket with Versasec. |
Red |
071 |
HSM Down |
HSM is currently not available. Tip: You should resolve this as this will impact the system from functioning correctly. If it is not an obvious issue to resolve then open a Support ticket with Versasec. |
Red |
072 |
FASN-Numbers not functional |
The PIV-FASCN number generator is not functional. Tip: If you are using this feature when issuing and managing your PIV credentials then open a Support ticket with Versasec. |
Red |
073 |
FASN-Numbers low on free numbers |
Only a few PIV-FASCN numbers left to be used. Tip: If you are using this feature when issuing and managing your PIV credentials then open a Support ticket with Versasec. |
Yellow |
074 |
HSM has invalid key or no valid key |
The HSM key used by the system is either invalid or could not be found. Tip: You should resolve this as this will impact the system from functioning correctly. If it is not an obvious issue to resolve then open a Support ticket with Versasec. |
Red |
075 |
Failed to export TPM endorsement key certificate |
Failed to export TPM endorsement key certificate. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
076 |
Failed to import TPM info |
Failed to import TPM information. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
077 |
RSDM: Device registration failed |
Failed to verify the host UUID when attempting to register the host with vSEC:CMS. Tip: See the article here for more details on this. |
Red |
078 |
RSDM: Device registration failed |
Failed to check the host UUID when attempting to register the host with vSEC:CMS as the UUID was not initialised. Tip: See the article here for more details on this. |
Red |
079 |
RSDM: UUID check not initialized |
Failed to check the host UUID when attempting to register the host with vSEC:CMS as the UUID was not initialised. Tip: See the article here for more details on this. |
Red |
080 |
Application security warning |
Read access to seed backup is enabled for client applications. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Yellow |
081 |
Failed to import vSEC:CMS software version information |
It was not possible to import the vSEC:CMS software version information. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
082 |
Failed to initialize HSM connection |
An error occurred when attempting to initialise the HSM connection. The Key Check Value (KVC) check failed during the HSM initialisation. Tip: You should resolve this as this will impact the system from functioning correctly. If it is not an obvious issue to resolve then open a Support ticket with Versasec. |
Red |
083 |
Security vulnerabilities detected |
vSEC:CMS has detected some security vulnerabilities. It is highly recommended that these are looked into and resolved. At minimum you should open a support ticket with Versasec. Tip: You should resolve this as this will impact the system from functioning correctly. If it is not an obvious issue to resolve then open a Support ticket with Versasec. |
Red |
084 |
License expired |
Your current subscription license has expired. Tip: Contact your vSEC:CMS provider ASAP to resolve. |
Yellow |
085 |
License invalid |
Your current license is invalid. Tip: Contact your vSEC:CMS provider ASAP to resolve. |
Red |
086 |
Failed to request license or subscription |
It was not possible to get license information from vSEC:CMS online licensing service. Tip: You should resolve this as this will impact the system from functioning correctly. If it is not an obvious issue to resolve then open a Support ticket with Versasec. |
|
087 |
Configured server certificate not found |
Problems have been found with the currently configured TLS certificate. Tip: You should resolve this as this will impact the system from functioning correctly. If it is not an obvious issue to resolve then open a Support ticket with Versasec. |
Red |
088 |
Configured server certificate is not functional |
The currently configured TLS certificate has expired. Tip: See the article here on how to update. |
Yellow |
089 |
Configured server certificate has a short validity time |
The currently configured TLS certificate will expire soon. Tip: See the article here on how to update. |
Yellow |
090 |
RSDM: Primary user check not initialized |
Failed to initialize for primary user check. Tip: You should resolve this as this will impact the system from functioning correctly. If it is not an obvious issue to resolve then open a Support ticket with Versasec. |
Red |
091 |
RSDM: Primary user check failed |
Computer check for primary user failed. Tip: You should resolve this as this will impact the system from functioning correctly. If it is not an obvious issue to resolve then open a Support ticket with Versasec. |
Red |
092 |
<reserved> |
<reserved for future use> |
|
093 |
System is unprotected |
The current system is not protected with a passcode. Tip: Set a passcode to secure access to the Admin console. |
Yellow |
094 |
Weak admin key warning |
Some managed user credentials are having a weak admin key loaded. Tip: Update these credentials to ensure that the latest master key is used. |
Yellow |
095 |
vSEC:CMS SQL database is down |
The SQL database used by vSEC:CMS is not available. Tip: You should resolve this as this will impact the system from functioning correctly. If it is not an obvious issue to resolve then open a Support ticket with Versasec. |
Red |
096 |
<reserved> |
<reserved for future use> |
|
097 |
<reserved> |
<reserved for future use> |
|
098 |
<reserved> |
<reserved for future use> |
|
099 |
<reserved> |
<reserved for future use> |
|
100 |
A database schema mismatch has been detected. The database schema needs to be updated |
The schema version of the database and the application differs. It is recommended to perform a schema upgrade on your database. Tip: You should always update the schema, therefore perform the schema update. |
Red |
101 |
Database cache is not functional |
The vSEC:CMS database cache is currently not functional. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
102 |
<reserved> |
<reserved for future use> |
|
103 |
<reserved> |
<reserved for future use> |
|
104 |
<reserved> |
<reserved for future use> |
|
105 |
<reserved> |
<reserved for future use> |
|
106 |
<reserved> |
<reserved for future use> |
|
107 |
Security vulnerabilities detected |
Virtual smart card (VSC) DEBUG features are enabled for self-service consoles. This would allow EVERY user on devices where the feature is shown to create/destroy VSC's. Tip: This should not be enabled in a production environment. Open a Support ticket if you see this warning. |
Yellow |
108 |
External scripts not found |
The following external scripts have been configured in vSEC:CMS but they do not exist. Tip: Check what script it complains about and correct accordingly. |
Red |
109 |
<reserved> |
<reserved for future use> |
|
110 |
System Owner card needs updates |
Update(s) are required to be performed on the System Owner card. Tip: Perform the on-screen steps to update the SO credential. |
Yellow |
111 |
Missing master key checksum(s) |
No checksum data found in database for the following Masterkeys: Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Yellow |
112 |
Critical exception detected |
A critical exception has been detected. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
113 |
Critical exception detected on the server |
A critical exception has been detected on vSEC:CMS server. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
114 |
A problem in HSM key store has been detected |
The HSM middleware (PKCS#11) has returned an error. Tip: Details have been sent to the Windows event system. |
Red |
115 |
Missing fields detected (key archive-guid) |
Some user entries in the key archive do not have the GUID set. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Yellow |
116 |
Failed to load configured LDAP plugin |
Failed to load configured LDAP plugin. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
117 |
Failed to detect RFID only card |
Failed to read serial number. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
118 |
Failed to detect RFID only card |
Card with this ATR is not supported. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
119 |
No encryption key available |
There is no encryption key available to encrypt/decrypt data in the database. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
120 |
Invalid DB data encryption key detected |
DB data encryption key test failed. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
121 |
Critical exception reported in database |
Critical exception(s) has been reported to the vSEC:CMS database. A process dump has been generated and stored: Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
122 |
<reserved> |
<reserved for future use> |
|
123 |
Possible improvements in SQL implementation detected (Server side) |
Some improvements in the SQL implementation has been detected (Server side). |
Yellow |
124 |
Possible improvements in SQL implementation detected (Client side) |
Some improvements in the SQL implementation has been detected (Client side). |
Yellow |
125 |
A problem with the resource lock management has been detected |
The following problem with the resource lock management has been detected Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
126 |
A problem with the SQlite database has been detected |
The SQlite file might be corrupted. The database consistency check failed. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
127 |
A problem with the SQlite database has been detected |
The SQlite file is corrupted (the database disk image is malformed). The following problems have been found Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
128 |
Unauthorized PIN unblock requests have been detected |
The CmsService blocked unauthorized requests to PIN unblock codes. Tip: This should not happen but if you do see this please open a Support ticket with Versasec. |
Red |
129 |
<reserved> |
<reserved for future use> |
|
130 |
<reserved> |
<reserved for future use> |
|
131 |
<reserved> |
<reserved for future use> |
|
132 |
<reserved> |
<reserved for future use> |
|
133 |
<reserved> |
<reserved for future use> |
|
134 |
Custom data is existing in the [cards] table while the feature is turned off |
The feature: "Store Custom Data in vSEC:CMS database [cards] table" is not enabled but there is still data stored in some entries. This has no impact on the system behaviour but might be relevant for privacy/data security reasons. Tip: Check the details reported and if it is not clear why this is being reported open a Support ticket with Versasec. |
Yellow |
135 |
Custom data in the [cards] table are potentially old |
The system is configured to store (and synchronize) custom data in the vSEC:CMS [cards] table. A number of entries have not been synchronized for some time. This can have an impact on the system behaviour. Tip: Check the details reported and if it is not clear why this is being reported open a Support ticket with Versasec. |
Yellow |
136 |
No scheduler available to synchronize custom data in the [cards] table |
The feature: "Store Custom Data in vSEC:CMS database [cards] table" is not enabled and configured to synchronize the data with the external source(s). The scheduler to perform the synchronization is either not enabled or no scheduler is configured. Tip: Go to Options - Scheduler and configure Synchronize custom cards data entry. |
Yellow |
137 |
<reserved> |
<reserved for future use> |
|
138 |
<reserved> |
<reserved for future use> |
|
139 |
<reserved> |
<reserved for future use> |
|
140 |
<reserved> |
<reserved for future use> |
|
141 |
Failed to initialize Operator Service Key Store |
Failed to initialize Operator Service Key Store. Tip: You should resolve this as this will impact the system from functioning correctly. If it is not an obvious issue to resolve then open a Support ticket with Versasec. |
Red |
142 |
Problem with a template configuration has been detected |
Invalid user DN has been detected. Tip: Additional details should be shown but if it is not possible to resolve from the details shown then open a Support ticket with Versasec. |
Red |
143 |
Operator Service Key Store is using an invalid masterkey |
Operator Service Key Store is using an invalid masterkey. Tip: You should resolve this as this will impact the system from functioning correctly. If it is not an obvious issue to resolve then open a Support ticket with Versasec. |
Yellow |
144 |
An invalid masterkey has been used |
Usage of an invalid master key has been detected. Tip: You should resolve this as this will impact the system from functioning correctly. If it is not an obvious issue to resolve then open a Support ticket with Versasec. |
Yellow |
145 |
No scheduler available to maintain data in the [tmp_ad_pwd] table |
The feature: 'Domain password reset via user self-service' is enabled, configured and used. The scheduler to maintain the the data is either not enabled or no scheduler is configured. Tip: Go to Options - Scheduler and configure AD password reset tasks entry. |
Yellow |
146 |
<reserved> |
<reserved for future use> |
|
147 |
<reserved> |
<reserved for future use> |
|
148 |
Problem with a template configuration has been detected |
Invalid AD Group DN has been detected. Tip: Additional details should be shown but if it is not possible to resolve from the details shown then open a Support ticket with Versasec. |
Yellow |