Skip to main content
Kofax

Abandoning lock because owning process has died error in Capture Errors Log

8464

QAID # 8464 Published

Question / Problem:

Why does the error log contain errors stating:

"Abandoning lock {<xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx>} because owning process {<process id>}{<Ascent Capture module>} has died."?

Answer / Solution:

This is a normal Batch recovery error. The following information can be used in addition to QAID 7256:

Ascent Capture's Batch recovery system utilizes a background worker process named KdoBackgroundWorker (KBW). The KBW is active on any station that has an Ascent Capture module running either as a module or as a service.

The Batch recovery process works in two ways:

Scenario One

  • An Ascent Capture module has a Batch open and that module is abruptly shut down (i.e. end task) on station A.
  • No one will log back into Station A.
  • Station B will reset station A's Batch after 20 minutes only if the module on Station B is open for at least 20 minutes (just the module can be open without any batches open).
    This will log an error message such as the following into the Error Log:
    2007-06-07 10:50:50, 0x00000018, 0x00000000, 0x00000000, 0x00000000, 
    0x00000000, C:\Program Files\Ascent\Bin, Ascent Capture Batch Manager, 
    <Machine_Name>, 7.00.704.0, KdoBackgroundWorker.cpp, 582, Abandoning lock 
    {F11A4ACD-F782-45d5-A8F4-74A4FB807B11} because update count is stale, ,

Scenario Two

If a batch crashes on station A, it will reset immediately (in most cases) once any module is launched at station A.

This will log an error message such as the following into the Error Log:

2007-06-07 10:19:41, 0x00000018, 0x00000000, 0x00000000, 0x00000000, 0x00000000,
C:\Program Files\AscentSS\ServLib\Bin, Ascent Capture Batch Manager,
<Machine_Name>, 7.00.704.0, KdoBackgroundWorker.cpp, 627, Abandoning lock
{41A59414-309F-4129-85D1-9FA0D4AE69D2} because owning process 1796 qc.exe has died, ,

In some cases, a Batch may show an "In Progress" state in Batch Manager and still permit you to view the Batch History. If you click OK in the History tab, it will update the Batch Status to the previous state that it was in before it went into 'In Progress.' This occurs in rare cases because the Batch was recovered but the status hadn't updated. Viewing Batch History forces a status update.

Otherwise, you will receive a message stating that the Batch is locked and request that you retry in 20 minutes.

Applies to

Product Version Category
CAPTURE 6.0 Batch Manager
CAPTURE 6.0 Logs
CAPTURE 6.1 Batch Manager
CAPTURE 6.1 Logs
CAPTURE 7.0 Batch Manager
CAPTURE 7.0 Logs
CAPTURE 7.5 Batch Manager
CAPTURE 7.5 Logs
  • Was this article helpful?