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:
- Make sure that the server is set up according to the Security Center specifications.
- 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 software, if required.
- 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.
- If yes: Your SQL server or installation might be corrupted. To make sure your system is fully repaired, reinstall Security Center.
- If no: Continue troubleshooting your main server by checking the next possible cause.