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

Question

Question

Please confirm: DCC error message "failed job" means?

asked on June 25, 2015

I have been doing a lot of work troubleshooting DCC lately. I came across this post which refers to DCC and WebAccess. It indicates that the error message "Failed" might just mean that a single document like a blank page for example was not OCRed vs non of the documents were ocr'ed. It would be great if I could get some information on all the things that can cause that error message. Is this only the case when using DCC with webaccess or for thick client too? 

https://answers.laserfiche.com/questions/71182/Sending-Document-to-DCC-with-blank-page-causes-job-to-Fail 

"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." -Alex Huang

0 0

Answer

SELECTED ANSWER
replied on June 25, 2015

The error message is generic and as indicated, could occur in situations where the job actually didn't fail. While we are working on cleaning up the error handling in DCC, I'd recommend just reviewing the DCC event logs to determine if a reported error is legitimate or not.

0 0

Replies

replied on June 26, 2015

I have a user that would like a feature added if possible,

"I get these errors every time DCC fails to get text from an image (whether blank or has no words).  It isn’t a huge issue but it has thrown a wrench into several of my workflows due to them running based on a document being marked as ‘ocrpages = true’.  Ideally if it could just throw in a blank text file instead of leaving nothing there (or the option to) would be nice…or someway for workflow to communicate with DCC."

0 0
replied on June 26, 2015

Thanks Ben. That had been noted in the bug report so it is something we're factoring in.

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

Sign in to reply to this post.