Solved

USB Scanner attached Windows 2008 Terminalserver works for one user, not for another

Posted on 2014-12-29
3
138 Views
Last Modified: 2014-12-30
Hi Experts,

I have a Windows 2008 Terminalserver. Attached to that is a USB document scanner. Drivers are available and installed, the device is visible in device manager. There is one program installed on the server that is supposed to use the scanner's TWAIN interface to scan documents.

Now, here's the funny part: Most users on that terminal server can start the program and it recognizes the WIA source and can scan just fine. Only for one user that program does not see any available scanner sources. So I figure it must be some issue in that user's profile, but haven't found anything about scanners in the HKCU-section.

Note: I have written the program that should scan myself. It's a relatively simple VB application and does nothing overly exciting when listing all available scanner sources. If it works for one user, it should work for all others, too...

Do you have any idea what could make Windows 2008 behave in such a weird way?

Thank you and best regards,
Thomad
0
Comment
Question by:Staudte
  • 2
3 Comments
 
LVL 15

Accepted Solution

by:
jrhelgeson earned 500 total points
ID: 40523600
Are there any entries/error messages in the event log? Failing that, I'd download and run MS Sysinternals "Process Monitor"
http://technet.microsoft.com/en-us/sysinternals/bb896645

I'd monitor file, system and registry activity and compare the results with a working profile.  That should get you pointing in the right direction on where to troubleshoot.
0
 

Author Comment

by:Staudte
ID: 40523615
Thanks for the kick in the butt.... should've thought of that myself ;-)

Indeed, there's a problem with c:\user\faultyuser\windows\twunk_16.exe that can't be started. I'm pretty sure that I just need to delete that file. Don't have time for an in depth-test, but that looks quite promising. I'll check it later and get back to you.

Cheers!
Tom
0
 

Author Comment

by:Staudte
ID: 40523623
Yep, couldn't wait and tested it right away. There were a bunch of TWAIN-related files in the faulty user's Windows directory, none of them were in the working user's one. I removed them all and now it works just fine!

Thanks a lot for the pointer and have a great year!

Tom
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Normally after a failure of Domain Controller, when promoting new DC the DC is renamed, we will discuss the options in Dcpromo to re-create the DC with the same name. Scenario: You are a small IT shop with two Domain Controllers (Domain Contr…
If you migrate a Terminal Server licenses server inside the 2008 server family, you can takte advantage of the build-in migration tool. If you like to migrate an older 2003 Server (and the installed client CALs) to a 2008 R2 server for example, you …
This tutorial will give a an overview on how to deploy remote agents in Backup Exec 2012 to new servers. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as connecting to a remote Back…
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question