Enabling UI_Debug.log

1. On the Apex Central server, go to ..\Control Manager\WebUI\WebApp.
2. Open the Web.config file using a text editor and edit the Log4net threshold entry by changing the value from =”ERROR” to =”DEBUG”.

   

3. Save and exit from the text editor.
4. Restart the IIS Admin Service.
5. UI_Debug.log will be located under ..\Control Manager\DebugLog\.

Disabling UI_Debug.log

1. On the Apex Central, go to ..\Control Manager\WebUI\WebApp.
2. Open the Web.config file using a text editor and edit the Log4net threshold entry by changing the value from =”DEBUG” to =”ERROR”.

   

3. Save and exit from the text editor.
4. Restart the IIS Admin Service.

Enabling Cgidelegate.log

1. On the Apex Central server, open Registry Editor (regedit).
2. Change the value of the following registry keys:
   [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TrendMicro\TVCS\Package\TMCM\ISAPI]
   "DEBUG_LOG_LEVEL"=dword:01073ff8
   "DUMP_BLOB_ENABLE"=dword:00000001
3. Restart the IIS Admin Service.
4. TMCM_cgiDelegate.log will be located under ..\Control Manager\DebugLog\.

Disabling Cgidelegate.log

1. On the Apex Central server, open Registry Editor (regedit).
2. Change the value of the following registry keys:
   [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TrendMicro\TVCS\Package\TMCM\ISAPI]
   "DEBUG_LOG_LEVEL"=dword:00000000
   "DUMP_BLOB_ENABLE"=dword:00000000
3. Restart the IIS Admin Service.

Enabling Log Processor Debug

1. On the Apex Central server, go to ..\Control Manager\.
2. Open the LogProcessor.exe.config file using a text editor.
3. Locate and set the following value: <priority value=”DEBUG”/>.

   

4. Save the changes.
5. Restart Trend Micro Apex Central Service.
6. TMCM_LogProcessor.log will be located under ..\Control Manager\DebugLog\.

Disabling Log Processor Debug

1. On the Apex Central server, go to ..\Control Manager\.
2. Open the LogProcessor.exe.config file using a text editor.
3. Locate and set the following value:<priority value=”WARN” />.

   

4. Save the changes.
5. Restart Trend Micro Apex Central Service.

Enabling ScloudProcessor Debug

1. On the Apex Central server, go to ..\Control Manager\.
2. Open the sCloudProcessorNET.exe.config file using a text editor.
3. Locate and set the following value:<priority value=”DEBUG” />.

   

4. Save the changes.
5. Restart Trend Micro Apex Central Service.
6. TMCM_SCloudProcessor.log will be located under ..\Control Manager\DebugLog\.

Disabling ScloudProcessor Debug

1. On the Apex Central server, go to ..\Control Manager\.
2. Open the sCloudProcessorNET.exe.config file using a text editor.
3. Locate and set the following value:<priority value=”WARN” />.

   

4. Save the changes.
5. Restart Trend Micro Apex Central Service.

Enabling DM Debug

1. Log on to the Apex Central server.
2. Click the space between “d” and “M” of Trend Micro:

   

3. Go to DM Debugger and select the following:

   

4. Click Apply
5. Close the window
6. dm_log_YYYY-MM-DD.log will be located under ..\Trend Micro\COMMON\TMI\DbgLog
   Where:
   YYYY = Year
   MM = Month
   DD = Day

Disabling DM Debug

1. Log on to the Apex Central server.
2. Click the space between “d” and “M” of Trend Micro:

   

3. Go to DM Debugger and uncheck the following:

   

4. Set the level to Error.
5. Click Apply
6. Close the window.

Enabling Log Forwarder Debug

1. On the Apex Central server, go to ..\Control Manager\.
2. Open the LogForwarder.exe.config file using a text editor.
3. Locate and set the following value: <priority value=”DEBUG”/>.

   

4. Save the changes.
5. Restart Trend Micro Apex Central Service.
6. TMCM_LogForwarder.log will be located under ..\Control Manager\DebugLog\.

Disabling Log Forwarder Debug

1. On the Apex Central server, go to ..\Control Manager\.
2. Open the LogFrowarder.exe.config file using a text editor.
3. Locate and set the following value: <priority value=”ERROR” />.

   

4. Save the changes.
5. Restart Trend Micro Apex Central Service.

Enabling Diagnostic.log Debug

1. On the Apex Central server, go to ..\Control Manager\WebUI\WebApp\widget\repository\widgetPool\wp1\inc\.
2. Open the config.php file using a text editor.
3. Locate and set the following value: $GLOBALS['wfconf_debug'] = true;

   

4. Save the changes.
5. Diagnostic.log will be located under ..\Control Manager\WebUI\WebApp\widget\repository\log\.

Disabling Diagnostic.log Debug

1. On the Apex Central server, go to ..\Control Manager\WebUI\WebApp\widget\repository\widgetPool\wp1\inc\.
2. Open the config.php file using a text editor.
3. Locate and set the following value: $GLOBALS['wfconf_debug'] = null;

   

4. Save the changes.

Enabling MCP Agent Debug

1. Log on to the Apex One server.
2. Go to <Apex One Server installation folder>\PCCSRV\CmAgent.
3. Using a text editor, open the product.ini configuration file.
4. Update product.ini by adding the following entries:

       [Debug]
       debugmode = 3
       debuglevel= 3
       debugtype = 0
       debugsize = 10000
       debuglog = C:\CMAgent_debug.log
       

5. Save and exit from product.ini.
6. Start the Apex One Apex Central Agent service from Microsoft Services applet:
   1. Go to Start > Run.
   2. Enter services.msc.
   3. In the Services applet, right-click the Apex One Apex Central Agent.

      

      ^{Click the image to enlarge.}

   4. Select Start.
7. CMAgent_debug.log is located on C:\.

Disabling MCP Agent Debug

1. Log on to the Apex One server.
2. Go to <Apex One Server installation folder>\PCCSRV\CmAgent.
3. Using a text editor, open the product.ini configuration file.
4. Update product.ini by removing the following entries:

       [Debug]
       debugmode = 3
       debuglevel= 3
       debugtype = 0
       debugsize = 10000
       debuglog = C:\CMAgent_debug.log
       

5. Save and exit from product.ini.
6. Start the Apex One Apex Central Agent service from Microsoft Services applet:
   1. Go to Start > Run.
   2. Enter services.msc.
   3. In the Services applet, right-click the Apex One Apex Central Agent.

      

      ^{Click the image to enlarge.}

   4. Select Start.