HP Integrity NonStop H-Series - Manual (Page 84)

Appendix A
WVP Event Analyzer Plug-in User Guide V01 – 536989-001
- 84 -
Recovery: Recovery will depend on the specific Guardian error returned. For e.g. Error 14 (device
non-existent) can be recovered from by ensuring that the processes (for EACOLL and EAVIEW) are
up and running.
NSEVNTA 122
<Program Name> <Function Name>: Could not get process name of EA Collector
Relating to function or activity: Admin interface program communicating with the EACOLL process.
Cause: Occurs when getting the process name of the EACOLL program. The error could occur for
reasons such as non-existent process. The error detail in this case is obtained from a follow up EMS
event (#s 125, 126 or 112).
Effect: The changes made to the daily run time or the one-time loads initiated from the Admin screen
will not be completed.
Recovery: Recovery will depend on the specific error returned. For e.g. If the EACOLL process is not
found, restart Web ViewPoint (and hence EA) processes.
NSEVNTA 123
<Program Name> <Function Name>: WriteRead Write Error <Error Number>
Relating to function or activity: Admin interface program communicating with and writing to the
EACOLL process.
Cause: Occurs on the “WRITEREADX” Guardian procedure call. The Guardian error number
indicating what the cause was is part of the event text. Could occur due to various reasons, for e.g.
non-existent process (Error 14).
Effect: The changes made to the daily run time or the one-time loads initiated from the Admin screen
will not be completed.
Recovery: Recovery will depend on the specific error returned. For e.g. If the EACOLL process is not
found, restart Web ViewPoint (and hence EA) processes.
NSEVNTA 124
<Program Name> <Function Name>: Error occurred in EACOLL while receiving message
Relating to function or activity: Admin interface program communicating with and writing to the
EACOLL process.
Cause: If an error occurred in EACOLL during communication, an error indication is sent back in the
reply message to the admin interface and the interface then generates this event. The EACOLL error
detail will be indicated by another event generated by EACOLL.
Effect: The changes made to the daily run time or the one-time loads initiated from the Admin screen
will not be completed.
Recovery: Recovery will depend on the specific EACOLL error event generated.
NSEVNTA 125
<Program Name> <Function Name>: Invalid Filename <Filename>. Error <Error Number>
Relating to function or activity: Admin interface program getting the process name for EACOLL
program.