jmahlmann
asked on
service is in stopping mode
How do I force a stop for a service that just says stopping? I'm on server 2003 r2 32bit.
Jamie Gillespie
Which service is it?
Go to the command-prompt and query the service (e.g. the SMTP service) by using sc:
sc queryex SMTPSvc
This will give you the following information:
SERVICE_NAME: SMTPSvc
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE, PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
PID : 388
FLAGS :
or something like this (the "state" will mention stopping).
Over here you can find the process identifier (PID), so it's pretty easy to kill the associated process either by using the task manager or by using taskkill:
taskkill /PID 388 /F
where the /F flag is needed to force the process kill (first try without the flag).
Please be careful when you do this; it's useful for emergencies but you shouldn't use it on a regular basis (use it as a last chance to solve the problem or to avoid the need of a reboot in an exceptional situation). It can even be used to stop a service that has the "NOT-STOPPABLE" and/or "IGNORES_SHUTDOWN" flag set (e.g. Terminal Services on a Windows Server 2003 is non-stoppable), at least when it's not hosted in the system process. You can query all this information by means of the sc command.
sc queryex SMTPSvc
This will give you the following information:
SERVICE_NAME: SMTPSvc
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 4 RUNNING
(STOPPABLE, PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
PID : 388
FLAGS :
or something like this (the "state" will mention stopping).
Over here you can find the process identifier (PID), so it's pretty easy to kill the associated process either by using the task manager or by using taskkill:
taskkill /PID 388 /F
where the /F flag is needed to force the process kill (first try without the flag).
Please be careful when you do this; it's useful for emergencies but you shouldn't use it on a regular basis (use it as a last chance to solve the problem or to avoid the need of a reboot in an exceptional situation). It can even be used to stop a service that has the "NOT-STOPPABLE" and/or "IGNORES_SHUTDOWN" flag set (e.g. Terminal Services on a Windows Server 2003 is non-stoppable), at least when it's not hosted in the system process. You can query all this information by means of the sc command.
ASKER
Acronis Managed Machine Service
That is the service and I type that it and it keeps telling me there is no service.
That is the service and I type that it and it keeps telling me there is no service.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yeah. That is what I was going to do, but I have to wait till tonight.
Yes, make sure that no one is working and send earlier some info that you are going to reboot server at... and it will be unavailable for ... minutes, please close and save you data to prevent its loss
Just in case to be able to explain your boss that it was planned and users were informed :)
Krzysztof
Just in case to be able to explain your boss that it was planned and users were informed :)
Krzysztof
(NOTE: What follows is purely for comedic relief. The author assumes no responsibility for damages or loss if you decide to act on this post.)
Or, you could do what one of our (former) entry-level NOC technicians did - just pull the plug! Much quicker and easier than all that pesky policy/procedure and graceful shutdown malarkey. *face palm*
Me: "Do you have anything to say to possibly explain why you thought this was OK?"
Tech: "Well...I did have a brain injury as a child that affects my short-term memory. That's why I take so many notes."
Me: "..."
Tech: "I've had six brain surgeries."
Me: "..."
Or, you could do what one of our (former) entry-level NOC technicians did - just pull the plug! Much quicker and easier than all that pesky policy/procedure and graceful shutdown malarkey. *face palm*
Me: "Do you have anything to say to possibly explain why you thought this was OK?"
Tech: "Well...I did have a brain injury as a child that affects my short-term memory. That's why I take so many notes."
Me: "..."
Tech: "I've had six brain surgeries."
Me: "..."
ASKER
Had to shut down.