ContentExtractionHost_FileReader.log is not getting updated
search cancel

ContentExtractionHost_FileReader.log is not getting updated

book

Article ID: 261613

calendar_today

Updated On:

Products

Data Loss Prevention

Issue/Introduction

The ContentExtractionHost_FileReader.log is not getting updated and you cannot validate if your custom Content Extraction Plugin is working correctly.

Environment

Release : 15.8/16.0

Resolution

  1. Stop the SymantecDLPDetectionServerService on your detection server.
  2. Go to [Install Dir]\ProgramData\Symantec\DataLossPrevention\DetectionServer\XXX\logs\debug on that server and rename ContentExtractionHost_FileReader.log to ContentExtractionHost_FileReader-OLD.log.
  3. Start the SymantecDLPDetectionServerService and once the server will be showing as reporting on the Enforce, please check if a new ContentExtractionHost_FileReader.log was created.