Issue
It is possible that if you reboot a server when an active alarm is present, after the reboot you will see a new active alarm with the timestamp of the reboot (more correctly, the timestamp of the ION Software Alarm service restart) in addition to the alarm that was active prior to the reboot. Thus, the system will end up having two active alarms, rather than just the original one. When the alarm becomes inactive, only the new, incorrect alarm will go inactive. The original one will remain in an active state forever.
Product Line
Power Monitoring Expert 7.2.2
Power Monitoring Expert 8.2
Power Monitoring Expert 9.0
Power Monitoring Expert 2020
Power Monitoring Expert 2021
Power Monitoring Expert 2022
Power Monitoring Expert 2023
Environment
Web Application
Management Console
Cause
This can happen if SQL Server is slow to start, and the ION Software Alarm service starts first. The ION Software Alarm service should have a service dependency on SQL Server, which would prevent this problem.
Resolution
To create the service dependency, type the following in a command prompt:
- Open CMD as an administrator
- Copy the following script into the CMD and press "Enter"
sc config PMALARM depend="MSSQL$ION"
Alarms that are 'stuck' in an active state can be reset using the 'Deactivate Alarms
tool accessed via Management Console -> Tools -> Deactivate Alarms
For a more detailed how-to for deactivating alarms, please see Video: How to Deactivate Alarms in PME | Schneider Electric USA
