Print Spooler

  • Thread starter Thread starter Peter Ellison
  • Start date Start date
P

Peter Ellison

Hi

I have XP pro client and 2000 server
Printer connected to server
After printing from client
The spooler continues to generate network traffic until I stop and restart
the spooler service
any ideas.

Thanks in advance
 
I have the same problem it appears. Using Win XP Pro. I
installed existing drived in a new notebook chassis and
when I booted, I get msg that new hardware had been found
so I accepted help from wizard. But it failed and I get
msg
My original description:
Received replacement chassis this afternoon. Amazingly
they left it at
the
front door and were leaving when I got to the door.

Anyway, there were no instructions on replacing drives
but I found the
tab
for the CD RW drive and the 3 1/2" diskette, and,
finally, found the
hard
drive below the CD RW drive.

When I booted the replacement chassis with old drives
installed, it came
up
but I received a message saying the Network Connection
needed to be
established and the Network Wizard would help me. The
Wizard
recommended a
LAN connection. I didn't remember what I had on the old
chassis, so I
accepted it. (I am back on the original chassis as I
write to you now.
I
am auto-configured, connected directly to the Internet
through
BrightHouse
Cable Road Runner.)

Then I received an error message: szAppName spool.exe
failed, szAppVer
5.1.2600.0, szModName ntdll.dl, szModVer 5.1.2600.1217
offset 0002c32b.

The Wizard failed to configure and the Notebook
recommended that I
restart
which I replied OK to. I don't understand why I received
this message
or
even why a Network Wizard popped up. I had the same disk
content as in
the
original chassis.

I expect this error has to do with printer spool as a
part of NT access
method.

Now I cannot print at all. I have deleted the printer
and reinstalled a downloaded driver from Epson C82 series.

When I try to print, it tries "checking printer status"
and "spooler" flashes and then noting happens except the
sequence continues ad nauseum.

I also sent an error msg to MS to no avail.

If I find something, I will let you know...
 
Back
Top