#529 Unable to scan multiple pages

[Tim Chin]

Hi - I've been using NAPS2 for years, and just got a new MFP unit (Xerox C505) and am using the WIA driver (was originally using TWAIN, but that was crashing so I switched to WIA). At this point, using my ADF, it scans all of the pages through the physical ADF, but only one page of scanned content is showing up in NAPS2. Am I missing a setting somewhere or have something misconfigured so that not all of the pages are scanning? Previously on my old unit, all of the pages would be scanned into NAPS2. Thanks for your help!

[Ben Olden-Cooligan]

Hi,

I just published a new beta version (6.0b4) with substantial WIA changes to fix this kind of issue. Please try it and let me know if it helps.

[Tim Chin]

Thank you very much! Any idea if there's a limit on the number of pages that can be scanned? We seem to hit a wall at 18, then at 19 the application crashes. We will try this release and see how it works, thanks!

From: Ben Olden-Cooligan ben-cyanfish@users.sourceforge.net
Sent: Thursday, December 6, 2018 1:06 PM
To: [naps2:tickets] 529@tickets.naps2.p.re.sourceforge.net
Subject: [naps2:tickets] #529 Unable to scan multiple pages

Hi,

I just published a new beta version (6.0b4)https://www.naps2.com/download.html with substantial WIA changes to fix this kind of issue. Please try it and let me know if it helps.

---

[tickets:#529]https://sourceforge.net/p/naps2/tickets/529/ Unable to scan multiple pages

Status: open
Milestone: 5.X
Created: Wed Dec 05, 2018 08:05 PM UTC by Tim Chin
Last Updated: Wed Dec 05, 2018 08:05 PM UTC
Owner: nobody

Hi - I've been using NAPS2 for years, and just got a new MFP unit (Xerox C505) and am using the WIA driver (was originally using TWAIN, but that was crashing so I switched to WIA). At this point, using my ADF, it scans all of the pages through the physical ADF, but only one page of scanned content is showing up in NAPS2. Am I missing a setting somewhere or have something misconfigured so that not all of the pages are scanning? Previously on my old unit, all of the pages would be scanned into NAPS2. Thanks for your help!

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/naps2/tickets/529/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Ben Olden-Cooligan]

There shouldn't be any limit (beyond what your scanner supports). Some of the other changes in the beta might help with that too.

If you still have a crashing issue with 6.0b4, please attach your errorlog.txt file here. You can find it in the "%APPDATA%\NAPS2" folder. For example, if your user name is Tim, it would be in "C:\Users\Tim\AppData\Roaming\NAPS2".

[Patrick Ducourthial]

I had report of a similar issue: NAPS2 crashed when scanning a "large" (20+) number of pages (using the ADF of a Brother MFC).

I tried 6.0b4 using the command line to create a pdf:
- 62 pages went properly through the scanning
- but the "save file" window never showed up (waited 20 or 30 mn)
- at the end of the wait I could see (resmon.exe):
4 NAPS2 worker processes, using 0% CPU but having a varying number of threads (between 8 & 11)
no disc access related to NAPS2
no tesseract processes
62 jpg images in a recovery subdir

I closed (CNTL-C) the command line window and could then recover the scans and save as pdf (4 tesseract processes were visible during this)

Hope this helps

[Ben Olden-Cooligan]

If you use the "-v" option in the command line, it should show additional output. Can you copy and paste the output here so I can see where it's hanging?

[Patrick Ducourthial]

The -v option does not give any info:

"C:\Program Files (x86)\NAPS2\NAPS2.Console.exe" --ocrlang "fra" -p "Scan multipage pdf N&B" -a -v
Beginning scan...
Starting scan 1 of 1...

is all I see in the command window :-(

Please note that the problem doesn't finaly seem to be related to the number of pages scanned: I have the same issue with 4 pages. This is when using a profile with autosave.
When not using autosave, but the -o option, the 4 pages scan works fine (and shows the number of pages being scanned).
Additional info:
4 images are properly created in a recovery subdir (as well as index.xml and .lock)
the NAPS2.Console.exe process seems waiting on itself (see the attached wait chain picture)
when I kill the command I can still see a NAPS2.Worker.exe process through resmon (please note that I did this test after a reboot, but I previously saw several of those "orphaned"? processes)

Hope this helps

[Renjith]

Yes same problem for me also. I used vb's shell function to work with it. After each scan that process is there. It is not killed. Thus system will be hanged.