Job stays in Reading barcodes state

Various issues can cause jobs to stay in the Reading barcodes state for longer than expected.
If a job stays in the Reading barcodes state after you expect all the documents to have been read, try the following actions.
  1. Use the Complete barcode step action to see the percent of documents read by the scanner and the number of unread documents. Close the dialog and then do the action again. If the barcode reader is still reading barcodes for the job, the number of unread documents should decrease. If the number does not decrease, note which barcode readers are being used for the job.

    Look in the Barcode readers portlet and make sure that the barcode reader is connected. If the barcode reader is disconnected, select View log on the barcode reader portlet and look at the timestamps for any disconnect messages. If some barcodes were read when the barcode reader was disconnected, scan the documents again.

  2. Check the barcode format on the barcode reader. If the data is not in the expected format, the information read from the barcode is written to a file in the /aiw/aiw1/barcodereader directory (AIX or Linux) or C:\aiw\aiw1\barcodereader directory (Windows). The file is named BarcodeReaderName.unmatched, where BarcodeReaderName is the name of the barcode reader object that received the unexpected data. Compare the contents of that file with the barcode format that was used to read the barcodes. Correct the barcode format or the method used to create the barcode.
  3. Check the properties on the Verification tab of the Job property notebook. If the Complete step when all barcodes are read property is set to No, the job will not leave the Reading barcodes state until you complete the step using the Complete barcode step action.

Related information:

Completing the barcode step for a job
Parent topic: Reading barcodes