Connection to server failed – socket connection aborted - CCURE Access Control 3.8.0

CCURE 9000 Access Control Plugin Guide 3.8.0
Product
CCURE 9000 Access Control
Content type
Guides > Plugin and extension guides
Version
3.8
Release
3.8.0
Language
English
Last updated
2023-10-10

If you receive a Connection to server failed message for the CCURE 9000 Access Control plugin role in Config Tool, there are several ways you can troubleshoot the issue.

Symptom

The proxy service is not running on the CCURE 9000 server.

You receive the following error message:
Code 
Connection to server failed
 net.tcp://nnn.nnn.nnn.nnn:nnnn/Genetec/CCUREAccessControl
A screen shot of the Diagnostic window in Config Tool showing the error message.

The proxy service is not running on the CCURE 9000 server

Cause: A required service is not running on the server.

Solution:
  1. Log on to the CCURE 9000 server as an administrator.
  2. Open the MS Windows Services MMC.
  3. Make sure that the CCURE 9000 proxy service is running. If it is not, start it.
  4. Make sure that the CCURE 9000 CrossFire services are running. For details refer to your CCURE 9000 documentation. If any services are not running, start them.
  5. Verify the transport encryption settings:
    • Make sure that the password in the plugin matches the password on the proxy.
    • Make sure that the certificate is valid.

The configurations of the proxy service and the plugin do not match

Cause: The proxy service runs on the CCURE 9000 server. The plugin runs on a Security Center server. To enable encryption, you modify a configuration file on the CCURE 9000 server and another configuration file on the plugin server. If one configuration file has encryption enabled, and the other file has encryption disabled, you get this error message.

Solution: Follow the instructions in the Enabling encryption chapter, and ensure that the encryption status in the configuration files for the plugin server and the proxy server match.

A configuration file contains incorrect syntax

Cause: When encryption was enabled or disabled, an error was accidentally introduced in one or both configuration files.

Solution: Referring to the instructions and examples in the Enabling encryption chapter, open each configuration file and verify that all tags are closed, and all syntax is correct.

The network is blocking the communications port used by the plugin

Cause: A device on the network is configured to block the communications port that the plugin and proxy service are configured to use.

Solution: Make sure that the communications port used by the plugin and proxy service is open on your network routers, switches, and Windows firewalls.