Service stuck in "Stopping" state

Sponsored Links

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

With Process Explorer
(http://www.microsoft.com/technet/sys...sExplorer.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.

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?

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

[Janos™]

This problem can be solved by downloading a utility to help system administrators diagnose and repair problems with the WMI service. What WMIDiag.vbs does is that it is a VBScript script designed to help you ascertain the current state of the WMI service on a computer. The download package includes the utility itself, a ReadMe file that discusses how the tool works (and how to best use it), and sample spreadsheets that provide information about the default WMI configuration on various versions of the Microsoft Windows operating system. One can easily download it from the microsoft website.