You are viewing limited content. For full access, please sign in.

Question

Question

OCR License Check Failed

asked on May 11, 2015

We're running LaserFiche 9.2 SP1 and Import Agent 9.0, and I've recently started seeing these errors in the event log:

     There was an error OCRing the file "X:\Scans\201505110816.tif" (OCR license check failed.)  

That error is immediately followed by this error:

     There was an error executing the profile HR while importing the file "X:\Scans\201505110816.tif". (Error reading file.) (1158)

The scanned file ends up in X:\Scans\IAError\.  If I manually move the file back to the Scans folder, the Import Agent will pick it up properly.

 

Server specs as follows:

  • LaserFiche 9.2 SP1
  • Import Agent 9.0
  • Server 2008 R2
  • 4GB Ram
  • Dual Xeon 2.2GHz processors

 

Has anyone experienced this?

 

0 0

Replies

replied on November 3, 2015

Some additional information on this - OmniPage basically launches an executable to do the license check every time OCR is run. Unfortunately if the executable can't launch for some reason - our of memory, dependency conflict, any number of standard windows stuff that causes exe's to fail to load - you'll get that error message. It might be worth seeing if the machine in question is low on resources or running slow enough that it's timing out, that sort of thing. 

2 0
replied on November 3, 2015

It appears to be a very transient error.  If OmniPage tries to launch the executable, and can't, I'm guessing if it waited for a second, then tried again, it might be successful.  Retry 'x' times.  Just a thought.

I still see this occur every couple of weeks.  Nothing major, just a minor pita. 

 

0 0
replied on May 11, 2015

In your profile, do you have "Perform image enhancement" checked or unchecked?

Do you get the same behavior with it checked or unchecked?

Have you applied the latest IA hotfix? https://support.laserfiche.com/KB/1012113c.  If not, please do so.

If this is still an issue after applying the hotfix, please have your VAR open a case with LF Support.

0 0
replied on May 11, 2015

Thanks for the quick reply!  

I did not have "Perform image enhancement" checked, but I have done so now.  I've also installed the latest IA hotfix.

I'll monitor it over the next couple of days.

 

 

0 0
replied on June 3, 2015

The problem seemed to have gone away for three weeks, but has resurfaced again today.  Exact same errors in the Application Event log as before.

 

0 0
replied on June 3, 2015

So what changed? Was anything removed/reinstalled recently?  Are you running any new processes on the machine that could be taking up resources?

0 0
replied on June 3, 2015

No changes that I'm aware of.  No new software installed/updated/uninstalled.  It's a dedicated server for LaserFiche only, so no other resource-stealer.

 

It's hit and miss.  Most scans go through fine, then suddenly one fails with those errors.  Again, if I move the files out of the IAError folder, and put them in the Scan folder... the Import Agent picks them up properly.

 

As a workaround, I'm tempted to write a script to run every 10 minutes to scour those IA folders and move the files back into the scan folder.

 

 

0 0
replied on September 22, 2015

We're getting reports of these exact errors as well, did anyone find a cause/fix at all?

0 0
replied on September 22, 2015

It may be file specific.  Does it work if you drag and drop and OCR with the LF client?

0 0
replied on September 24, 2015

I never did find a cause for it.  I wrote a script that runs every few minutes and moves any files it finds into the proper folders.  It does the trick!

0 0
replied on November 3, 2015

Interesting to note. Just had a call with a customer who is also experiencing this issue. Are there any updates from Laserfiche on this?

 

Cheers!

0 0
replied on November 3, 2015

Please open a case Chris

0 0
replied on November 3, 2015 Show version history

Hi Raymond,

It's OK. It seems to be related to a particular file or files. The customer has re-scanned the files and it seems to be working again now. I see this error from time to time across various sites, seems totally random as you scan the same document again and it works.... Weird....

 

I was just wondering if anyone had nailed it yet....

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.