The document was sent to DCC from WebAccess, when the document contained a blank page it causes the job within the DCC to fail. When you remove the blank pages the job finishes successfully. The original document contained 10 pages with text and 10 blank pages as the user scanned them without page removal.
Question
Question
Sending Document to DCC with blank page causes job to Fail
Answer
This issue has been addressed and the patch can be obtained from KB 1013860
Replies
Alex,
We are experiencing the same case where the Job within DCC and WebAccess is indicating a failed status. We are receiving the same message in the event logs. Blank pages have zero text associated with them. My case would be that we would be sending large number of documents per job as recommended by the help files. We would get a failure for the entire job in DCC and need to QC to see why\what failed. Although it does not terminate the OCR process it does however inform the user incorrectly by saying that job failed.
Thanks for looking into this.
Thanks for confirming. A request has been filed such that a more accurate status is provided instead of incorrectly indicating the entire job failed when DCC OCRs blank pages.
Did this ever change in 10?
I have a decently large set of files I just processed and it looks like any one of them that have blank pages have come up as FAILED. This makes it hard to look for actual failures.
Hi Chris,
According to the SCR listings, the issue is there (123946) but it doesn't appear to have been resolved yet. I added a note that there continue to be requests for this.
thanks!
Hi Steven,
Are you referring to the OCR Status dialog in Web Access where you see it indicate that the job failed? If you open the document and view the text, can you see OCR'ed text for the non-blank pages?
I tested using Web Access and DCC and sent a document with some blank pages to have searchable text generated. While the OCR Status did indicate the job failed, I do see that text was generated and searching by that text works. Can you confirm if that's the case for you?
Also, looking at the DCC event logs, an error did get recorded, however, it should have been non-terminating. The message would look like
Could not find file 'C:\ProgramData\Laserfiche\Distributed Computing Cluster\Temp\5nvlawi2\job_32_32\taskFile_1_59.txt'.