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 be displayed 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 describes that the acknowledge state of the alert of the given dp-element (DPE-ID) could not be modified. The command to modify the alert was sent by the manager and described by using the keywords <system number> <manager type> -num <manager number>.
For the keyword <user ID> the internal user ID is given. With this information you can see which user has tried to modify the alert.
The log-message is shown when the following conditions are met:
- The referenced alert class of the given dp-element uses the acknowledge type “CAME and WENT must be acknowledged seperately”
- In the alert list of the AEScreen the CAME alert is displayed on a row which is not visible at the moment
- In the alert list of the AEScreen the CAME alert is displayed on a row 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 be shown if the user clicks on a table-cell of 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 of the refresh time is 1000 msec. If it is reduced to 500 msec, the log-message should not be shown since you cannot click on an unacknowledged alert. After changing the refresh time, the user interface must be restarted to apply the changes.