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)]
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:
- Open the OfficeScan management console.
- 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.
- Click Verify Now.
- Go to ..\Program Files\Trend Micro\Officescan\PCCSRV\Log.
- Check if there is a verconn.log generated.
- 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.
- Ensure that there are list of OfficeScan clients listed.
- 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.