"Object not found" service provider alarms are apperaing in the sys alarm list
Some of the system objects not the CBM objects are exist in the system alarm list but we are unable to find those objects by their GUID.We tried to delete them & they gets deleted & they will come back again on restart of the aspect servers, Even we tried to stop the alarm manager & restarted again but still the problem remains.
if you look at the system alarm list where the object name start with GUID along with that there is one more object controller_1 is also not defined in the CBM but still this also exist in the system alarm list.
System version:800xA5.1 RevC
Observations:Nothing is found in the Lost & found object.
How to delete those nuisance alarms
The Object Description "Object not found in the system" gives perfect explanation to why the alarm and event lists show GUIDs instead of names. Internally, all alarm and events are handled by their object GUID. If the object is deleted, we loose track of what it was called and fall back on GUID. Names are sometimes cached and presentation of GUID may be delayed until cache is expired or client has restarted.
Next find out the Category for the nuisance alarm.
The category will tell you where to go next. Each OPC AE server emits alarm and events on well known categories which can be looked up among the Alarm Collection Definitions objects and aspects in the Library Structure.
"System Alarm for Softalarms" belong to the SoftAlarm OPC AE Server and are generated by Alarm Expression aspects. Some come with the system per default while others may belong to some application library or be custom made by some application engineers, etc.
The message "Service Provider not in Operational State" points to that the alarm belonged to a service provider in the Service Structure, but that the service object has been deleted (e.g. by Configuration Wizard->Remove Server or manipulation of services, groups or providers in Plant Explorer, etc.).
I think we can rather safely conclude that you are troubled by alarms from deleted service provider objects.
Why does "Delete Alarm..." on context menu or restart of Alarm Manager, Event Collector and SoftAlarm Services not help then?
-> Most alarm categories can be refreshed from the Event Collector and OPC AE Server (some OPC AE servers, e.g. 800xA for Advant Master does NOT support refresh).
The delete is only "skin deep" - alarm will still exist in Event Collector and OPC AE server waiting to be refreshed.
Also the Soft Alarm OPC AE Server supports refresh - internally it is storing alarm conditions in a disk based cache file (alarms will remain between reboots).
I suggest that you "cold start" the SoftAlarm service by:
a) Stopping it in parallel on all aspect servers (Alarm Expressions will go lost!)
b) Deleting the disk cache "\OperateITData\SoftAlarms\SomeGUID\*.*"
c) Restart the SoftAlarm Service
Please note the side effect of the above cold restart: Both active & unacknowledged and active & acknowleded alarm expression based alarms will fire again with new active time.
Older alarms in "inactive, unacknowledged" state will unfortunately go lost, but you can still view them as events in event lists.
If the alarm should come from a controller, you must ensure that the object configuration in the 800xA system is perfectly mapping the object configuration in the controller. E.g. a missing upload or download may be the root cause. Synchronize the two worlds, delete the objects below the Lost and Found folder, delete alarms from alarm lists (if still lingering) and try again.