NAPS2 not working on Remote Desktop / Twacker finds devices
Scan documents to PDF and other file types, as simply as possible.
Brought to you by:
ben-cyanfish
Menu
▾
▴
1 Attachments
#477 NAPS2 not working on Remote Desktop / Twacker finds devices
Hello,
we are trying to use this software with Remote Desktop solution (Citrix).
Twacker Output find the WIA and Twain non-2.0 devices (see picture).
Also a test SCAN works out of this software.
With NAPS I’m out of luck, it always tells me that there is no devices found (with WIA or TWAIN).
As a starting point to sort something out, I tried the TWAIN combability settings but had no luck with it.
OS is Windows Server 2016.
I didn't find any logfile, it just tells me "No Scanners found".
So Twacker works, but not NAPS2?
Hopefully someone can help me with this.
Best regards
Daniel
Same Her
Any ideas where we can look to get it running?
I can scan with Twacker some demo pages without problem?
Best regards
Daniel
I'm not sure if it is bad or not, there are 2 issues regarding the same topic. But i'll post in both and see who responds. I have the same issue. Any log files that would help anyone determine the issue. I've tried the Old Twain setting, but no luck. All other twain scanning software works correctly. I read somewhere about some software not being terminal services aware and looking for a twain dll file in the wrong spot. Could this be a possiblity?
Update: I've tried almost every portable version (so i don't have to uninstall/reinstall) from 5.8.2 to 4.7.2 , and 4.7.2 is the only one that works. I tried changing to old dsm and legacy in advanced settings on all of them. Any ideas? I really like the fetures provided in the new versions.
Chris (or someone else with the issue), could I get you to try the following?
The old 4.7.2 gave me a few issues with detection, it detected the scanner, then would say scanner not found. But after opening and closing a few times it detected correctly and scanned. I then used the profile data folder built from the old 4.7.2 version in the newer 5.8.2.37279 version like you said to do. This did work and corrected the problem. Do you still want a log, or does this give you a glympse of what the issue may be?
That helps narrow it down. Could you extract the attached test version, run it, select "Old DSM" in a profile, then click the Choose Device button? That should cause an error, then attach the errorlog.txt file from the Data folder here.
It was odd, when I selected the device the program detected the scanner. This is more than it would do before you provided the "test" version in the previous post. It didn't error out and say device not found until I attempted to scan. Then after that, it could not detect the device again and i got a device not detected message everytime. I've attached the error logs. Thank you for your help. I'll provide whatever i can.
Thanks. Could you attach the profiles.xml files from both the test version and 4.7.2?
Wierd. Now I tried the 5.8.2-test and i was able to scan. This is kind of what I think i saw happen to me at one point with 4.7.2. After closing and opening a few times i was able to scan. But when i sent the errors earlier, it detected the scanner but wouldn't scan. Files attached.
Okay. Thanks for the help. As far as I can tell, for you 4.7.2 should work the same as the official 5.8.2 with Old DSM. Perhaps the problem you had was just this same inconsistency?
I don't think I can diagnose that inconsistency any further right now. I'm exploring the possibility of getting myself a Citrix environment to test in to help with that.
In the next version of NAPS2 I will include a fix that will automatically fall back to Old DSM, as well as a possible fix for a slightly different issue from one of the older tickets.
After playing around with it some more. I can't really give you a clear answer, but I don't think the problem is really with a detection issue. I think the problem is with the GUI options not setting things correctly, or maybe not reading something after a change, or maybe a locked file. I have to head out the door, but i can explain further later if you want. Once there is profile it works. Or if i have a newly created profile i have to exit the application and reload it before it actually scans. Or that is the "feeling" i get. Thanks for the help. Does any of my ramblings make sense?
Yeah, I wouldn't be surprised if the driver leaves some kind of leftover resource that isn't cleaned up properly. That makes me think... Try the attached version. It will be generally buggy (it's a work in progress of the next version), but scanning should work. See if that makes any difference. Try both with and without Old DSM.
Last edit: Ben Olden-Cooligan 2018-09-15
After initial testing going back and forth between the stable 5.8.2 portable and the test_nightly, detection is much better. 3 times in a row, the nightly detected the scanner with OldDSM. It did not automaticlly default to this, i had to select it for detection to occur. It appears the changes in the nightly have been for the better. This is with less than 5 minutes of testing. Anything i can provide to help you narrow down the changes that fixed it? Or do you just want to go with the its fixed and not worry about it approach? Thanks for the help in this.
One other question, and i might have to put it in another ticket, but i'm having trouble with detecting a FUJITSU fi-5110C which is using the twain32 9.21.1307 driver. Other model scanners such as the fi-6130 using the same driver detect correctly. So both scanner use the same driver, but for some reason the 5110 goes undetected in any of the versions tested. And after a little more testing, the nightly build provided seems to be pretty good. Thanks again for you hard work on this.
I've published a new version (6.0b1) with the same changes as in the nightly version. I think these changes are the most I can do for now.
Thank you for all your work and help with this. I'll keep an eye out, and send me a PM if you ever want me to test something in a citrix / terminal services enviroment, or with any other OS testing. Scripting to automate tasks is as far as my codeing abbility, so i can't really help in that aspect. But i can test, provide logs, and assist in other ways to help back. This is a impressive project. Thanks again.