Really stopping Spoolsv.

[Guest Patrick]

Lately we have had an issue with our 2k3 R2 file and print server. Users

sometimes print something that cause the printer to hang. If I go into

services and stop the printing spooler, it will show stopped. However the

spoolsv.exe is still in memory. If I try to Kill that instance via kill and

its PID, nothing happens the Service and PID stay in the processes tab. If I

restart the printer service, a new spoolsv.exe instance with a new PID starts

and the old one is still there as well. I cannot delete the offending spools

files from the spool directory either, as the unkillable spoolsv.exe instance

seems to have them locked. They only way I found to resolve the problem it

to reboot the server. Which is inconvenient to say the least. Has anyone

had this problem? This is the first time I've run across a PID that Kill.exe

or tskill could not terminate for me.

 

Any suggestions would be great- Thanks

Patrick

[Guest Pegasus \(MVP\)]

Re: Really stopping Spoolsv.

 

 

"Patrick" <Patrick@discussions.microsoft.com> wrote in message

news:56572DAF-FE72-4F49-8C2A-089F7208871D@microsoft.com...

> Lately we have had an issue with our 2k3 R2 file and print server. Users

> sometimes print something that cause the printer to hang. If I go into

> services and stop the printing spooler, it will show stopped. However the

> spoolsv.exe is still in memory. If I try to Kill that instance via kill

> and

> its PID, nothing happens the Service and PID stay in the processes tab.

> If I

> restart the printer service, a new spoolsv.exe instance with a new PID

> starts

> and the old one is still there as well. I cannot delete the offending

> spools

> files from the spool directory either, as the unkillable spoolsv.exe

> instance

> seems to have them locked. They only way I found to resolve the problem

> it

> to reboot the server. Which is inconvenient to say the least. Has anyone

> had this problem? This is the first time I've run across a PID that

> Kill.exe

> or tskill could not terminate for me.

>

> Any suggestions would be great- Thanks

> Patrick

 

Have you tried taskkill.exe /f? What response do you see?

[Guest Patrick]

Re: Really stopping Spoolsv.

 

Thanks for the reply. No I didn't try taskkill. I will next time it happens

though and see if it makes a difference.

 

Patrick

 

"Pegasus (MVP)" wrote:

>

> "Patrick" <Patrick@discussions.microsoft.com> wrote in message

> news:56572DAF-FE72-4F49-8C2A-089F7208871D@microsoft.com...

> > Lately we have had an issue with our 2k3 R2 file and print server. Users

> > sometimes print something that cause the printer to hang. If I go into

> > services and stop the printing spooler, it will show stopped. However the

> > spoolsv.exe is still in memory. If I try to Kill that instance via kill

> > and

> > its PID, nothing happens the Service and PID stay in the processes tab.

> > If I

> > restart the printer service, a new spoolsv.exe instance with a new PID

> > starts

> > and the old one is still there as well. I cannot delete the offending

> > spools

> > files from the spool directory either, as the unkillable spoolsv.exe

> > instance

> > seems to have them locked. They only way I found to resolve the problem

> > it

> > to reboot the server. Which is inconvenient to say the least. Has anyone

> > had this problem? This is the first time I've run across a PID that

> > Kill.exe

> > or tskill could not terminate for me.

> >

> > Any suggestions would be great- Thanks

> > Patrick

>

> Have you tried taskkill.exe /f? What response do you see?

>

>

>