WCCILevent - PARAM/SEVERE - Setting/modifying attributes failed "DPE-ID":_alert_hdl.._ack_state
Enclosed you'll find the explanation for a log-message which can occur during runtime. The log-message is written to the PVSS_II.log-file.
WCCILevent (0), 2013.11.11 14:42:23.018, PARAM,SEVERE, 23, Setting/modifying attributes failed, DP: System1:PUMP1.failure.engine.:_alert_hdl.._ack_state, MAN: (SYS: 1 Ui -num 1 CONN: 1), USER: 0
Log-message with symbolic names:
WCCILevent (0), <TIMESTAMP>, PARAM,SEVERE, 23, Setting/modifying attributes failed, DP: <system name>:<DPE-ID>:_alert_hdl.._ack_state, MAN: (SYS: <system number> <manager type> -num <manager number> CONN: <connection ID>), USER: <user ID>
This log-message describe that the acknowledge state for the alert at the given dp-element (DPE-ID) could not be modified. The command to modify the alert was send by the manager described with the values at the keywords <system number> <manager type> -num <manager number>.
At the keyword <user ID> the internal user ID is given. With this information you can see which user has tried to modify the alert.
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.
The log-message can also occur if the user is clicking on the table-cell for the acknowledge function several times (without starting the double-click event) before the table is refreshed.
For the AEScreen you can define a block time for the queries (and the table refresh). If this refresh time is decreased this behavior can be avoided.
The default value for the refresh time is 1000ms. If it is reduced to 500ms the log-message should not occur because clicking several times on the unacknowledged alert is not possible then. After changing the refresh time the user interface needs to be restarted to take effect of the changes.