Security Center Federation™ role is offline - Security Center 5.9 - 5.12

Troubleshooting Security Center Federation™

Security Center
Content type
Last updated

If the Security Center Federation™ role is offline (icon is red), it is likely a connection issue. To troubleshoot the issue, learn about the possible causes and their respective solutions.

Cause Description Solution
Server is offline If the Security Center Federation™ role is hosted on an expansion server, the server might be offline. To check the status of the server, open Config Tool, and then click System > Roles > [Your role] > Resources. In Windows Services, ensure that the Genetec Server service is running on that server. If the service is running, make sure that the expansion server has connected successfully to the Directory. If the server fails to start, troubleshoot the server issue.
Connection failed to federated system If the Security Center Federation™ role shows a Connection failed error message, there is a communication issue between the Federation™ host and the federated system. The ports for Security Center Federation™ might be closed or in use by other applications. Do the following:
  1. Ping the IP address of the remote server. Open a Windows Command Prompt and enter the following command: ping <IP address>.

    If you cannot communicate with the remote server, it might be offline. Troubleshoot the remote server.

  2. Use Telnet Client to confirm that communication between the servers is open using port 5500. On both servers, open a Windows Command Prompt and enter the following command: telnet <IP address> 5500 (<IP address> is the public address of the other server).
    NOTE: The port is configurable and might change.

    If necessary, open port 5500 on the public address of both servers and make sure that the port is redirected for firewall and NAT purposes.

  3. On the server hosting the Security Center Federation™ role, try connecting to the Directory of the federated system from Security Desk using the Federation™ user. If the user does not have the privilege to connect with Security Desk, you get the Insufficient privileges error.

    If you cannot connect to the Directory of the federated system, it is likely a network issue. Talk to your network administrator or see Configuring Security Center Federation™ across different networks.

Invalid credentials for Federation™ user If the Security Center Federation™ role shows an Invalid credentials error message, the wrong password was entered for the user that connects to the federated system. In Security Desk, try to connect to the Directory of the federated system using the Federation™ user account.

If you cannot connect, verify with the administrator of the federated system that you have the correct password for the user specified on the Properties tab of the Security Center Federation™ role. Try entering the password in Config Tool again.

Duplicate federated entities If you are federating more than one system and the same entity exists on both remote systems, you receive an error message in the Event Viewer logs due to a duplicate federated entity.
Example: Cardholder Ray exists on System A and System B. System C is already federating System A. If you start federating System B on System C, the Security Center Federation™ role goes offline when trying to synchronize cardholder Ray.
  1. In the Event Viewer logs, identify the duplicate entity.
  2. On one of the federated systems, add the duplicate entity to a partition that the Federation™ user is not a member of. To change partition settings, see Granting access rights for partitions.

    The duplicate entity can no longer be viewed by the Federation™ user, so the entity is not federated.