Extraction is not working in PEGA OCR Component as expected

General
, , , ,
1

Hi,

We’ve followed the installation guide to set up the Pega OCR Component. Currently, we’re testing the functionality by sending an image to an email listener and verifying if the content within the image is successfully extracted. However, we encountered an error in the log file. Does anyone have insights into resolving this issue?

2024-05-17 20:19:53,982 [gine-single-thread-0] [          ] [                    ] [                    ] (or.Data_AbbyyFineReader.Action) ERROR   - ABBYY Text Extractor error: Internal program error: 
Src/Cache/CacheImpl.cpp, 556. 
com.abbyy.FREngine.EngineException: Internal program error: 
Src/Cache/CacheImpl.cpp, 556. 
	at com.abbyy.FREngine.IFRDocument.Process(Native Method) ~[pega.ocr.component.jar:?] 
	at com.pegarules.generated.activity.ra_action_abbyytextextractor_63d7a9c7c75f454954ee19d8e3a46f9d$1.execute(ra_action_abbyytextextractor_63d7a9c7c75f454954ee19d8e3a46f9d.java:494) ~[?:?] 
	at com.pega.platform.abbyy.AbbyyEngineAccessor.lambda$runJob$1(AbbyyEngineAccessor.java:108) ~[pega.ocr.component.jar:?] 
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_131] 
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_131] 
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_131] 
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_131] 
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131] 
2

@Bharathan An error setting up the OCR component with AbbyyEngineAccessor can be caused by the location where the engine is installed. If the engine is installed in a location like /root/, it may run into access issues. Installing the engine in a location like /opt/ can resolve this issue.

:warning: This is a GenAI-powered tool. All generated answers require validation against the provided references.

Problem installing OCR Component

If you still need help please log a support issue via the MSP and provide the INC id here so we can help track it.