Can't delete print jobs on an HP printer que

egascho
egascho used Ask the Experts™
on
On a XP workstation computer, we can't print to one network printer (we can to other network printers).

The printer we can't print to, has a number of jobs stuck in the print que - from other workstations.  They do not show these jobs, and they can print fine.

Nobody can delete these jobs.

I have uninstalled the network printer on this workstation and reinstalled it - no luck.

What do do next?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
GRiTechIT Engineer

Commented:
I've found a useful utility for completely resetting the local print spooler to default, cleaning all drivers\registry\ports etc from the local machine.  Might be useful for problem machine with strange printing problems.  Also might need to reboot to finish clearing everything.
 
This tool is part of the xp/2003 resource kit - cleanspl.exe

Try running this and see if it cures it.  You'll need to set up all printers on the workstation zapped.

Could also try a cold reset on the printer just for good measure.

Hope this helps
Cheers
It is generally not a good idea to allow any network user to delete anything off the print queue. It is usually set so that people can only delete their own work from the queue.
GRiTechIT Engineer

Commented:
Totally agree patrick, however if a printadmin uses cleanspl out of the resource kit it can give a totally clean PC to start afresh, just to make sure theres not a corrupt dll or something.

Cheers
G
Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

GRiTech - Thanks for that - patrickab
Most generous as I didn't solve anything really - patrickab
Most generous as I didn't solve anything really - patrickab
GRiTechIT Engineer

Commented:
Yes but your information probably set egascho off on the right track......;o) I guess we'll never know unless egascho tells us more - Cheers G

Author

Commented:
Sorry didn't get back to you all.  The problem ended up being a print driver / issue and something to do with our changing our server IP addresses to the standard addressing scheme (which we did recently). I uninstalled the printers completely from servers and all machines, then reinstalled - now everything is working.  The XP 2003 tools "cleanspl.exe" did zap the printers on the workstation I first had trouble with.  But in the meantime everyone had problems, so I started from strach.

Thanks guys.
GRiTechIT Engineer

Commented:
Thanks for the feedback, glad you got it sorted - G

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial