Re: Cannot Get Xerox Network Scanner To Work
- From: bs_spam_30611749@xxxxxxx
- Date: 28 Dec 2006 23:09:20 -0800
Hi Kelvin,
I had the same problem with WinXP and an Epson 1240U scanner.
Found the solution at
http://groups.google.com/group/microsoft.public.office/browse_thread/thread/33cc1c96634bfd21/8e7d480c29115447.
I added the specified files to the DEP exclusion list and the problem
was solved.
Just another example of our friends at Micro$oft releasing s/w without
testing it.
Good luck!
Bob
On 14 Nov, 23:58, Kelvin <Kel...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi,
We put in a new Windows 2003 Terminal Server into a client's network. We
can't seem to get the Xerox Network scanner software (Network Scanner
Utility2) to work. Using Microsoft Office Document Scanning produces the
error message "The scan failed because of a scanner hardware error. Feeder
may be jammed. Please correct the error and scan again." However, the Xerox
Mailbox Viewer2 program (a standalone program that allows users to access the
scanned documents on the network scanner) works without a hitch. The problem
is, this is very inconvenient as they are not able to scan directly into
their Twain aware software (the Microsoft Document Scanning is one of the
software used) and have to save the files out from Mailbox Viewer2 before
importing them into their applications.
Xerox confirms that the version of the driver in use supports 2003 Terminal
Services. In fact their tech support reckons they have tested it themselves
and have not come across any problems.
Some background :
We initially put in a loan server at the client's running the 180 day
Evaluation version of Server 2003 (32 bit) in Terminal Services mode. We
encountered the problem with the driver then and try as we might we could not
get the driver to work. Xerox still says they cannot replicate the problem at
their end. Customer decided that since this is an evaluation server, they
will put up with the 2 step process until they decide on purchasing a
permanent terminal server.
A little way into the eval, they decided to try the 64bit version of 2003
Server in Terminal Services mode as well. So, we put in another loan server
with the 64bit eval Server 2003 in TS mode. The network scanner driver worked
flawlessly under this server ! If anything, we were expecting issues with it
under the 64bit OS.
At the end of the eval, the client decided to put in a brand new TS running
the 32 bit Server 2003 (due to lack of vendor support for their various
industry specific applications). This new server is an Intel based (dual
Xeon) server while the loan servers were single processor AMD64s, so the
hardware is totally different. However, the same problem with the Scanner
driver has come back with this new server ! Xerox still says they have no
problem !
We have loaded and unloaded the drivers many times with no success and
cannot see any reason why the driver will not work. The installation sequence
and method is the same each time, yet it works on the 64 bit eval server but
not on the 32 bit ones.
Can anyone else suggest where else to look ? What is the mechanism involved
in getting a Twain aware application to recognise and work with Twain drivers
? We think the process is falling down somewhere at this point.
Any help greatly appreciated
.
- Prev by Date: Re: Migrate "Documents and Settings" folder from one drive to another
- Next by Date: Re: How to make the client network printer name shorten?
- Previous by thread: Re: Cannot Get Xerox Network Scanner To Work
- Next by thread: Re: outlook won't recieve messages automatically
- Index(es):
Relevant Pages
|
