Archiver database is not connected - Security Center 5.8 - 5.12

Troubleshooting the Archiver
Product
Security Center
Content type
Troubleshooting
Version
5.12
5.11
5.10
5.9
5.8
Language
English
Last updated
2024-09-03

If the Archiver database is not connected, check whether you have sufficient access rights. To help you troubleshoot this issue, learn about its possible causes and their respective solutions.

Missing permissions

Description of cause: The Genetec Service logon user does not have the necessary rights on the Archiver database in SQL.

Solution: To check this, open SQL Management Studio and do the following:
  1. Click Security > Logins > [Right-click the user] > Properties.
  2. Click Server roles and check that all server-level roles for the Archiver are selected.
    SQL Management Studio showing the server-level user permissions for the Archiver database.
  3. Click User mapping, select Archiver, and check that all database-level roles for the Archiver are selected.
    SQL Management Studio showing the database-level user permissions for the Archiver database.
For more information on the required permissions, see the basic administrative privileges.

Archiver database is full

Description of cause: The Archiver database has reached its size limit. In SQL Server 2008 Express and later, the size limit is 10 GB.

Solution: Upgrade SQL Server Express to the Standard or Enterprise editions. As a workaround, you can do the following:
  • Create a new database
  • Reduce the retention period of the recordings
  • Contact tech support to help you determine why the database has reached its storage limit
NOTE: Databases can suddenly fill up due to cameras sending too many events. You can have the system monitor incoming camera events to help detect when an unusually high number of events are being received. For more information, see Archiver: Resources tab.

Database transaction log is too big

Description of cause: The transaction log file (LDF) of the SQL database is too big. The LDF should not be bigger than the main data file (MDF).

Solution: In SQL Management Studio, do the following:
  1. Switch the recovery model of the database to Simple.
  2. Shrink the transaction log file.
  3. Set a maximum size limit for the transaction log file.

Remote database ports are not open

Description of cause: The remote database ports, TCP 1433 and UDP 1434, are not open or they are being used by other applications and causing conflicts.

Solution: Open the ports and make sure that they are reserved for the SQL Server.

Parent topic: Troubleshooting the Archiver
Browse