Discussion Locked

On a server reboot spooler is hung

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

On ALL of my NT4 machines, I have print queues set up using LPR printing.

Whenever I reboot a server, I have to restart the spooler service and sometimes the TCP/IP Printing service to get printing to work again.

Neither of the services are greyed out. They both appear to be started, but clients can't print, they print and get "PRINTER ERROR OR BUSY" and the queue is stuck.

I have 110 servers that are doing this. It didn't just happen, it's been like that from the get go.

Any ideas? I don't know where to go... Every time I need to reboot, I don't want to have to restart these services all the time. I have tried to give the TCP service a dependency and start before or after the Spooler service and that didn't help either.
Anyone have a clue? I have Jetadmin installed, but even on a fresh NT4 install with just LPR printing it does this. Anyone else have this problem?

HELP!!!!!!!!!

5 replies

by d_v ant

What service pack are you running? I remember a problem with LPR printing that was fixed in Service Pack 3 but I don't remember the details. If you are using a later service pack, try re-applying it and see if that helps.

by sgt_shultz

what is in the event log when the queue hangs?
well this is an awful solution but what about logon batch file...
net stop spooler...
net start spooler
or just change the spooler service startup to manual and batch file just starts it...??

by curlergirl

This is a toughie and could be a combination of printers, print server and network server problems. My experience has been that HP printers on NT4 work better with JetDirect ports than with standard LPR ports (contrary to what Microsoft tells you). However, the same printers on a Win2K network work better with standard TCP/IP printing. So, if you are using exclusively HP printers, I'd recommend getting rid of the LPR ports and TCP/IP printing services altogether and using JetAdmin and the HPJetDirect port software exclusively. However, if these are NOT HP printers, then I'm a little lost. A few troubleshooting ideas: Make sure you are using the most up-to-date printer drivers for your printers. How about firmware upgrades? You could try removing the printer drivers one by one from one of your servers, just to see if there's a particular printer driver that seems to be causing the problems. Hope this helps!

by clint.lechner

It's not a combination of the printer server, printers and network problems. It happens on all 110 server that all have different configurations.

It's definately NOT a specific print driver, as we use a ton of them and they all vary.

This is incredibly frustrating...

This discussion is closed to new replies.