Skip to main content
Skip table of contents

How Can I Troubleshoot an Syteca Client if it is Displayed as Offline?


In the event that any (or all) Syteca Clients are displayed as being offline on the Client Management page, this may be for many possible reasons, but the main issues (i.e. causes) and possible solutions are as follows:


Issue:

The Client was uninstalled from an endpoint computer, but its data is still displayed in the system.

The Client also needs to be deleted in the Management Tool (after uninstalling it using either a remote or local method of uninstallation), after which the Client will no longer be displayed in the Management Tool, and all data associated with the Client is deleted.


Issue:

Isolation mode was enabled on Syteca Application Server.

Disable Isolation mode.


Issue:

The computer where the Syteca Client is installed is turned off.

Turn the Client computer on.


Issue:

There is a network issue (i.e. no connection) between the Client and the Application Server.

The network problems need to be fixed.


Issue:

The port for communication between the Client and the Application Server machines is blocked by a software firewall or hardware firewall.

Either disable the firewall, or allow it to open the connection port (which by default is 9447).


Issue:

The EkranClient service is stopped, or does not start automatically on the endpoint machine.

Start the EkranClient service manually, and check that all the required files are located in the Ekran Client root folder (i.e. the folder where the Syteca Client application is installed), or otherwise reinstall the Client.


Issue:

The Syteca Application Server machine has a new IP address / hostname or port, and all the Clients are trying to connect to the Application Server using the old settings. 

Either re-install all the Clients using a remote or local method of installation, or modify their settings in the appropriate files (see Points 3-5).


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.