Troubleshooting the main server in Security Center - Security Center 5.5 - 5.10

Applies to
Security Center 5.5 - 5.10
Last updated
2021-08-05
Content type
Troubleshooting topics
Language
English (United States)
Product line
Security Center unified platform > Security Center
Version
5.10
5.9
5.8
5.7
5.6
5.5
ContentOps
ContentSolution

Main server is offline

If your Security Center clients are not connecting, your main server might be offline. Ask the following troubleshooting questions to determine a possible cause and solution.

NOTE: To help guide you through the troubleshooting process, you can also use this questionnaire.

Is your license up to date?

In Server Admin, check whether the License is still valid (green).

  • If yes: Go to the next question.
  • If no: Contact Customer Service to obtain and activate a new license.

Is the Genetec™ Server service started on the server?

In the Windows Services console, check whether the Genetec™ Server service is Running.

Does the Genetec™ Server service logon user have full user permissions on the database and on Windows?

On the Genetec™ Server, verify that you can log in to your SQL server using SQL Management Studio. You can also check your user permissions with your IT department.

  • If yes: Go to the next question.
  • If no: Obtain full user permissions and restart the Genetec™ Server service. If the server does not come online, go to the next question.

Is the Directory role started on the server?

In the Server Admin, check whether the Directory is online (green).

  • If yes: Go to the next question.
  • If no: In Server Admin, try to start the Directory. If the Directory does not start and the server does not come online, troubleshoot the Directory role.

Are your ports open?

Check with your IT department that the ports for server communication are open and are not being used by another process. You can also run the Command Prompt and enter the command line netstat -na | find"[PortNumber]" to check whether a port is open.

  • If yes: Go to the next question.
  • If no: Open the correct ports. See the list of default Security Center ports. If the server does not come online, go to the next question.

Was there a Windows event that caused the service to stop?

Check the Windows event logs or dump files for strange events or errors. To check the Windows logs, open the command prompt as administrator and enter the following command: eventvwr.msc. Make sure to check application, system, and Genetec event logs. To check whether dump files have been created, open C:\Program Data\Genetec Security Center [5.x], and then open the Dumps or Logs folders.

Genetec™ Server service is stopped

If the Genetec™ Server service is not running on the server and your server is offline, ask the following troubleshooting questions to determine a possible cause and solution.

Did the Genetec™ Server service account have a logon failure?

In the Windows Services console, try starting the Genetec™ Server service.

  • If yes: From the Computer Management console, right-click the service account in the Users folder, reset the account password, and try starting the service again. If you have insufficient privileges, contact your administrator.
  • If no: Go to the next question.

Is your server running out of CPU or memory?

In the Performance tab of the Task Manager, check the CPU and memory usage. The server might be overloaded.

  • If yes: Do the following:
    1. Make sure the server is set up according to the Security Center specifications.
    2. Investigate processes and applications that use the most CPU or consume excessive amounts of physical memory (RAM). Consult the vendors of the respective applications or softwares, if required.
    3. Close all unwanted applications that might affect CPU and RAM usage.
  • If no: Go to the next question.

Is your server running out of disk space?

In Windows, check the amount of space available on the C drive. Low disk space can have negative effects on your server's performance and cause processes to falter or fail.

  • If yes: Free up disk space on the server's C drive and restart the Genetec™ Server Service. If the server comes online, monitor your disk space going forward. If the server does not come online, go to the next question.
  • If no: Go to the next question.

Was there a power outage or any recent Windows updates that caused the server to restart unexpectedly?

In Windows Event Viewer, check the Application and System event logs for Event ID 41: The system has rebooted without cleanly shutting down first.

Directory role is offline

If the Directory role is stopped and your server is offline, ask the following troubleshooting questions to determine a possible cause and solution.

Is your Directory database connected and communicating properly?

In the Server Admin, check whether the Directory database status indicates OK (green).

Is it a license issue?

In Config Tool, check for license errors in the About page.

  • If yes: Modify your system configuration (requires a Directory restart) or update your license.
  • If no: Go to the next question.

Is it a certificate issue?

In your server page on Server Admin, check the Secure communication section to see if your certificate has expired.

  • If yes: Replace your certificate, then restart the Genetec™ Server service.
  • If no: Go to the next question.

Is the timestamp of your server incorrect?

Check whether the date and time of your Windows system are correct.

Directory database is disconnected

If the Directory database of your main server is disconnected (red or yellow) and not communicating properly, ask the following troubleshooting questions to determine a possible cause and solution.

Is the database local?

On the main server page in Server Admin, check whether the name of the Database server indicates that the SQL Server is local.

  • If yes: In the Windows Services console, restart the SQL Server service. If the Directory does not start and the server does not come online, go to the next question.
  • If no: Try the following:
    • Ensure that the server running SQL service is online. You can check this by logging in to that server using Remote Desktop or SQL Management Studio.
    • Instead of connecting to the remote database server using the SQL Server instance name, open Server Admin and try connecting using the server's IP address.
    • Ensure that the remote database server ports (TCP 1434 or UDP 1433) are open and reserved for the SQL Server. They should not be used by another application.
    If the database does not connect and the Directory and server do not come online, go to the next question.

Is the database version incompatible?

On the main server page in Server Admin, check the Status section for the following error: Database version is higher than the current version.

Does the user that is running the Genetec™ Server service have permission to access the Directory database?

The Genetec™ Server logon user might be missing SysAdmin rights on the Directory database in SQL. To check this, open SQL Management Studio, click Security > Logins > [Right-click on the user] > Properties > Server roles, and then select public and sysadmin.

  • If yes: Go to the next question.
  • If no: In SQL Server Management Studio, add the SysAdmin server role to the user who is running the Genetec™ Server service. If you cannot grant SysAdmin permissions to the user, grant the basic administrative privileges. If the database does not connect and the Directory and server do not come online, go to the next question.

Is the Directory database full?

In SQL Server Management Studio, click Server Explorer > Right-click on Database > Properties > General, and check whether the Directory database has reached its size limit. The size limit in SQL Server 2005 Express is 4 GB; the size limit in SQL Server 2008 Express and later is 10 GB.