Printer Queues in Server 2008 R2 Print Management Wont't Clear

dcts
dcts used Ask the Experts™
on
I have recently installed the Print Management Role on a Windows Server 2008 R2 server. I have added 5 Sharp Color Copier/printers, and 6 Sharp B/W Copier/printers to the server, and advertised them in the directory. Users have no issues adding and printing to these devices. The problem is, the queue of all of these printers will not clear. The jobs just stay in the print queue for each device, with the status "Sent to Printer," despite the fact that the jobs themselves have already been printed.

There are no jobs on the queue of the local printers, just on the server. I cannot clear the queue by any other methods besides stopping the print spooler service, going to the spool folder in the system32 folder, and manually deleting the queues.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Go to each printer and open the "Printer Properties" .  On the advanced tab clear the checkmark next to "Keep printed documents"

Author

Commented:
The check box is clear, and the queues are still retaining all jobs.
Are you running the most current version of the driver available from the manufacturer of the printer?  Can you duplicate the behavior from a system running no other printers (potential driver conflict pehaps?)  You stated you are running Windows 2008 R2.  Did you get the 64 bit version of the drivers as well as the 32 bit?

Author

Commented:
The drivers that are installed on the server are the most current drivers for the Sharp MX4100-N MFP, and the Sharp M-453N MFP, both x86 (for winxp/vista/7) and x64 (for server 2008)

Author

Commented:
Problem Fixed. The issue was the printers were set up to be Web Services Printers. Once I deleted them, and added them as standard TCP/IP printers, the queues updated as normal.
AH good to know.  You might want to submit a request for a points refund as I didnt really help that much!
I had the same symptoms as 'dcts' except I have TCP/IP printers. I installed all the latest drivers. Some printers had "Sent to Printer" jobs remaining in the queue and some did not. I noticed that the drivers on the problem printers had installed with "Driver Isolation" set to "Shared" by default. The working printers installed with "Driver Isolation" set to "none". Changing the isolation from "Shared" to "None" resolved my issue.

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