Following is a list of potential faults that may occur during installation and references to recommended actions:
If... | Then... |
---|---|
installation does not progress | make sure the hardware key is correctly inserted. |
RCS console cannot connect to the server |
or
|
Following is a list of potential faults that may occur during product use and references to recommended actions:
If | And | Then |
---|---|---|
cannot connect to Master Node |
the hardware key is correctly inserted but Master Node service does not start |
|
data no longer arrives from agents |
from RCS Console the Collector is running and correctly communicates |
check Collector status. |
The Master Node is not available |
The Collector is running |
|
images are not converted into text | the OCR module is installed | check how slow in the module log and install another OCR module (if in distributed architecture). |
The Collector is not available | - |
restart RCScollector service. |
data is queued in the Master Node | the most recent data does not appear on RCS |
check Worker service status for Master Node and for the other Shards. |
Network Controller indicates an error |
Connect to the machine where Network Injector or Anonymizer is installed and check the log file. |
Following is a list of potential faults that may occur during backup and references to recommended actions:
If | And | Then |
---|---|---|
backup status is error |
- |
check available disk space and manually restart backup. |
To check component status see "Component status check procedure"
To restart services See "Service restart procedures "
RCS8.2 | User's and Installation Guide | © COPYRIGHT 2012