Service stuck in "Stopping" state

My BackupExec service is stuck in the "Stopping" state and it is just barely
getting close enough to stopping and then it dies with a 1053 error "Error
1053: The service did not respond to the start or control request in a
timely fashion"

I added the registry key to increase the timeout to 120 seconds based on
this link:
http://support.microsoft.com/kb/824344

It requires a reboot to take effect and I really cannot take down this
server during the day.

Is there a workaround to apply this setting or otherwise get this service
into the "Started" state?

Thanks,
JM

 

Hi,

With Process Explorer
(http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/ProcessExplorer.mspx)
you can kill every process even when it's stuck in "stopping" state.

This way you can kill and start the service/process without rebooting your
server.

Floris van Haaster

 

I've had ProcessExplorer for quite some time but was not
aware of this facility. Nice tip coming from Holland!

 

bestop
bestart

 

Cool utility, but when I right click beserver.exe and choose Kill Process I
get "Error terminating process. Access is denied."

Anything else?

Thanks,
JM

 

That's strange... I only get that error on windows services needed for the
computer to keep running...

What you can try is:

Go to the task manager / processes tab, and add the column (view/select
columns) PID.

Then run in dos prompt: taskkill /PID PID /F
replace the second PID with the PID ID like: taskkill /PID 1511 /F

Floris van Haaster

 

That's strange... I only get that error on windows services needed for the
computer to keep running...

What you can try is:

Go to the task manager / processes tab, and add the column (view/select
columns) PID.

Then run in dos prompt: taskkill /PID PID /F
replace the second PID with the PID ID like: taskkill /PID 1511 /F

Floris van Haaster