800XA 5.1 error

Hello,

We have a fail with 800XA 5.1 version, the problem is appears X over alarms indicators (please look the pictures attached),

all services are working fine and also OPC server is OK,

(as you see in the picture)

this problem is the result of one energy fail, and all computers off,

then we start computers again but appears this problem.

What could be the solution in this case?

if someone has any idea please, we will be grateful.

Comments (2) New comment

csanchez411 AKS expert

Rank: 14

Asked 4 years ago

Answer this question Follow

Answers

Whats revision of 5.1 you have? What about Rollups?

Is alarm manager service running healthy? its not shown in the picture you attached.

Check if Restarting Alarm manager service helps.

Comments (1) New comment

elemravi Rank: 42

Answered 4 years ago

Open the Alarm List that has the "X" indication. There should be a large circular Icon in the header that shows the status of the Alarm Services. Click that and check where the alarm list thinks the error is coming from.

The alarm band aspects can also show an "X" if they are configured to Count the number of Alarms but the List only contains Events.

Comments (0) New comment

Rob Lyon Rank: 2

Answered 4 years ago

You may be affected by a rarely occuring bug which causes the Alarm Manager to fail setting up proper subscriptions to all Event Collectors. When this happen; all A&E services will report "green" and everything looks OK on the outside (with exception for the orange border in alarm list/bands).

I suggest reporting this to your regional ABB support center for further action.

The bug can be verified with the AppLog tool: call the ListEventCollectorStatus operation and study the output carefully. If there is one (or more) Event Collectors reported as "Connected (Subscription *Inactive*)" you are affected. All Event Collectors with Connected/Inactive state must be toggled (stopped & started) for having another go with setting up a proper subscription. It is believed the problem may stem from loss of network packets, but no hard evidence have ever been found. Later revisions and feature packs have been made slightly more robust to prevent this rare phenomenon from occuring.

Comments (0) New comment