Version 3.3.0.28715 on Windows 10 in VirtualBox
Scan documents to PDF and other file types, as simply as possible.
Brought to you by:
ben-cyanfish
Menu
▾
▴
Version 3.2.0 worked in this environment, but Version 3.3 does not. The program runs, but when I select either Quick Scan or Scan nothing happens. That is, the scan button just remains highlighted same as before I selected it. And the scanner does not do anything. NAPS2 gives no indication of any problems i.e. no messages: it just remains open with the same screen displayed that came up when 'scan' is selected from the menu bar.
To verify that some problem did not suddenly appear with the scanner(Kodak i40) when I installed v3.3, I did successful scans with both the Kodak Scan Verification Tool and FreeOCR.
Then I reinstalled NAPS2 version 3.2.0 and it scanned as expected. Following that, I reinstalled 3.3 and the problem is still there.
Thank you for reporting this. I just published a new version that should fix this (3.3.1). Please try that and see if it works.
Thanks for the quick response. With 3.3.1 I now get further and see the "waiting for twain to complete" popup message, but it hangs at that point. The Scanner Properties window also popped up briefly <1 sec and disappeared, leaving the Twain message hanging.
I had to use Windows Task Manager to kill to program after waiting 5-10 min for the scan to start.
As before, I reinstalled 3.2 and scanning worked with no problems.
Could you try a few things to help me figure out the problem?
Since other people seem to be having this issue, I've changed the default download for NAPS2 back to 3.2.1 until I can figure this out.
Last edit: Ben Olden-Cooligan 2015-06-16
Also, I would greatly appreciate it if you could reproduce the issue with this test version and upload the errorlog.txt file here. (You can find that file in the same folder as the EXE after running it.)
Link
Sorry it took a while to get back to you.
In my previous response I might have misled you when I said that the Scanner Properties window popped up briefly but then disappeared. As I was doing additional tests to respond to your questions, I noticed that the Scanner Properties window did disappear as I stated. However, it did not automatically close as I had thought, but it quickly moved to the background. Once I noticed that, I reran the test with the original version of 3.3.1.24448, as follows:
test 1: 3.3.1.24448-original version: Using TWAIN & predefined settings -> when I selected 'scan' from the main menu an error message popped up "An error occurred with the scanning driver". Also, in answer to your question Alt-F4 had no effect.
In answer to your second question, I had not previously tried a test with the 'native UI', so I proceeded to run that test, as follows:
test 2: 3.3.1.24448-original version: Using TWAIN & native UI -> Scanner Properties window opens and quickly moves to background so is hidden behind the main NAPS2 window. Also, a "waiting for TWAIN to complete..." message is displayed in the foreground. Moving the Scanner Properties window to the foreground and selecting 'scan' results in the scan occurring followed by the popup error window "An error occurred with the scanning driver". No image is ever displayed throughout the test. I clicked "OK" to close the error window and noticed the Scanner Properties window had again moved to the background. Moving it to the foreground, I clicked 'stop' but the window continued to display 'Scanning...'. I was able to 'cancel' the window and then tried another scan.
The document was scanned with exactly the same results as in the first pass. I tried two more scans with the same result. On each scan the "Total Bytes" count increased. At that point the Scanner Properties window became unresponsive and I had to kill the process using Task Manager.
In answer to your third question, I did not try NAPS2 on a different version of windows, only Windows 10.
You also asked me to run 3.3.1-trace. I did that and have attached the log file. Let me know if you need anything else. I ran two tests: with the Predefined settings and with the Native UI, as follows:
test3: 3.3.1-trace: Using TWAIN and predefined settings. The first difference I noticed between this and the earlier tests is that when I selected 'scan' a "Select Source" window popped up and displayed my scanner's name. I selected the scanner and immediately got the error window "An error occured with the scanning driver". I selected OK to close that window then selected Scan again with the same result. Then I selected 'done' to end the test and then closed the application.
test 4: 3.3.1-trace: Using TWAIN and native UI. Selected the scanner from the Select Source window the selected 'scan'. The results looked same as test 2, but this time the application hung on the first scan.
None of the four tests resulted in a displayed image.
Thanks for all of that. Could you try and attach the log file again? I don't see it on your post.
Sorry, forgot to attach it. Here it is.
Okay, based on the log I think I've identified the issue (a bug in the TWAIN library that I just started using in NAPS2 3.3). I've contacted the library author to fix the issue, and if I'm right, will hopefully have a fix ready for you to test within the next few days.
Actually, I went ahead and got something for you to test right now. Please download the following file and use it to replace the existing NTwain.dll file in the 3.3.1-trace folder you used before. Then run the NAPS2.exe file in that folder and see if the issue is fixed (or changed in any way). If it is not fixed, please re-attach the errorlog.txt file.
Link
Last edit: Ben Olden-Cooligan 2015-06-20
Downloaded and replaced NTwain.dll file. I had some success with scanning now, but there are still some issues. See following tests and attached log. OCR was not selected for the tests.
test1: predefined interface.
select 'scan' from menu bar on top
choose Profile window opens
select 'manage profile and set to predefined interface-> select 'ok'
select 'scan' in Choose Profile window
scanner feeds paper after short delay
black rectangle appears (looks like the 'waiting for TWAIN...' popup but is all black). That popup persists with the Windows 'working' indicator (blue circle). After a minute or so, decide to click on it and get a Windows popup with message "NAPS2 is not responding". Then choose the option to 'close the program' to kill the application.
restart NAPS2 and get option to recover the image. Selected that option and image is successfully recovered and displayed as thumbnail in the NAPS2 main window.
save as pdf -> 65KB
close NAPS2
test 2: native UI
select 'scan' from menu bar on top
Choose Profile window opens
Select 'manage profile and set to native interface-> select 'ok'
Select 'scan' in Choose Profle window
Scanner Properties window open and immediately goes to background - behind main NAPS2 window. "Waiting for Twain..." message appears in foreground.
move Scanner Prperties window to foreground and select 'scan'
Scanner feeds paper and image thumbnail appears in main window.
Select 'done', then 'Save PDF'. Seems to work smoothly and produces the pdf file.
save as pdf -> 965KB
Okay, looks like this is a separate issue. At least we fixed the first one. Please try this version, which could fix this second issue, and in either case please attach the errorlog.txt file which should give me some more information as to why this occurred.
Link
Downloaded NAPS2 3.3.1-rev2, extracted and ran version 3.3.1.22832. See tests below. OCR was not selected for the tests.
test1: predefined interface.
• select 'scan' from menu bar on top
• ‘Choose Profile’ window opens
• select 'manage profile’ and set to predefined interface-> select 'ok'
• select 'scan' in Choose Profile window
• Scanner feeds paper and image thumbnail appears in main window. Also, black rectangle appears for a couple seconds then disappears (looks like the 'waiting for TWAIN...' popup box geometry but is all black).
• save as pdf
• close NAPS2
• Test was successful. Only issue seen is an obscured ‘waiting for TWAIN…’ message.
test 2: native UI
• select 'scan' from menu bar on top
• ‘Choose Profile’ window opens
• Select 'manage profile’ and set to native interface-> select 'ok'
• Select 'scan' in Choose Profile window
• Scanner Properties window open and immediately goes to background - behind main NAPS2 window. "Waiting for Twain..." message appears in foreground.
• move Scanner Properties window to foreground and select 'scan'
• Scanner feeds paper and image thumbnail appears in main window.
• save as pdf
• Test was successful. Only issue seen is the hidden Scanner Properties window.
Thanks for addressing the issues so quickly. Let me know if you need any additional tests run. errorlog.txt file is attached.
Awesome. Thanks for you help with this, I'm sure it will benefit a number of users. I'll have a look at those two minor things tomorrow and see if there's anything I can do about them. In the meantime the fixes from the most recent test are already published in version 3.3.2.
Okay, I think I know what's causing those two issues. Please try this and see if it fixes them:
Link
v3.3.3 appears to have fixed both problems:
test1: naps2-3.3.3,TWAIN,predefined.
Now displays the 'waiting for TWAIN...' message (good) and scan is successful as in previous tests.
test2: naps2-3.3.3,TWAIN,nativeUI.
The Scanner Properties window opens after the 'waiting for TWAIN...' message as before, but now it stays in the foreground (good) and scan is successful as in previous tests.
No errorlog file was produced.
Looks good to me. Thanks, let me know if you need additional info.
The fix has been published in version 3.3.3. There shouldn't be anything else I need from you (unless you come across another issue of course).
Thanks again.
Hello Ben,
I am using naps.console.exe - 5.3.3 and the issue is same. Scan gets over but the message "waiting for TWAIN to complete" never goes away. I have to end the process by task manager.
Once I am ending the process from task manager then it works fine for all the later scans till I restart the machine. After I restart my machine, this issue comes again for the first time.
I am using HP scanjet 3000 s3 scanner and issue comes on very few machines. On most of the machines it works perfectly fine.
Let me know if any more details I can provide. Thanks :)
As of recent I've been recieving the same thing. It was working 100% previously. Ending the process via Task Manager and relaunching retrieves previous scans but the next batch of scans hangs once again. If I don't end the process, after a while Window reports that NAPS2 is not responding.
I've discovered that it works fine at 150dpi but hangs at 300dpi
Last edit: William Porto 2018-05-06
Resolved. Feeder vs Glass. I was using a document scanner and not a flatbed, but the profile for 300dpi was set to glass.