Sigma Server crashes and the hard drive has filled with archived Alarm Logs.

[Product_Support]

Issue

Sigma Server crashes, and the hard drive becomes full due to an accumulation of archived Alarm Logs, all timestamped around the same time. Alarm Fail Safe window displays:

• "Logging Database is 100% full"
• "Unable to archive"

Product Line

Satchwell BAS & Sigma

Environment

Satchwell Sigma

Cause

The Sigma Server crashes because the Logging Database is full. Normally, this database is automatically archived. However, if the folder C:\Sigma\Data\ArchivedLogs is missing, the archiving process fails repeatedly. Each failed attempt generates a System Message, which further fills the Alarm Log Database, triggering another archiving attempt—creating a loop that eventually crashes the server.

Resolution

Step 1: Recreate Missing Folders

Ensure the following folders exist under C:\Sigma\Data. If not, manually recreate them:

• ArchivedAlarms
• ArchivedLogs
• ArchivedTransactions

  

Step 2: Test Archiving Functionality

1. Create an Action and Schedule to archive the logs.
2. Allow the schedule to run.
3. Verify that a file named Sigma0nnnn.dbs appears in the ArchivedLogs folder.

✅ If successful, you may either remove the daily schedule or leave it in place for ongoing archiving.