You need to enable DLP OCR server trace logging

Products

• Data Loss Prevention Sensitive Image Recognition

Issue/Introduction

If there is an issue with DLP OCR detection and the default OCR Server logs are not providing enough detail to diagnose the issue appropriately.

Resolution

Here is the log location on the OCR server needed: C:\SymantecDLPOCR\Protect\logs

In addition to this it is likely worthwhile to enable trace level logging.

For any system experiencing the 30 second timeout, enable trace logging. After that, restart the SymantecDLPOCR service and attempt to reproduce the issue.

How to enable OCR trace Logging -

Path: c:\SymantecDLPOCR\protect\config

File: log4cxx_config_ocrworker.xml

Example:

<?xml version="1.0" encoding="UTF-8" ?>
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">
 <appender name="ocrEngineAppender" class="org.apache.log4j.RollingFileAppender">
  <!-- file is the base path and name for the ocr worker log files -->
  <!-- "../logs/debug/ocrworker" results in logs named "../logs/debug/ocrworker-workerid.log" -->
  <!-- where workerid is the identifier for a particular instance of an ocr worker -->
  <param name="file" value="../logs/debug/ocrworker" />
  <param name="append" value="true" />
  <param name="MaxFileSize" value="1024KB" />
  <param name="MaxBackupIndex" value="5" />
  <layout class="org.apache.log4j.PatternLayout">
   <param name="ConversionPattern" value="%d{%m/%d/%y %H:%M:%S} | %-5p | %c{2} | %m%n" />
  </layout>
 </appender>
 
 <category name="ocrEngine" >
  <priority value ="trace" />
  <appender-ref ref="ocrEngineAppender"/>
 </category>

</log4j:configuration>