Hey Jason,

Unfortunately DCC doesn't offer much in the way of feedback as to why it fails from what I can see, it just shows that the job failed in the job log. Greyscale scanning is a business decision so that isn't going to change, what's very odd is that as I said it OCR's absolutely fine through the client, so it's not an image issue, it's something specific with DCC.

Cheers!

That sounds pretty similar to what I encountered. I wasn't suggesting you stop using grayscale, just that it might require some adjustments to your OCR settings.

Something to consider is that OCR on a local machine is very different from using OCR on the DCC. Local OCR is just one process at a time, but the DCC can be juggling multiple actions and could easily overwhelm your server's resources.

I would try the following steps:

1. Check your server to see how it is doing as far as memory/cpu resources
2. Set the "max" threads/tasks to be 1 lower than the number of processors (for example, our DCC workers have 12 processors, so we limit them to 11 tasks to make sure they shouldn't go beyond about 85% utilization)
3. Test again to see how things run

If you continue having the same problem

1. Disable OCR options one at a time until you get better results
2. Try re-enabling them one at a time to see which ones may be causing the problems.

My guess would be that you're either looking at resource issues, problems with some of the settings, or a combination of both. Also check which version of DCC you are on because an update improved performance when we first started using DCC.