Difference between revisions of "Deleting stuck print jobs"

From ISoft Wiki
Jump to navigationJump to search
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
Ever got a print job that just won't go away, no matter how hard you click the delete button?
Ever got a print job that just won't go away, no matter how hard you click the delete button?


Follow these simple steps and you will be back an empty print queue in no time!
Follow these simple steps and you will be back an empty print queue in no time, and it doesn't require restarting the server!


# Stop the print spooler service.
# Stop the print spooler service.
# Delete the .spl and .shd files from %SystemRoot%\System32\Spool\Printers that have the a date modified that is close to the date of said stuck print job.
# Delete the .spl and .shd files from %SystemRoot%\System32\Spool\Printers that have a date modified that is close to the date of the stuck print job.
# Start the print spooler service back up.
# Start the print spooler service back up.
# Tell the user how awesome you are that you didn't have to restart their computer. (Recommended)
# If there are networked printers and stuck print jobs between multiple computers, check \\System32\Spool\SERVERS. You'll find print jobs stuck across the print servers there.

Latest revision as of 11:28, 17 September 2012

Ever got a print job that just won't go away, no matter how hard you click the delete button?

Follow these simple steps and you will be back an empty print queue in no time, and it doesn't require restarting the server!

  1. Stop the print spooler service.
  2. Delete the .spl and .shd files from %SystemRoot%\System32\Spool\Printers that have a date modified that is close to the date of the stuck print job.
  3. Start the print spooler service back up.
  4. If there are networked printers and stuck print jobs between multiple computers, check \\System32\Spool\SERVERS. You'll find print jobs stuck across the print servers there.