Archiver database is not connected - If your Archiver database is not connected, ensure that your database has sufficient permissions, available file space, and open ports. To help you troubleshoot this issue, learn about its possible causes and their respective solutions. - Security Center 5.10 - 5.13 - Troubleshooting

Troubleshooting the Archiver
Product
Security Center
Content type
Troubleshooting
Version
5.13
5.12
5.11
5.10
ft:locale
en-US

If your Archiver database is not connected, ensure that your database has sufficient permissions, available file space, and open ports. 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 permissions 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 your recordings.
  • Contact tech support to determine why the database has reached its storage limit.
NOTE: Your database can unexpectedly fill up due to cameras sending too many events. You can set up your system to monitor when an unusually high number of events is 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.