Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance.
Many alarms showing up during site commissioning for controllers that were not configured properly. Some duplicate id's and controller offline alarms for controllers that are no longer online and the alarms can't be removed.
- Enterprise Server
- Automation Server
- SmartStruxure 1.3
Alarms are orphaned in the database and are not removed once the duplicate id issue is resolved.
The first thing to do is to attempt deleting the PersistedData.dat file (Lessons Learned Article #12070) and restarting the AS. If the orphaned alarms are still showing up then the next option is to completely clear the AS.
- Backup the AS, configuration only.
- Clear the AS and commission.
- Once it comes back up, restore the configuration.