Re: Track Down Print Job Crashing Spooler
- From: "Alan Morris [MSFT]" <alanmo@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 29 Nov 2005 09:07:51 -0800
Hi Bruce. I have a process that is too much to explain in this forum. The
driver developers like my process since once I have the offending file
I can easily recreate the failure on any machine. It makes debugging easy
and it also makes verification simple that the driver fix corrects the
issue.
contact me and I'll give you the specifics. You will need a machine to move
all the existing spool files to rather than deleting them. Preferable one
that is running the same OS / SP and security patches that the print server
is running
alanmo@xxxxxxxxxxxxx
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bruce Duncan" <bduncan@xxxxxxxxxxxxxxx> wrote in message
news:1133202400.515865.6970@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Periodically a specific print job will crash the spooler service. We
> have to open the spooler folder and delete all the contents before
> restarting the print spooler service. Ideally we'd like to be able to
> identify the owner of the jobs in the spooler folder so we can track
> down the print job responsible for crashing the service. Is there any
> way to do this?
>
.
- Follow-Ups:
- Re: Track Down Print Job Crashing Spooler
- From: Christoph Lindemann
- Re: Track Down Print Job Crashing Spooler
- References:
- Track Down Print Job Crashing Spooler
- From: Bruce Duncan
- Track Down Print Job Crashing Spooler
- Prev by Date: Track Down Print Job Crashing Spooler
- Next by Date: Re: Track Down Print Job Crashing Spooler
- Previous by thread: Track Down Print Job Crashing Spooler
- Next by thread: Re: Track Down Print Job Crashing Spooler
- Index(es):
Relevant Pages
|