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

Create a technical support case if you need further support.

Cannot generate Connection Verification Log in OfficeScan (OSCE)

    • Updated:
    • 17 Oct 2016
    • Product/Version:
    • OfficeScan 10.6
    • OfficeScan 11.0
    • OfficeScan XG.All
    • Platform:
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2008 Enterprise
Summary

You are unable to generate the Connection Verification log. You have checked the ofcdebug.log and found the following:

  • There is no record found for connection verification.
  • It fails to open ..\PCCSRV\Log\verconn.log which is queried when generating a report for Connection Verification.

Below is a snippet of the log:

2012 07/13 08:24:35 [2140 : 2484] (00) (D) [cgiShowLogs][cgiShowLogs.exe]LogsViewVerconnLogPage::No record - [(1)]
2012 07/13 08:24:40 [1910 : 0554] (00) (F) [LogCache][ofcservice.exe]SearchVerConLogs:fail open file 'E:\Program Files (x86)\Trend Micro\OfficeScan\PCCSRV\Log\verconn.log' - [(1)]
2012 07/13 08:24:40 [2424 : 2458] (00) (D) [cgiShowLogs
[cgiShowLogs.exe]LogsViewVerconnLogPage::No record - [(1)]
Details
Public

You can generate verconn.log by performing Manual Verification and Scheduled Verification. This log is queried/accessed when exporting Connection Verification log.

To resolve the issue:

  1. Open the OfficeScan management console.
  2. Do one of the following:
    • For OfficeScan 11.0/XG, go to Agent > Connection Verification > Manual Verification tab.
    • For OfficeScan 10.6 and below, go to Networked Computers > Connection Verification > Manual Verification tab.
  3. Click Verify Now.
  4. Go to ..\Program Files\Trend Micro\Officescan\PCCSRV\Log.
  5. Check if there is a verconn.log generated.
  6. Open the OfficeScan console and do one of the following:
    • For OfficeScan 11.0/XG, go to Logs > Connection Verification Log.
    • For OfficeScan 10.6 and below, go to Logs > Networked Computer Logs > Connection Verification.
  7. Ensure that there are list of OfficeScan clients listed.
  8. Export the log to CSV.

If the issue persists, do the following:

  • Check if verconn.log is created in the ..\PCCSRV\Log folder.

    This is the file being accessed and referred to when generating Connection Verification log.

  • Check if verconn.exe is still running in the Windows Task Manager.

    If this executable file is still running, this means that it is still processing/retrieving the information that will be logged to verconn.log. In this case, verconn.log is still being used by the verconn.exe process. Thus, this prevents the generation of Connection Verification log.
    You may wait for a few minutes for the verify connection process to finish. If it is takes too long and the process seems to hang, you may terminate the verconn.exe process.

Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1060947
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.