egascho
asked on
Can't delete print jobs on an HP printer que
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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
Cheers
G
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
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
ASKER
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.
Thanks guys.
Thanks for the feedback, glad you got it sorted - G
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