Home > IT Answers > Microsoft Windows > Unable to delete stuck print jobs
Help

Question

  Asked: Nov 13 2007   7:04 PM GMT
  Asked by: CGCAdmin

Unable to delete stuck print jobs


Printing, Spooling, VMware ESX

I recently created a new print server for our campus. It is a Windows 2K3 R2 system running in a VMWare ESX Server. All of my print devices are various HP models from a 5M to brand new 4250's. All are connected to the server via HP port monitors and all of the drivers are the latest available from HP.

I am experiencing a unusual amount of jobs getting stuck in a several of the print queues and, even worse, I am unable to delete any of the stuck jobs without restarting the spooler.

I have tried deleting one of the offending queues and recreating it with freshly downloaded drivers from HP to no avail.

I have also read of a known problem where an RDP session that maps a local printer to the server can cause this but have been able to rule this out.

Any other ideas on how to reduce the number of stuck print jobs as well as fixing the spooler so that jobs that do get stuck can be deleted properly?

S

Subscribe to Alerts! Get questions and answers delivered to your Inbox.


E-mail me updates on this question



   SUBSCRIBE

hidden modal window
Help

Answer Wiki (Improve, edit or add to this answer)

IMPROVE THIS ANSWER
View History
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
Last Answered: Nov 14 2007  5:41 PM GMT  by KarlG




How are you doing on space on the server? And memory? Both of these can effect the job spooling to completion. Do you have security configured for this printer? Via Active Directory?

How about the error log - is anything showing up?
  • AddThis Social Bookmark Button

Browse more Questions and Answers on Microsoft Windows and Virtualization.

Looking for relevant Microsoft Windows Whitepapers? Visit the SearchEnterpriseDesktop.com Research Library.


RSS - Discussions Help

Discuss This Answer


You must be logged-in to discuss a question. Log-in/Register

B00M3R  |   Nov 14 2007  7:03AM GMT

S when u find the answer to this post it its a common thing and i experience ot too.

 

CGCAdmin  |   Nov 15 2007  4:05PM GMT

Spool directory is in the default location and there is approx. 8 GB free on the drive. VMWare is configured to allocate 1 GB of RAM to the VM. The server and users are in AD but the default security permissions have not been altered.

Since my last post I found someone with the same issue who solved it by reverting back to Microsoft “Standard TCP/IP ports” instead of the “HP Standard TCP/IP ports”. I did this for the two queues that were experiencing this issue most often and, although it is too early to tell for sure, I haven’t had the issue recur on either of them yet. I’ll keep monitoring them for another week.

S