Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Manually enabling debug mode of Apex Central

    • Updated:
    • 16 Jul 2021
    • Product/Version:
    • Platform:
Summary

This article shows you how to manually enable debugging mode of Apex Central.

Details
Public

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”.

    Enable UI 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”.

    Disable UI Debug

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

Enabling Cgidelegate.log

 
Always back up the whole registry before making any modifications. Incorrect changes to the registry can cause serious system problems. Should this occur, restore it by referring to the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.
 
  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

 
Always back up the whole registry before making any modifications. Incorrect changes to the registry can cause serious system problems. Should this occur, restore it by referring to the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.
 
  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”/>.

    Enable Log Processor 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” />.

    Disable Log Processor Debug

  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” />.

    Enable ScloudProcessor 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” />.

    Disable ScloudProcessor Debug

  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:

    Access Debug options

  3. Go to DM Debugger and select the following:

    Enable DM Debug

  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:

    Access Debug options

  3. Go to DM Debugger and uncheck the following:

    Disabled DM Debug

  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”/>.

    Enabled Log Forwarder 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” />.

    Disable Log Forwarder Debug

  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;

    Enable Diagnostic.log Debug

  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;

    Disable Diagnostic.log Debug

  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.

      Start 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.

      Start Agent

      Click the image to enlarge.

    4. Select Start.
Premium
Internal
Partner
Rating:
Category:
Configure
Solution Id:
000287635
Feedback
Did this article help you?

Thank you for your feedback!


*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.