OCR Issues - Application Enabler - English - Foundation 22.1 - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

When rebuilding the font database that the OCR engine requires to do OCR parsing, Application Enabler attempts to generate a file named OCRSDK.pat in the folder where the Application Enabler executable exists, if OCRSDK.pat does not already exist. If Application Enabler does not have write permission to that folder (e.g., when running the Application Enabler executable from UNC path, or when Windows UAC is enabled), an error message will be displayed and the OCR engine will not function correctly.

An example of this error message is the "Textract error -986" message displayed in the following screen shot:

To use Application Enabler 's OCR functionality, Windows UAC must be disabled, and users must have write permission to the folder where the Application Enabler executable is stored. To resolve this issue, disable Windows UAC and/or open the OCRSDK.ini file and modify the Database Path attribute to point to a location where the user has write permissions.

After verifying that OCR is properly configured and rebuilding the font database, you can use the following files, located in the user's Temp folder (i.e., C:\Documents and Settings\[user]\Local Settings\Temp), to continue troubleshooting:

• AEOCRtmp_mono.bmp- This image file is the monochrome version of the line-of-business screen, as recognized by the Local OCR engine. If this image does not contain recognizable text, then OCR will not work for this line-of-business screen.

• AEOCRtmp_poly.bmp- This image file is the polychromatic version of the line-of-business screen, as recognized by the Data Capture Server's OCR engine. If this image does not contain recognizable text, then OCR will not work for this line-of-business screen.

• AEOCRtmptext.txt- This text file is the OCR result of the last OCR operation. It is the same as the file generated when pressing View OCR text during configuration. It contains the same OCR result information in the AEVerbose file.

For these files to be generated in the user's Temp folder, Application Enabler must have read and write permissions to this folder.

When using Application Enabler Configuration, these three files exist in the Temp folder until you finish configuring the screen.

When using Application Enabler on client workstations, these three files are created and immediately deleted from the Temp folder. They cannot be viewed unless Verbose Mode is enabled. When Verbose Mode is enabled, these three files are created and retained until you turn off Verbose Mode.

In most cases, the Application Enabler OCR engine will recognize the fonts that it needs to use by rebuilding the font database. If you find that the correct fonts are not being recognized by the Application Enabler OCR engine:

You can also edit OCRSDK.ini to exclude fonts if the Application Enabler OCR engine is recognizing fonts that it does not need to use when building the font database. Repeat the steps above, adding the font name(s) to the list of fonts in the Exclude line in the OCRSDK.ini file.

When the Always use ClearType for HTML Internet Explorer setting is enabled, fonts are rendered using ClearType, which is not recognized by Application Enabler 's OCR engine. To disable this setting in Internet Explorer, select Tools | Internet Options. Click the Advanced tab. Locate the Multimedia section and clear the Always use ClearType for HTML check box. Restart Internet Explorer.

This is an issue with Application Enabler and Windows Data Execution Prevention (DEP). To resolve, follow the steps in Application Enabler and Data Execution Prevention (DEP).