The error folder
Every configuration has an error folder. BarcodeOCR puts files there that it could not process successfully. This page sums up when that happens, how to recognize the cause and which settings you can check. Check the error folder regularly.
Causes at a glance
| Cause | How to recognize it | What to do |
|---|---|---|
| No barcode recognized | Error reason NoBarcode | For exported PDFs, turn on View PDF files as images during processing. The filters under Preprocessing the documents can improve recognition. With "Document stack not separated", BarcodeOCR only searches the first page, unless you turn on the search in the whole document under Advanced. |
| Naming conflict (duplicate): a file with the intended name already exists in the target folder, for example because a barcode appeared twice in a batch. | File name "Duplicate", error reason Duplicate, entry in the error log | Define the behavior under Conflict resolution, for example "Intended file name + consecutive number". |
| Invalid characters in the file name: the barcode contains characters that are not allowed in file names on NTFS. | File name "Naming Error", error reason NameError | Turn on Replace characters in the file name that are invalid in NTFS with. |
| Damaged file: the PDF file does not comply with the standard. | File name "Corrupted File", error reason CorruptedFile | Turn on Fix damaged PDF files. If the file cannot be repaired even then, it still ends up in the error folder. |
| Timeout: processing a file takes longer than allowed (60 minutes by default). | The source file is in the error folder. Partial documents already saved stay in the output or error folder. | Under Advanced, turn on Service restart delay (90 minutes) or Do not limit processing time. |
| Encrypted input file | not documented | Not documented. BarcodeOCR cannot process encrypted documents at all, see Encryption. |
| Following page without a barcode: the stack type requires the same barcode on the following pages. | not documented | Check the behavior of the selected stack type. |
| Two consecutive blank pages with the stack type "with the same barcode as a mandatory requirement or each with an empty page" (duplex) | not documented | Check the behavior of the selected stack type. |
File names in the error folder
Since version 21.4.2, the name of a file that is moved to the error folder because of a problem also contains the original file name: <reason>_<old file name>_<random string>.
What happens if a file with the same name already exists in the error folder is defined under Conflicts in the error folder.
Files in the error folder also go through text recognition and are encrypted if you set this up under Text recognition and optimization.
Error reasons in scripts
Scripts and downstream applications learn why a file ended up in the error folder. This way you can forward or report error files automatically.
| Interface | Parameter | Possible values |
|---|---|---|
| Type 1: Program after each output file | -errorReason | None, NoBarcode, Duplicate, Error |
| Type 3 and Type 4 (PowerShell) | ErrorReason | NoBarcode, CorruptedFile, Unknown, Duplicate, NameError |
The type 1 downstream application is also called after each save in the error folder. With type 2, the -files list shows for each file whether it was processed successfully (True or False), see Type 2: Program after each input file.
Check the log
Error messages and naming conflicts are also recorded in the error log. How to open it is described in Service and logs.