Event Collector Service Providers randomly fail
I am working on a system (800xA 5.1) that has two pairs of redundant 800xA for DCI Connectivity Servers. What I am finding is that occasionally, the Event Collector Service on the providers goes into "Unknown" status (rather than "Service" or "Standby"). I checked the Windows Application Log, and shortly after the service is started I see the following Warning:
"AE Event Notification Error - No client connection point established ... may not be able to report outstanding active alarms/events." The Event Collector service will then run for anywhere from hours to weeks. This problem occurs on each of the four Connectivity Servers. This is usually remedied by disabling and re-enabling the service groups along with the service providers. Any thoughts on what might be causing this failure? Is there anything else that I might check to better understand or troubleshoot this? TIA

"AE Event Notification Error - No client connection point established ... may not be able to report outstanding active alarms/events." The Event Collector service will then run for anywhere from hours to weeks. This problem occurs on each of the four Connectivity Servers. This is usually remedied by disabling and re-enabling the service groups along with the service providers. Any thoughts on what might be causing this failure? Is there anything else that I might check to better understand or troubleshoot this? TIA

Answers
Please file a support case with your regional ABB support center asking for assistance with troubleshooting DCI.
The Event Collector service in System 800xA is periodically (every 5 seconds) calling the GetStatus() function of the OPC AE Server it is connecting. A negative answer or lack of answer will lead to termination & automated restart of the Event Collector.

The Event Collector service in System 800xA is periodically (every 5 seconds) calling the GetStatus() function of the OPC AE Server it is connecting. A negative answer or lack of answer will lead to termination & automated restart of the Event Collector.

Add new comment