Potential faults

Potential installation faults

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
  • Make sure you logged in with the System administrator's name, password and name of the server where Master Node was installed.

or

  • connect from the browser with "https://<serverName>" or "https://<backendServerName>"
  • The browser inspects the HTTPS certificate and returns some addresses to find out what went wrong.
Possible server problems

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

  • check Master Node service status
  • request hardware key replacement.
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

  • check whether an update is in progress
  • check the Collector log file
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.

Potential backup problems

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 learn more

To check component status see "Component status check procedure".

To restart services see "Service restart procedures ".