Interpreting Windows Error Codes; Agent Activity Log; Use Of The Virusscan Update Log - McAfee EPOLICY ORCHESTRATOR 4.0 - LOG FILES FOR Troubleshooting Manual

Troubleshooting with Log Files

Interpreting Windows error codes

Interpreting Windows error codes
To understand Windows error messages, identify the error code and look it up in the MSDN
library.
1 Locate messages of type e or E in the log file.
2 Identify the time that the problem occurred, if known.
3 Note the Windows error code associated with the problem event.
4 Find the error code in the MSDN library at:
http://msdn2.microsoft.com/en-us/library/ms681381.aspx
For example, when tracking down an error message that includes code 1326, navigate to
and click the code in the list of system error codes. The explanation of the code is displayed:
1326 ERROR_LOGON_FAILURE Logon failure: unknown user name or bad password
NOTE: You can also use the ERRLOOK.EXE utility to determine the cause of these error
codes. This utility is distributed with Microsoft Visual Studio

Agent activity log

The agent activity log (AGENT_<SYSTEM>.XML) contains copies of messages from the
AGENT_<SYSTEM>.LOG, including translated messages, of types "e", "w", and "i", (corresponding
to logging levels 1 – 3). This file is not intended for debugging, but as information for users not
likely to be troubleshooting. Messages of type "x" (logging level 4) can be included in the activity
log. For information on setting levels, see
Information in the activity log also appears in the Agent Monitor.
If you enable remote access to the agent activity log file, you can also view the agent debug
log files remotely by clicking View debug log (current or previous) in the agent activity log
file. For instructions, see "Agent Activity Logs" and "Viewing the agent activity log" in the ePolicy
Orchestrator 4.0 Product Guide.

Use of the VirusScan update log

The UPDATETXT.LOG file in VirusScan Enterprise 8.0i and 8.5i provides information derived
from the AGENT_<SYSTEM>.LOG. It does not provide any additional information than the agent
log provides. However, VirusScan reformats the information for compatibility with previous
versions. In addition, users can control the content that is displayed in the UPDATETXT.LOG
and can designate its location.
12 Using Log Files for Troubleshooting in ePolicy Orchestrator 4.0
Logging levels for debugging.