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

OL Connect Enterprise Workflow
1

Hi All,

Just updated our development/test/acceptance servers to 2023.1. Since the update we are experiencing 2 error that occur often in a run of creating 10k documents through workflow. The update is on the machines now for a couple of weeks. Backups are deleted because all seemed fine.

The errors we encounter are the following:

  • ERROR: 10:27:46.172 [0061] W3685 : Error processing file E:\ProgramData\Objectif Lune\PlanetPress Workflow 8\PlanetPress Watch\Spool\36.tmp\job010HQDMYBALNXB8E4419.dat: W3687 : Error replacing job file by processed file: Error code 14007: The requested lookup key was not found in any active activation context.
  • ERROR: 10:28:33.298 [0001] W3011 : Input folder error: A call to an OS function failed

So far I’ve tried te following actions:

  • Check antivirus exclusions, they are fine;
  • Made sure the machine is not working at full capacity;
  • Reinstalling Connect after deinstallation and removal of user settings and every possible folder;
  • Reinstalling Connect 2022.2 with same procedure;
  • Rollback config to current production config;
    All to no avail.

We have encountered this error last year on our production/acceptance/development servers, the solution then was to setup new servers for acceptance/development and do a backup restore for production.

Now I’m facing the same issue, and should setup 3 new servers for this issue. Not looking forward to do so…

What are other options to tackle this problem, and possible solutions.

Kind regards,

Ted van Roon
Nedasco BV

2

Dear tvanroon,

the error message that your report means that the file maybe in use by another process, AV or someone accessing the input file.
Which Antivirus do you have?
I strongly suggest opening a support ticket in order to investigate.

3

Just found out yesterday that we changed our local defender to a cloud managed defender. For the dev/test/acceptante machine. So there might be a correlation.

With your reply and the reply from FormLogic, our partner, I am fairly convinced the av is the problem. We are going to investigate further today.

4

Did some testing today, it seems that when onboarding the server to defender 365 the exclusions are not used. After offboarding the problem dissapeared.

5

This is not entirely surprising. By its very nature, Workflow does things that anti-malware software tend to regard as suspicious. We have had many reports of odd issues such as this that turned out to be caused by over-zealous, and sometimes ill-conceived, anti-malware. Hence the importance of properly configuring the appropriate exclusions.

6

Great answers everyone, thanks for the help