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

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
StaudteAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jrhelgesonCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
StaudteAuthor Commented:
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
StaudteAuthor Commented:
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.