stuck print jobs 1

[itfellow]

I have an office full of PCs using Windows XP SP1, all of which have installed HP laserjet 4000 network printers. However, whenever a print job is sent from PC #1, that print job prints properly but then remains in the print queue with the description "sent to printer". When PC #1 is rebooted, as soon as it comes online it prints the job again and the job remains in the queue with status "sent to printer".

I have tried re-installing the printer using the same driver that all the other PCs use, with no succes. I logon with an account that has admin rights on the PC and the jobs still get stuck.

Any suggestions? Thanks.

 

[KenB]

http://searchwinsystems.techtarget.com/tip/1,289483,sid68_gci955386,00.html

Try this Tip.

HTH
Ken

 

[itfellow]

Yes, I don't have a problem clearing the jobs out once they are in there. The problem is that all jobs for this printer get stuck every time. The user of this PC is currently having to clear the queue each day before she shuts down. If she forgets, the PC starts printing all jobs again as soon as it boots up. What should be happening is the jobs print, then clear out of the queue automatically. That is what I am trying to make happen.

 

[linney]

There is a batch file at the end of this first article that you might be able to use as a workaround?

More Print Queue Tricks

http://langa.com/newsletters/2006/2006-03-06.htm

cancelled print job won't go away & holding queu hostage
thread779-642863

Have a look around this site too.

http://members.shaw.ca/bsanders/CleanPrinterDrivers.htm

Some suggestions from

http://www.experts-exchange.com/Operating_Systems/WinXP/Q_21034681.html

"check that "keep printed documents" is switched off in printer properties - advanced tab.

You need to disable (uncheck) Bi-directional support.
Untick the bi-directioanl support"

 

[tfg13]

I think linney hit it on the head with the "keep printed Documents" check box on the advanced tab. I just tried it, and it does as described above....

Star is on it's way linney!

 

[itfellow]

For me, unchecking the box for bi-directional support did the trick. I'm not sure why this particular PC needed that to be done while the others have no problem, but it worked.