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

Appendix A
WVP Event Analyzer Plug-in User Guide V01 – 536989-001
- 80 -
NSEVNTA 103
<Program Name> <Function Name>: Error Reading file <Filename>:<Error Number>
Relating to function or activity: Reading from a key-sequenced file (database file) to access contents.
Cause: Occurs on the “READX” 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. the operation
timed out (Error 40).
Effect: If the error occurs on the collector program, the daily database updates or the one-time loads
will not be completed. If the error occurs on the UI, the screen or data requested will not be displayed.
Recovery: Recovery will depend on the specific Guardian error returned. For e.g. Error 11 can be
recovered from by ensuring the file exists in its proper location or that the program is pointing to the
right volume. This error on READX means the file was moved or purged after the open but before the
read.
NSEVNTA 104
<Program Name> <Function Name>: Error Writing file <Filename>:<Error Number>
Relating to function or activity: Writing to a key-sequenced file (database file) to access contents.
Cause: Occurs on the “WRITEX” 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. no write
permissions (Error 48).
Effect: This error occurs on the collector program. The daily database updates or the one-time loads
will not be completed.
Recovery: Recovery will depend on the specific Guardian error returned. For e.g. Error 48 can be
recovered from by assigning proper permissions to the file or the program trying to write to the file.
NSEVNTA 105
EACOLL <Function Name>: Pair Info Error <Error Number>
Relating to function or activity: EACOLL backup process attempting to communicate with the primary.
Cause: Occurs on the “PROCESS_GETPAIRINFO_” 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 9).
Effect: The backup process will not be able to communicate with the primary. This will prevent the
backup process to take over as the primary in case the primary process goes down.
Recovery: Recovery will depend on the specific Guardian error returned. For e.g. Error 9 can be
recovered from by restarting the Web ViewPoint (and hence EA) processes.
NSEVNTA 106
EACOLL <Function Name>: Decompose Error: <Error Number>
Relating to function or activity: Primary or backup EACOLL process trying to retrieve process
information from the process handle.
Cause: Occurs on the “PROCESSHANDLE_DECOMPOSE_” 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).