Hi Lucas,

There are two possible causes that I can think of:

1. OCR failed for a document, and DCC retried OCRing the document on another machine.  If the second attempt started before the first attempt completed unlocking the document,  then we’d get an Entry locked error.
2. Some other Laserfiche application is locking the document.

The first case is a DCC bug that would have to be addressed in a future release. 

Either way, to work around the issue, check the Entry Locks node in the Admin Console ([ServerName] > Repositories > [RepositoryName] > Activity > Entry Locks) after the OCR job has completed.  If the documents that failed to be OCRed are locked, then determine whether DCC or another application locked the document by looking at the user that created the lock.  If the displayed user implies that DCC created the lock, then it should be safe to use the Admin Console to manually release the lock.  If the displayed user implies that another application created the lock, then you’d have to decide whether it’s safe to manually release the lock.  After releasing the locks, try running an OCR job to OCR those failed entries.

Let me know if this works for you!