Configure settings to specify the debug log level, maximum file size limit of the log file, and the log file location. Use these settings when you want to troubleshoot an issue with the product and provide the logs to McAfee Technical Support for further analysis.
| Configure Debug Log settings for troubleshooting purposes and only for a limited duration. Once you capture sufficient logs for troubleshooting, set the value for Level to None. Using debug logging indiscriminately could fill up the hard disk space and affect the overall performance of the server. Enable it for a limited duration as advised by an authorized personnel (McAfee Technical Support Engineer). |
Task
1 |
From the product's user interface, click .
The Diagnostics page appears.
|
2 |
In the Debug Logging tab, you can use:
Option definitions
Option |
Definition |
Level
|
To enable or disable debug logging and specify the level of information that should be captured in the debug log file. You can select:
• | None — To disable debug logging. |
• | Low — To log critical events such as errors, exceptions, and return values of functions in the debug log file. Select this if you want to keep a low size for the debug log file. |
• | Medium — To log events mentioned in the Low state and additional information that could be of help to the technical support team. |
• | High — To log all critical errors, warnings and debug messages in the debug log file. It contains information about all activities performed by the product. This is the most detailed level of logging supported by the product. |
|
Enable size limit
|
If you want to specify a maximum file size limit for each debug log file. |
Specify maximum file size
|
To specify how large the debug log files can be. You can specify a value from 1 KB to 2000 MB. | If the debug log files exceed the specified file size, older events will be rewritten due to circular logging, where new log entries are added to the file by deleting the oldest log entries. |
|
Enable debug logging
|
If you want to modify the default debug file logging location. | If this option is disabled, the debug log files will be stored under <Install Folder>\bin\debuglogs default directory. |
|
Specify file location
|
To specify the debug log file location path where events triggered by MSME can be stored. You can select:
• | <Install Folder> — To create the debug log files under the MSME installation directory. |
• | <System Drive> — To create the debug log files under the C:\Windows\system32 directory. |
• | <Program Files> — To create the debug log files under the Windows C:\Program Files (x86) directory. |
• | <Windows Folder> — To create the debug log files under the C:\Windows directory. |
• | <Data Folder> — To create the debug log files under the C:\ProgramData\ directory. |
• | <Full Path> — To store the debug log files in the complete path specified in the adjacent textbox. |
| To store the debug log files to a custom location or sub-folder, specify the sub-folder name or path in the field next to the drop-down list. |
|
| Make sure that the folder that collects the debug logs is provided "Write" permissions for the NETWORK SERVICE account. |
|
3 |
Click Apply to save the settings.
| For more information on generating Exchange Web Services (EWS) wrapper log for the on-demand scan task, see McAfee KnowledgeBase article KB82215. |
|
You have now successfully configured the debug log settings, that you can use for troubleshooting.