Batch scan fails after page 1
Scan documents to PDF and other file types, as simply as possible.
Brought to you by:
ben-cyanfish
Menu
▾
▴
#182 Batch scan fails after page 1
closed
nobody
5.1.1.26389
Bug Fix
Medium
WIA
2016-04-10
2016-04-05
No
I'm having a problem with NAPS2 and my HP OfficeJet 3830 (on wifi). I'm trying to batch scan from the feeder (single scan, one file per page), but I can only get 1 page before I get a "Selected Scanner is Busy" error. The scanner then feeds through all remaining pages, and I get the 1st two pages saved in the target folder.
To be clear, I get the error when the batch window first says "Scanning page 2" (immediately after finishing page 1), but the program outputs 2 files. Possibly a timing issue between the printer and the software?
I get the same error if I try "multiple scans (fixed delay)" as well. When the first page finishes, I get the scanner is busy error.
Not sure where to find the error log. I'll attach it if you can direct me.
OK, here's the error log, and my profiles as well. Using "Documents Scan - Feeder".
I'm not sure what you're asking about the main UI. I'm not trying to scan from CLI, and I'm not sure you can batch scan by just hitting the scan button with the default profile.
When I try to use TWAIN, I don't have any devices when I click "choose device".
Ah, Same thing happens as with a batch scan, except I only get 1 page of output.
I tried again using "Use Native UI" and I still get the same error.
I also checked using windows fax and scan to see if there was an overall windows issue, and it does scan multipages from the UI properly. So it shouldn't be a hardware compatibility problem between my network printer and the PC.
Same behavior. Error log attached.
OK, new behavior, but still a failure. After the initial progress window popped up, while scanning the 1st page. After the first page finished, the progress window completed, and a second window appeared and disappeared rapidly. I just caught the text saying "scanning page 2". It flashed for about a full second (or maybe 3 full seconds), when the device busy error message appeared again. We still only got 1 page. Error log attached.
Last edit: Joel Kolodziej 2016-04-07
Still no good. Error log attached. Same behavior as before the most recent test, except now I only get one page in color, even though I set it up for greyscale scanning.
I also tried using "native UI", but it kept bringing up the native UI dialog, and would not scan al all. Everytime I hit "scan" on the native UI, it just popped up another native UI window.
That program gives me an unhandled exception. I guess I'm out of luck. Thanks for trying though.
OK. So I went to the HP site and downloaded their official drivers (instead of using Microsoft's Win10 driver), and the TWAIN worked, and I had no problems at all.
Sorry for putting you through all the hard work when an official driver install is all that was needed to fix the issue.