Question

OCR engine crash

Laserfiche

Updated January 6, 2016

asked on January 5, 2016

I'm working on a mass OCR on an image import. 14,000 files all multiple pages. I keep finding the machine crashing as well as read error on individual files. The last 2 times I get a OCRengine not responding. This is what I get from the event viewer.

Faulting application name: LFOmniOCR.exe, version: 9.0.0.165, time stamp: 0x54ebd105
Faulting module name: ntdll.dll, version: 6.3.9600.18146, time stamp: 0x5650afd4
Exception code: 0xc0000374
Fault offset: 0x000e5914
Faulting process id: 0x27ac
Faulting application start time: 0x01d1471cadc9d39c
Faulting application path: C:\Program Files (x86)\Common Files\Laserfiche\Batch Processor\BPOmniOCR185\LFOmniOCR.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 5f1a3df1-b37c-11e5-80ca-005056a11171
Faulting package full name:
Faulting package-relative application ID:

Any ideas on how to prevent this? Thanks.

0 0

Replies

replied on January 5, 2016

How are you doing the Importing and OCRing? You can get this behavior when you run out of resources. Instead of doing it all at once, split the imports up.

0 0

replied on January 5, 2016

I import all the Docs without running OCR and then I ran it after they are in the Repo. These are all multi page tiff files. I am now getting this error.

0 0

replied on January 5, 2016

Here is a better look. This is a file that I took out of the repo to the desktop, it converted to .pdf, I re-imported it with generating pages and reran the OCR with normal settings as well as advance settings. Still getting this error.

0 0

replied on January 6, 2016

How big are the files? The issue can still be about resources. Does it fail on exactly the same spot for the same files? It can also be profile specific. If another user on another machine tries to OCR it, does it work? It can also be LF version specific. Are you running the latest version of Laserfiche?

0 0

You are not allowed to follow up in this post.

Question

Question

OCR engine crash

Replies

Sign in to reply to this post.