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

Create a technical support case if you need further support.

OfficeScan (OSCE) Issue Detector tool for certificate issues

    • Updated:
    • 15 Mar 2020
    • Product/Version:
    • Apex One 2019
    • OfficeScan 11.0
    • OfficeScan XG
    • Platform:
    • N/A N/A
    • Windows 10
    • Windows 10 32-bit
    • Windows 10 64-bit
    • Windows 2000 Advanced Server
    • Windows 2000 Professional
    • Windows 2000 Server
    • Windows 2003 32-Bit
    • Windows 2003 64-Bit
    • Windows 2003 Datacenter 64-bit
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2003 Server R2
    • Windows 2003 Standard
    • Windows 2003 Standard 64-bit
    • Windows 2008 32-Bit
    • Windows 2008 64-Bit
    • Windows 2008 Datacenter
    • Windows 2008 Datacenter 64-bit
    • Windows 2008 Enterprise
    • Windows 2008 Enterprise 64-bit
    • Windows 2008 Server Core
    • Windows 2008 Server R2 Enterprise
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
    • Windows 2008 Web Server Edition
    • Windows 2008 Web Server Edition 64-bit
    • Windows 2012
    • Windows 2012 Datacenter
    • Windows 2012 Datacenter R2
    • Windows 2012 Enterprise
    • Windows 2012 Enterprise R2
    • Windows 2012 Server Essential R2
    • Windows 2012 Server Essentials
    • Windows 2012 Server R2
    • Windows 2012 Standard
    • Windows 2012 Standard R2
    • Windows 2012 Web Server Edition
    • Windows 2016
    • Windows 2016 Server Core
    • Windows 2016 Server Datacenter
    • Windows 2016 Server Standard
    • Windows 7 32-Bit
    • Windows 7 64-Bit
    • Windows 8 32-Bit
    • Windows 8 64-Bit
    • Windows 8.1 32-Bit
    • Windows 8.1 64-Bit
    • Windows Vista 32-bit
    • Windows Vista 64-bit
    • Windows XP Home
    • Windows XP Professional
    • Windows XP Professional 64-bit

If your OfficeScan (OSCE) agents exhibit the following symptoms, they might be caused by Certificate issues in your environment:

Possible Symptoms:

  • The Agent is not showing on the web console.
  • The Agent is not updating successfully.
  • The Agent does not receive configuration from the server.
  • The Agent is unable to upgrade to latest version.
  • The Agent cannot connect to the server.
  • The Agent service cannot start normally
  • The Agent does not behave normally

If the above symptoms still occur even when connection tests such as ping, telnet, or manually sending an http request (i.e. manually sending a cgiOnStart request:http://%serverName%:%serverPort%/officescan/cgi/cgionstart.exe) to the Officescan server show they ALL passed, plus the Network level client/server communication also shows no problems, then the most likely cause is the application failure that is caused by a certificate/signature issue.

To help you check if this is caused by Certificate issues, you can use the Officescan Issue Detector tool.

  • Digital signature failing to be verified issues.

    • All windows Error code: 0x800*****, -2146******,

      For example:

      Windows Error code: 0x80096005, 0x800b010a, 0x800b0110 etc.
      Windows Error code: -2146869243, -2146762486 etc.

    • Other error codes related with signature checking failure.
  • OSCE’s own certificate file(public key file: OfcNTCer.dat) missing or mismatched issues.
  1. "Set Log Path" to assign a log folder path, by default, it will be: C:\ _OSCE_IssueDetector\.
  2. Turn ON OfcDebug using the Turn On/Off OfcDebug.ini button.
  3. After turning On OfcDebug, you need to unload and reload the OSCE Agent to start writing debug log.
  4. This tool will create C:\OfcDebug.ini to enable OSCE debug mode, and after reloading the OSCE agent, OSCE will write OfcDebug.log into the log folder that you set in Step 1.
  5. Reproduce your OSCE agent problem/issue.
  6. Click Detect Certificate Issue, then check the result in the Message Box and also check in ADT's own log file.

    It will analyze the OfcDebug.log generated under the log folder you set.

  7. When an issue is detected, the issue description, possible root cause, and also the solutions will be in the output of this tool’s own log file (C:\Log_OSCEIssueDetector.log) as well as in the message box.
  8. Currently the Detect Certificate Issue button only supports analyze ofcdebug.log file under the assigned log path.
  9. Make sure to turn OFF OfcDebug.
  • If Cert_001 or Cert_002 issue is detected, which means an OfcNTCer.dat (OSCE’s own certificate file) related issue, you can choose to fix it by using the tool.
  • It will ask the user to unload agent first, then it will automatically copy the correct OfcNTCer.dat file from [\\%OSCE server% \ofcscan\Pccnt\Common\] folder to the local OSCE install folder for the user, then ask user to reload the agent.
  • If SMB access to \\%OSCE server%\ requires a user name and password login from local, you first need to log in using Windows Explorer.
  • If \\%OSCE server%\ can directly be opened via Windows Explorer without prompting a login dialog, this tool can directly copy the public key file to local.
  • Only for OfcNtCer.dat file related issues will this tool try to do some fix.
  • As for other issues, possible solutions and root cause will be in the output of both message box and in the following log file:


If you have an existing ofcdebug.log on hand (may be collected by CDT tool), and you want to analyze it using the Detect Certificate Issue button.

  1. Place the ofcdebug.log file into the %LogPath% folder:

    %LogPath% is the folder you set using button "Set Log Path", by default, it will be C:\_OSCE_IssueDetector\.
  2. Click Detect Certificate Issue.

When an issue is detected by the Detect Certificate Issue function, hitted logs will be the output in this tool’s own log. The “hitted log” means which log lines in the OSCE debug log indicate the issue.

So you can check “hitted log” to see which file signature failed to be verified. For example:

hitted log

  • It depends on the IssueDetector.ptn file that should exist under the same folder as this tool.
  • .NET framework 3.5+ version
  • If the OfcDebug.log file is very big, it may be a bit slow to respond after clicking the button.

    If the log file “OfcDebug.log” file is too huge, this tool may NOT be able to analyze it successfully or quickly, due to lack of enough free memory or other system resource.

    After turning ON ofcDebug.ini, click Detect Certificate Issue button to analyze the log file without waiting too long and to keep the log file from getting too big.

  • After the OfcDebug debug mode is turned ON, OSCE's log server will drop 5 files under C:\ for debug purposes, which will the same effect if you manually create C:\ofcdebug.ini:

    The 5 files are:

    • 7z.dll
    • 7z.exe
    • LogServer.exe
    • OfcPIPC.dll
    • tmdbg20.dll

    After OfcDebug is turned OFF, these 5 files will remain under C:\. You may manually delete them if they are no longer needed.

  • Supported OSCE versions:

    10.6 *, 11 *, 12 *

  • Supported Platforms:

    All Windows platforms the OSCE Agent Program supports

  • The tool does not need installation.
  • The tool will not get installed in your system and may be deleted anytime.
  • Changes To The System:

    • It only writes a registry key on the following registry:


    • A log file under C:\ :


    • You can remove them manually after troubleshooting is done.


Click image to enlarge

  • Download OSCE IssueDetector tool using this link.
  • Zip password: trend
Configure; Troubleshoot; Deploy; Upgrade; Update
Solution Id:
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.