Difference between revisions of "Deleting stuck print jobs"
From ISoft Wiki
Jump to navigationJump to search
Daytonlowell (talk | contribs) (New page: 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! 1. Stop the p...) |
|||
| (7 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, and it doesn't require restarting the server! | |||
# Stop the print spooler service. | |||
# 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. | |||
# 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!
- Stop the print spooler service.
- 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.
- 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.
