Print jobs delete themselves before printing

Question

_{Saturday, February 5, 2011 3:41 PM | 1 vote}

I have a laptop running XP and a Xerox network printer. When printing, jobs get spooled and then delete themselves before printing. This happens when trying to print from all applications. Has anybody seen this before or have any suggested solutions?

All replies (5)

_{Sunday, February 6, 2011 1:11 AM ✅Answered}

Look for the error generated in the event log on the failure.  The error will hopeful contain enough information to get you in the right direction. Alan Morris Windows Printing Team

_{Sunday, February 6, 2011 8:59 PM}

saw this symptom many years ago, when spooling a PostScript job, to a non-PostScript capable printer.
the server spooled the job successfully to the printer, the printer accepted the job, then discarded it, as the PS personality was not installed.
unlikely in today's environment, but confirm that the printer driver you've selected matches the printer capabilities.
examine the event/job logs and/or display panel of the printer to confirm the job is reaching the printer.tesgroup

_{Friday, March 16, 2012 3:23 PM}

I am having this same problem except I am working with Windows 7 x64 Enterprise. All of the printers are deployed via group policy and all printers exhibit the same problem when trying to print from that machine. Print jobs are deleted before being sent to the print server. 

There was an instance where I logged in with my test account and let the printers populate from group policy and I was able to print from that account, but not from any other account that I had previously logged in with. I logged off of that test account and then logged back in and was then unable to print...

Thanks in advance for any help you can provide!

This is the error message I receive in the logs below. I removed the machine name and the location from which the job came from. Where it came from doesn't seem to matter because it does it from all programs I have tried to print from.

Error Message:

The description for Event ID 372 from source Microsoft-Windows-PrintService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

"location from which print job came and username associated with the print job"
NT EMF 1.008
351936
0
2
0
\"machinename"
5
Access is denied.

The handle is invalid

_{Friday, March 16, 2012 3:49 PM}

Change the spool file location on the print server out of \system32\spool\printers.  Or you can change the default security for this directory but it's just a better idea to move the spool directory.  It's an Advanced setting on the Print Server properties page from printmanagement.msc

I normally drop to a disk other than the system drive but c:\spool will work as well.

Alan Morris Windows Printing Team

_{Monday, March 19, 2012 4:46 PM}

I have some reservations about doing that on our print server at the moment. Will this disrupt printing for other users? I will be in a hole mess of trouble if I end up making printing unavailable for the other 200+ users. 

What would I have to do change for the default security to make this work for the one machine that is having the issue?