Print Spooler constantly failing with error 7031

  • Thread starter Thread starter Ian Furlong
  • Start date Start date
I

Ian Furlong

Every Sunday after our weekly reboot, the print spool
service does not start up. We then go in and manually
start it. It starts ok, but with in 30 seconds to a minute
it fails again. So every single Monday we are stuck doing
this for at least an hour until the spooler finally
decides to stick. I have looked through the knowledge base
and found an article that basically told me the fix was to
install SP4, but that did not help. The problem still
exists. Oh by the way... The OS is W2K with SP4 with
Terminal Services.

Any help would be greatly appreciated.
Thank you
Ian
 
ian, this is somewhat similar to the problem i just
described above. Like you, I have sp4 and have the same
results. But as far as i can tell, my spooler never takes
hold (as i can not print ever, always get the printer not
available message).

I wish i had seen your full thread title before post a
duplicate thread.

Jamie
 
Hi Ian

Which printers are installed - or might be more
interesting - which printer-ports?? It sounds to me that
your problem is caused by some communication errors with
an networked printerport

Kind regards
Thomas Iwang
 
Every Sunday after our weekly reboot, the print spool
service does not start up. We then go in and manually
start it. It starts ok, but with in 30 seconds to a minute
it fails again. So every single Monday we are stuck doing
this for at least an hour until the spooler finally
decides to stick. I have looked through the knowledge base
and found an article that basically told me the fix was to
install SP4, but that did not help. The problem still
exists. Oh by the way... The OS is W2K with SP4 with
Terminal Services.

Any help would be greatly appreciated.
Thank you
Ian
Click to expand...

I had a similar problem with error 7031 for which Microsoft
recommended a hotfix. Instead of the hotfix I went up to SP4 which
did not fix the problem but we are no longer getting 7031 errors
rather 2510 errors which I cannot find any reference for for post NT
systems. One thing I did find, that was when your spooler will not
restart, go into your spool queue directory and delete all the .spl
and .shd files. These are your actual print job spool files. For me
deleting these allowed the spooler to restart. I posted about this
awhile back and one responder suggested I update drivers. I have 30
printers and the problem does not seem to be related to one particular
printer so I am still considering how best to do this.

Hal
 
-----Original Message-----


I had a similar problem with error 7031 for which Microsoft
recommended a hotfix. Instead of the hotfix I went up to SP4 which
did not fix the problem but we are no longer getting 7031 errors
rather 2510 errors which I cannot find any reference for for post NT
systems. One thing I did find, that was when your spooler will not
restart, go into your spool queue directory and delete all the .spl
and .shd files. These are your actual print job spool files. For me
deleting these allowed the spooler to restart. I posted about this
awhile back and one responder suggested I update drivers. I have 30
printers and the problem does not seem to be related to one particular
printer so I am still considering how best to do this.

Hal


.
Click to expand...


That's exactly the same for me. We would have at least a
hundred printers but maybe only 30 different types of
printers.
I can go in and delete the spl files no problem, but I
would rather a more permanent solution. Do any of you use
Terminal Services? We also have Citrix installed...
 
We have this problem with the Kyocera KX Printer drivers. We replace them
with the Hp-PCL 5 Drivers . and the problem go away. Also in our Citrix
Farm.
Please check your Drivers :-)

C. Leclercq
 
Back
Top