search cancel

Adobe Acrobat Reader DC version 2019.12.20034 and 2019.12.20035 does not generate any incident in DLP

book

Article ID: 175315

calendar_today

Updated On:

Products

Data Loss Prevention Endpoint Prevent Data Loss Prevention

Issue/Introduction

If a user does a print/copy of a PDF file using Adobe Acrobat Reader DC version 2019.12.20034 or 2019.12.20035, no incident will be generated. Earlier versions of Adobe Acrobat Reader DC do not have this issue.

When Printing a PDF with Adobe PDF Reader DC (2019.012.20034)

Line 1805: 06/26/2019 21:36:03 | 11980 | FINE    | Print.PrintConnector | 
Starting
Line 1806: 06/26/2019 21:36:03 | 11980 | FINE    | Print.PrintConnector | 
Started
Line 3620: 06/26/2019 21:39:25 |  7120 | FINE    | Print.PrintClient | 
CSTATUS : 0x20020003 | PrintDataAnalyser.cpp(589)
Line 3623: 06/26/2019 21:39:25 |  9672 | FINE    | Print.PrintConnector | 
Connection from 3668_ee96f84a_C:\Program Files (x86)\Adobe\Acrobat Reader 
DC\Reader\AcroRd32.exe
Line 3624: 06/26/2019 21:39:25 |  9672 | FINEST  | Print.PrintConnector | 
<DLPPrintRequestMarshallable>
Line 3695: 06/26/2019 21:39:25 |  9672 | FINEST  | Print.PrintConnector | 
String to normalize : TEst doc.pdf
Line 3696: 06/26/2019 21:39:25 |  9672 | FINEST  | Print.PrintConnector | 
String to normalize : TEst doc.pdfString after normalization : TEst doc.pdf
Line 3754: 06/26/2019 21:39:26 |  9672 | FINEST  | Print.PrintConnector | 
Failed to resolve file path, Retry Attempt : 0
Line 3818: 06/26/2019 21:39:27 |  9672 | FINEST  | Print.PrintConnector | 
Failed to resolve file path, Retry Attempt : 1
Line 3881: 06/26/2019 21:39:28 |  9672 | FINEST  | Print.PrintConnector | 
Failed to resolve file path, Retry Attempt : 2
Line 3886: 06/26/2019 21:39:29 |  9672 | FINE    | Print.PrintConnector | 
Disconnection from 3668_ee96f84a_C:\Program Files (x86)\Adobe\Acrobat Reader 
DC\Reader\AcroRd32.exe
Line 4307: 06/26/2019 21:41:23 |  9340 | FINE    | Print.PrintConnector | 
Shutting down

Environment

Symantec Data Loss Prevention 15.1 MP1 & 15.5 MP1

Resolution

This issue has been fixed in 15.5 MP2 and 15.7.