Windows Defender Causes PDF Splitter to stop process

OL Connect Professional Workflow
1

We have a process that is affected by Defender, we know it is this because we have switched off all Defender services and it works ok, it is 19300 documents being split from one large PDF by a PDF Splitter.

All exclusions are on including the folder that reports as the error in the log when it happens.

Any ideas, maybe disable live scanning? I suspect Windows Defender Advanced Threat Prevention as that runs during the process.

Any further ideas? What else can I try if exceptions are in place

2

Does this error occur in the PlanetPress Watch log? If so, can you please share the error which occurs by executing the PDF Splitter Workflow plugin?

3

image
image1403×88 26.1 KB

Hi Marten, I have uploaded the error message, we do have a support call open & I believe there is a discussion around this today. We did another test with Defender disabled and it all worked fine again, our next test will be with entire C and E drive in the exceptions list

Thanks
Dave (PB)

4 
ERROR: 16:45:58.054 [0050] W3001 : Error while executing plugin: W3671 : Move file C:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress Watch\Spool\8.tmp\tmp010JK0FRZ9FSN0CC6BEA346.pdf to C:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress Watch\Spool\8.tmp\spl010JK0DY58MWK03C6B89048.dat failed: Error code 14007: The requested lookup key was not found in any active activation context.
ERROR: 16:45:58.054 [0050] PDF Splitter: W1603 : Plugin failed - 4:45:58 PM (elapsed time: 00:06:40.181)

Transcribed the shared image to make the error searchable.

5

Please check whether these exclusions aren’t just ignored by the antivirus in a specific situation, as appeared to be the case regarding the following forum post:

A call to an OS function failed || Error code 14007: The requested lookup key was not found in any active activation context - OL Learn

6

Hi Dave,

I’m experiencing the same problems, as you can see in the other topic. I’ve found that when we have a local defender with the recommended exclusions from the manual there are no problems. When we onboard the server to defender365 the exclusions don’t work as they should be.

Maybe this helps.

Kind regards,

Ted van Roon
Nedasco BV

1 Like
7

Thanks for this, really appreciate your input & thanks to Marten as well as always a great help

Dave

1 Like
8

Awesome info, thanks for the link certainly helps