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

Question

Question

Where can I get the log of DCC Job:Task:EntryIDs?

asked on March 7, 2016 Show version history

I have a DCC job that was (I believe) sent something like 250 entries for OCRing and the results of the process are not easy to interpret.

The DCC webadmin console shows the Job ID that the workflow instance initialised, 2221 had 73 tasks, completed 73/73 tasks with the result "Failed" after 26minutes and 21seconds.

I can only see a concatenated summary of the EntryIDs associated:

 

-Entry ID's: 79876, 79465, 79539, 79549, 79531, 79858, 79519, 79865, 79910, 79174 ...

What I really need is a way to review all the entries handled and see where the error was generated.

 

I can't tell which client/worker agent machine was given the assignment either.

Is all this to be found in the event viewer logs, and if so is it on the client machines I need to go to or the scheduler?

Thanks guys,
W

 

Following up on this, I see in the Windows Logs on the Scheduler that the information is fairly limited:

 

-Entry ID's: 79876, 79465, 79539, 79549, 79531, 79858, 79519, 79865, 79910, 79174 ...

 

I can however see which worker it was sent to - I'll have to log in there and see what it knows about what went down.

0 0

Replies

replied on March 8, 2016

Our experience with DCC logging was similar - not a lot to go on when it reports "Failed".  But also note that unless this has changed in version 10, "Failed" could also mean something as innocent as a document with nothing to OCR - all handwritten text for example.

The way we found "Failed" docs was to query all docs that had been sent through DCC with partial or no indexing.

1 0
replied on March 8, 2016

Thanks, yes, I've added a token to collect in csv format all the entries sent so I can evaluate later when I need to.  Proving quite difficult to diagnose and handle our exceptions.  At the moment I have a series of tags commented with the date/time of first, second and third/final scheduling for DCC before being tagged for exclusion on subsequent runs of the DCC scheduling workflow and queued for a manual intervention business process. More interactive logging or feedback from the DCC would be very helpful.

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

Sign in to reply to this post.