• Disabled - Designates that logging is disabled
• Info - Designates informational messages that highlight the progress of the application at a coarse-grained level
• Debug - Designates fine-grained informational events that are most useful to debug an application
• Trace - Designates finer-grained informational events than Debug. This log level isn't applicable to McScript.log because it doesn't have trace logs

• Option 1: Set the log level (Debug or Info) in the TA policy using the ePolicy Orchestrator (ePO) console
  If Enable detail logging is set, the log level is set to Debug for all agent logs. If Enable detail logging isn't set, the log level is set to Info for all agent logs. You can control the log size and rotation only through the TA policy. They can't be changed on the local system.
   
  1. Log on to the ePO console.
  2. Click Menu, Policy, Policy Catalog.
  3. Select McAfee Agent from the Product drop-down list.
  4. Select General from the Category drop-down list.
  5. Click the policy that you want to change.
  6. Click the Logging tab.
  7. Select the option Enable detail logging.
  8. If needed, change the Log file size limit (MB) and Roll over count options.
  9. Click Save.
  10. To receive the policy change, send an agent wake-up call to the client.
       
• Option 2: Set the log level (Disabled, Info, Debug, or Trace) using the maconfig tool from the command line
  The maconfig settings override the settings in the TA policy and are applicable until you restart the TA service. After you restart the TA service, the agent honors the log level set in the TA policy.
  
  NOTE: By default, the location of maconfig.exe for TA 5.x is C:\Program Files\McAfee\Agent\
   
  Open an administrative command prompt on the local system and use maconfig.exe to enable debug logging:
   
  maconfig.exe -enforce -loglevel n
   
  Example:
   
  maconfig -enforce -loglevel 3
   
  Here, n equals one of the following:

1. It's best to enable trace level logging using maconfig –enforce –loglevel 3
2. Enforce the policy using the command cmdagent –e

1. Press Windows+R, type regedit, and click OK.
2. Navigate to the following key:
   
   64-bit: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\McAfee\Win32_GUI_Support_DLL]
   32-bit: [HKEY_LOCAL_MACHINE\SOFTWARE\McAfee\Win32_GUI_Support_DLL]
    
3. Double-click the debug_tracing string value and set Value data to 1.
4. Close the registry editor.
5. Restart the McTray.exe process.

NOTES:

• Debug logging continues until you change the value back to 0. Technical Support recommends that you change the value back after you've collected sufficient logs.
• Because McTray.exe runs under the logged-on user's profile, it also stores the debug logs under the logged-on user's profile. The MER tool doesn't collect these logs; you must obtain them manually.

McTray log is located in the following:

• Agent 5.5.1 or later:
  C:\Users\<username>\AppData\Local\Temp\McAfeeLogs
   
• Agent 5.0.x: 
  C:\Users\<username>\AppData\Roaming\McAfee\Common Framework\DB\Support DLL\DebugTraceFile 

NOTE: A separate log file is created for each new instance of McTray, with up to 20 historical files, plus one file for the currently active log. Each log file is dynamically pruned at runtime to 2 MB in length, until debug logging is turned off.

1. Download and extract the file ETLTrace*.zip from the "Attachment" section of this article.
2. Press Windows+R, type cmd, and click OK.
3. Navigate to the directory to which you extracted ETLTrace*.zip.
4. Run the following command:
    
   EtlTrace.exe -Start
    
5. Reproduce the issue.
6. Return to the command prompt and run the following command: EtlTrace.exe -Stop
7. If you need to collect binary file versions, run the following command: EtlTrace.exe -GetVer
8. Gather the following files:
   • EtlTrace.log
   • Syscore.etl