Windows Forum

Ask something
Discussion Locked

Print jobs stay in queue

0 helpful
17 replies

by spank

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have an HP4000 printer set up on my network that is connected to a jetdirect print server. When a user sends a print job to the server, the job prints but stays in the queue. Eventually the queue gets VERY full and will not accept any more printjobs. I have 3 other HP4000's on the network and none of the others have this problem. I have been unable to find a resolution on HP or Microsoft's website. Any help would be appreciated. Thanks.

17 replies

by olisao55

This is not a fix, but is a very handy tool that can be ran automatically. Copy and paste this in to a batch file and it will automatically start and stop the print spooler.

net stop spooler
echo y | del w:\winnt\system32\spool\printers\*.*
netstart spooler

by spank

I'd rather fix the problem than treat the symptom. Thank you for your input though.

by mattl_rf

Try this, go to the properties of your printer. Go to the advanced tab and see if keep printed documents is checked.

by mcorr

We just bought some Jet Directs, and haven't had the problem you mention.

My first guess would be incorrect printer drivers on one or more PCs. Does the same job always get hung? The same PC/user's print jobs? What does the printer status window say?

by jlaar

First check if the ip-address of the printer and the queue match or if the printer even has an ip-address (or has a networkconnection!!). If so delete the queue and create a new one (with the same configuration). It should work now.
Testing for ip and connection can best and quickest be done by printing a configuration page from the printer itself.

by hazzard_005

Sounds like a registry snaffoo. Try checking the keep documents after they have printed and click ok. Then go back into the printer properties and uncheck it. See if that resets the registry entry.

Hope this helps.

by mike @ motorola

Here's the Key path to check. I also agree that this seems to be a registry glitch. Have you tried deleting and recreating the print queue? Is this an external print server? Double check your settings on the print server to ensure proper configuration. Has it ever worked properly? Try switching with a known good one temporarily and see if the problem clears or moves...

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers\(Printer Name)\DsSpooler

If it is set to other than 00 than it is set to hold jobs.

Hope this helps.

Sincerely,

Mike Pedigo

This discussion is closed to new replies.