Applicable Systems
Wonderware System Platform
Symptoms
The Wonderware System Platform reports that the alarm service has stopped. New alarms are not being generated or displayed in the alarm summary, leaving operators without real-time alarm visibility.
Possible Causes
- The Alarm object engine crashed due to an unhandled exception in a custom alarm provider
- The alarm database is locked or corrupted, preventing the alarm service from reading or writing
- The Windows service account running the alarm engine lacks permissions after a domain policy change
Troubleshooting Steps
- Step 1: Check the alarm engine status in the SMC System Management Console
Alarm engine shows Running status with no fatal errors in the last 10 minutes - Step 2: Test the alarm database by running a manual alarm query
Database responds to the query within 2 seconds and returns expected alarm records - Step 3: Verify the Windows service account permissions on the alarm database and Galaxy objects
Account has db_owner role on the alarm database and Full Control on the Galaxy folder
How to Reset
To reset: 1) Restart the alarm engine from the SMC console. 2) Repair or unlock the alarm database. 3) Restore service account permissions. 4) Verify alarms appear in the summary within 30 seconds.
Source: Wonderware System Platform Manual, AVEVA (formerly Wonderware)
Category: SCADA