Error when alarm appears

[funkey]

On my system I got an error every time an alarm appears.

Code: Select all

WCCILevent   (0), 2013.10.21 11:20:32.960, PARAM,SEVERE,     23, Setting/modifying attributes failed, DP: System1:example_error_dp.:_alert_hdl.._ack_state, MAN: (SYS: 1 Ui -num 7 CONN: 1(R)), USER: 2

Everything works fine, I just want to know what this means for me and how to get rid of this message?


Thanks for every useful answer.

Best regards.

[leoknipp]

Hello,

I had a look at our internal database, the log-message appeared several times when modifying alerts.
There have been made some bugfixes with a relationship to this log-message.

Please give us detailed information which WinCC OA version you are using and which patches are installed.

Best Regards
Leopold Knipp
Senior Support Specialist

[funkey]

Hello,
thanks for your answer. We use V3.11 SP1 and patch 16 I think (patch 19 is not installed till now). We have two redundant servers and about ten clients. I would have put this infos to my signature, but I did not find it in this forum.
I'm sure I have this error log since V3.6 or at least V3.9, but now I have a little time, so I want to get rid of some error logs.

Best regards
Christoph Fankhauser

[leoknipp]

Hello,

I found a possible cause for this log-message.
Most of the time the log-message occurs when the following conditions are met:
-- the referenced alert class at the given dp-element uses the acknowledge type “CAME and WENT must be acknowledged seperately”
-- at the alarm list for the AEScreen the CAME alert is displayed in a line which is not visible at the moment
-- at the alarm list for the AEScreen the WENT alert is displayed in a line which is visible at the moment
-- the user has called the commonConfirm function for the module where the AEScreen is displayed

In this case only the visible alerts will be acknowledged. The WENT alert cannot be acknowledged as you have to acknowledge the CAME alert first. For the WENT alert the log-message is written.


Please check if this could be an explanation for the log-message in your project.

Best Regards
Leopold Knipp
Senior Support Specialist

[funkey]

Thanks for looking after it.
We use "CAME or WENT has to be acknowledged". I think the error appears, when users are acknowledging very fast. They just click a lot of times for every alarm in the list.

[funkey]

Hello,
now with V3.13 I still get the same error messages. I tried everything to get rid of of them, but no success!

[funkey]

https://www.winccoa.com/fileadmin/image ... _Error.png Can please anybody tell me what is wrong configured? I attached an image to let you see my configuration.

[leoknipp]

Hello,

when does this log-message occur exactly?
When the alert is raised?
When trying to acknowledge the alert?

Best Regards
Leopold Knipp
Senior Support Specialist

[funkey]

Thanks for your answer. The error occurs when trying to acknowledge the alert. But not always.

[fmulder]

I'd advise you to start your GUI with '-snd 2'. You can then see exactly what alarms are being acknowledged in the LogViewer. It is not easy but I can imagine that the AES panel is trying to acknowledge in the wrong order.

good luck

Frenk