Attempting to delete a print job sitting on one of my network printers has created the 'Deleting - printing' error, where the job won't delete. I have tried the usual things such as starting and restarting the Print Spooler to no avail. The job just won't go away. Googling shows that some people have succeeded in clearing problem print jobs, but nothing has worked for me so far.
Any ideas on clearing this print job would be gratefully received.
Have the owner of the job delete it
Thanks for the replies, but I have tried everything. I am hoping that someone has a way of getting rid of a print job that won't respond to the usual deletion methods. I am the owner of the job but cannot zap it.
Use Windows (file) Explorer to navigate to here:
C:\Windows\System32\spool
Select* and delete the folder named PRINTERS.
*Select via single click or you might see this:
If you see that, select Continue and then delete the folder named PRINTERS.
Restart the computer and the folder should automatically be recreated with the correct NTFS file permissions.
If those steps fail, there are stronger methods to delete folders.
Last edited by UsernameIssues; 30 Oct 2015 at 04:16.
Is the print job stuck at the printer or hanging in the server? What is the printer make and model? Does the printer also have a stand alone server attached? Some high end printers use devices like Fiery or ImagePass
Can you access the printer via a web browser interface and view the print queue from there? See below. You also can access Admin Mode from web interface.
Attachment 374796
Last edited by cyclops; 30 Nov 2015 at 09:55.
Many thanks, UNI. Deleting the PRINTERS folder did it. I now know what to do if this sort of thing reoccurs.
Thanks also, Cyclops, but I have a simple wired network that usually works perfectly with printer sharing. This seems to have been a rare glitch. My wife sent something to one of my office printers because her printer needed some ink replacement. Usually I don't get involved in her printing.
Glad that it worked out for you
Hey stony41, good for you. Now I am going to beat this horse a little more. Based on the last statement about your wife sent the print job to your office printer, do you think authentication issues may have started this?
Quote