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

Create a technical support case if you need further support.

Core Protection Module exit codes

    • Updated:
    • 20 Dec 2013
    • Product/Version:
    • Core Protection Module 10.5
    • Core Protection Module 10.6
    • Endpoint Security Platform 7.2
    • Endpoint Security Platform 8.0
    • Endpoint Security Platform 8.1
    • Endpoint Security Platform 8.2
    • Platform:
    • Windows 2003 Enterprise
    • Windows 2008 Enterprise
    • Windows 7 32-bit
    • Windows 7 64-bit
    • Windows Vista 32-bit
    • Windows Vista 64-bit
    • Windows XP Professional
    • Windows XP Professional 64-bit
Summary
Whenever you deploy a fixlet message to an endpoint, the progress and status is written in the BES Client Log file as shown below:
%BES Client%\__BESData\__Global\Logs\yyyymmdd.log
A corresponding exit code is generated for every action script that the fixlet performs. See the sample log snippet below:
#################################
. . .
At 14:57:47 +0800 - Trend Core Protection Module QA (http://testsite.bigfix.com/cgibin/bfgather/trendcpmqa)
Command succeeded (Exit Code=106) waithidden "C:\Program Files\Trend Micro\Core Protection Module\TMCPMCLI.exe" CONFIG -i "C:\Program Files\Trend Micro\Core Protection Module\wpmlog.ini" (fixlet 519)
##################################
Exit Codes are used to troubleshoot failed fixlet deployments.
Details
Public
This article lists all possible Exit Codes that can appear in the BES Client Log files and their corresponding meaning.
Exit/Return code descriptions
CPM CLI Exit Code 100: Possible Explanations
Error code 100 can occur for either of these reasons:
  • Configuration file is corrupted
  • Memory/Resource shortage
Try this workaround to help solve/prevent error 100:
  1. Back up the current CPM Configuration file.
    %ProgramFiles%\Trend Micro\Core Protection Module\CpmConfig.ini
  2. Look for the Default CPM Configuration file in the same folder.
    %ProgramFiles%\Trend Micro\Core Protection Module\DefaultCpmConfig.ini
  3. Make a copy and name it as CpmConfig.ini to replace the current INI file.
  4. Restart the CPM services.
  5. Reboot the computer and redeploy the fixlet.
CPM CLI Exit Code 105: Possible Explanations
Error code 105 can occur for any of these reasons:
  • New configuration could not be deployed.
  • The Listener service is not running.
  • The NT RealTime Scan service is running incorrectly due to a wrong configuration or corrupted program/configuration files.
Try this workaround to help solve/prevent error 105:
  1. Open the following configuration files in %ProgramFiles%\Trend Micro\Core Protection Module\Backup using notepad:
    • Backup configuration file: CPMConfig_01.bak
    • Configuration that is being deployed: DeployedConfig_01.bak
  2. Check the time and look for an error in DeployedConfig_01.bak, compare the configuration, or restore the backup file the similar to Exit Code 100.
  3. Restart the CPM services.
  4. Reboot the computer and redeploy the fixlet.
CPM CLI Exit Code 106: Possible Explanations
Error code 106 can occur for any of these reasons:
  • The action that was executed has taken too long to complete.
  • CPM is running a virus scan on a large disk space.
  • One or more system resources are low.
  • There is a pattern-merging operation on a low-speed disk.
  • The NT RealTime Scan service is not running.
Try this workaround to help solve/prevent error 106:
  1. Ensure that the computer is running on adequate system resources.
  2. Reinstall CPM Endpoint Component
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1101672
Feedback
Did this article help you?

Thank you for your feedback!

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.

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.


Need More Help?

Create a technical support case if you need further support.