Supported Trend Micro Products/Versions
The following section lists all Trend Micro products/versions that are considered current and are fully supported by Trend Micro, along with milestone dates (End-of-Sale and End-of-Life) that have been formally announced.Please refer to Trend Micro’s latest End-of-Life Policy for more information on milestone definitions and standard timelines. You can also view the products/versions that have reached End-of-Life in the past 12 months here.
End-of-Life Trend Micro Products/Versions
The following section lists all Trend Micro products and versions that have reached End-of-Life (EOL) status (formerly End-of-Support or EOS) in the last twelve (12) months and are no longer actively supported by Trend Micro. If the product/version you are looking for is not listed below, it is either still supported or is an older version that has been End-of-Life for more than 12 months.Please refer to Trend Micro’s latest End-of-Life Policy for more information on milestone definitions and standard timelines.
"Feature disabled. Unable to single sign-on to Trend Vision One™..." error appears in Apex Central™
The following error appears when using Single-Sign On (SSO) for Trend Vision One tab in the Apex Central SaaS console:Feature disabled. Unable to single sign-on to Trend Vision One. Additional licensing and administrator account privileges required. For more information, contact your support representative.
2025 Release Schedule for Trend Micro Apex One™ and Trend Micro Apex Central™
This article provides information on Year 2025 release schedule for Trend Micro Apex One and Trend Micro Apex Central On-premise.
Deploying policies from Trend Micro Apex Central™ is stuck at "Pending: Waiting for product agent" status because the IIS Server is handling too many requests
When policies are deployed from Apex Central to Apex One, all agents show the "Waiting for product agent" status.Root Cause AnalysisHTTP Error 503 can be seen in the following logs: From Apex One ofcdebug.log located at ...\Trend Micro\Apex One\PCCSRV\Log\: These logs correspond to Apex One Vulnerability Protection issue: 2020 02/27 12:20:14 [0a04 : 21f8] (00) (I) [][ofcservice.exe]BoostHTTPContext::prepareContext - prepare context scheme=[https], host=[DMZTMAO01.interdomain.com], port=[4343], target=[/officescan_ivp/command/osf/OnQuery] - [libosfsvcclienthttpcontext.cpp(228)] 2020 02/27 12:20:14 [0a04 : 21f8] (00) (E) [][ofcservice.exe]BoostHTTPClient::receive - http response code=503 - [libosfsvcclienthttpclient.cpp(101)] These logs correspond to Apex One Application Control issue: 2020 02/27 12:21:14 [0a04 : 22f0] (00) (I) [][ofcservice.exe]BoostHTTPContext::prepareContext - prepare context scheme=[https], host=[192.168.25.113], port=[4343], target=[/officescan_iac/osf/ONQUERY] - [libosfsvcclienthttpcontext.cpp(228)] 2020 02/27 12:21:14 [0a04 : 22f0] (00) (E) [][ofcservice.exe]BoostHTTPClient::receive - http response code=503 - [libosfsvcclienthttpclient.cpp(101)] From diagnostic.log of Apex Central located under ...\Control Manager\WebUI\WebApp\widget\repository\log\Diagnostic.log Apex One Vulnerability Protection error: 2020-02-27 12:21:00,208,DEBUG,null,null,[modOSCE IVPProxy][send_policy]URL = https://dmztmao01.interdomain.com:4343/officescan_ivp/command 2020-02-27 12:21:00,208,DEBUG,null,null,[modOSCE IVPProxy][send_policy] HTTP failed, HTTP status code: [503]. Apex One Application Control error: 2020-02-27 12:21:00,208,DEBUG,null,null,[modOSCE IACProxy][send_policy_to_osce_server]In2020-02-27 12:21:00,208,ERROR,null,null,[modOSCE IACProxy][send_data]HTTP failed, HTTP status code: [503]. The HTTP 503 error may occur if there are too many requests being handled by the IIS server, causing the request limit to be exceeded.
Verifying Trend Micro Apex Central™ database using Microsoft Open Database Connectivity (ODBC)
You can verify the Apex Central database details and test the connection using ODBC on the Apex Central server.
"Application Control Service: Disabled product services" error appears when deploying a policy using Apex Central
When deploying a policy from Apex Central, the following error is encountered:Click the image to enlarge.Application Control Service: Disabled product services.
Manually enabling debug mode of Apex Central
This article shows you how to manually enable debugging mode of Apex Central.
Information about Apex Central - SMEX Settings Replication
This article provides information about which ScanMail for Exchange settings can be replicated via Apex Central / Control Manager.
Missing entry in the php.ini file causes "System error. Error ID: -1" when deploying policies from Apex Central
The Policy Deployment status shows "Unable to deploy: See Command Tracking". Upon checking the Command Tracking page, the "System error. Error ID: -1" message is shown.Root Cause AnalysisChecking the php-errors.log (located on the Apex Central ..\Trend Micro\Control Manager\DebugLog\..), the error keyword "PHP Fatal error" occurs during processing policy data.thrown in C:\Program Files (x86)\Trend Micro\Control Manager\WebUI\WebApp\widget\repository\widgetPool\wp1\proxy\modOSCE\OSCE\Proxy.php on line 896[30-Apr-2020 14:06:42 Asia/Singapore] PHP Fatal error: Uncaught Error: Call to undefined function ProcessPolicyData() in C:\Program Files (x86)\Trend Micro\Control Manager\WebUI\WebApp\widget\repository\widgetPool\wp1\proxy\modOSCE\OSCE\Proxy.php:896Stack trace:#0 C:\Program Files (x86)\Trend Micro\Control Manager\WebUI\WebApp\widget\repository\widgetPool\wp1\proxy\modOSCE\OSCE\Proxy.php(532): OSCEProxy->customize_json_data(Array)After checking further, the entry for php_Ofc.dll is missing from the php.ini file. Without the entry, the PHP process will not load php_Ofc.dll and cause the issue.
