Service stuck in "Stopping" state

  • Thread starter Thread starter Joe Murphy
  • Start date Start date
J

Joe Murphy

Guest
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
 
Re: Service stuck in "Stopping" state

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

"Joe Murphy" <spam@spamthis.com> wrote in message
news:uXBZBVg%23HHA.4568@TK2MSFTNGP02.phx.gbl...
> 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
>
 
Re: Service stuck in "Stopping" state

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


"Floris van Haaster" <florisNOSP@Mdatasmit.nl> wrote in message
news:38EF3034-9029-47DD-86B2-14BC59A05E2A@microsoft.com...
> 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
>
> "Joe Murphy" <spam@spamthis.com> wrote in message
> news:uXBZBVg%23HHA.4568@TK2MSFTNGP02.phx.gbl...
>> 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
>>
>
 
Re: Service stuck in "Stopping" state

bestop
bestart


"Pegasus (MVP)" <I.can@fly.com> wrote in message
news:upBVUMh%23HHA.5840@TK2MSFTNGP03.phx.gbl...
> I've had ProcessExplorer for quite some time but was not
> aware of this facility. Nice tip coming from Holland!
>
>
> "Floris van Haaster" <florisNOSP@Mdatasmit.nl> wrote in message
> news:38EF3034-9029-47DD-86B2-14BC59A05E2A@microsoft.com...
>> 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
>>
>> "Joe Murphy" <spam@spamthis.com> wrote in message
>> news:uXBZBVg%23HHA.4568@TK2MSFTNGP02.phx.gbl...
>>> 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
>>>
>>
>
>
 
Re: Service stuck in "Stopping" state

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

"Floris van Haaster" <florisNOSP@Mdatasmit.nl> wrote in message
news:38EF3034-9029-47DD-86B2-14BC59A05E2A@microsoft.com...
> 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
>
> "Joe Murphy" <spam@spamthis.com> wrote in message
> news:uXBZBVg%23HHA.4568@TK2MSFTNGP02.phx.gbl...
>> 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
>>
>
 
Re: Service stuck in "Stopping" state

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

"Joe Murphy" <spam@spamthis.com> wrote in message
news:%23PymA5i%23HHA.4432@TK2MSFTNGP02.phx.gbl...
> 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
>
> "Floris van Haaster" <florisNOSP@Mdatasmit.nl> wrote in message
> news:38EF3034-9029-47DD-86B2-14BC59A05E2A@microsoft.com...
>> 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
>>
>> "Joe Murphy" <spam@spamthis.com> wrote in message
>> news:uXBZBVg%23HHA.4568@TK2MSFTNGP02.phx.gbl...
>>> 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
>>>
>>
>
>
 
Re: Service stuck in "Stopping" state

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

"Joe Murphy" <spam@spamthis.com> wrote in message
news:%23PymA5i%23HHA.4432@TK2MSFTNGP02.phx.gbl...
> 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
>
> "Floris van Haaster" <florisNOSP@Mdatasmit.nl> wrote in message
> news:38EF3034-9029-47DD-86B2-14BC59A05E2A@microsoft.com...
>> 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
>>
>> "Joe Murphy" <spam@spamthis.com> wrote in message
>> news:uXBZBVg%23HHA.4568@TK2MSFTNGP02.phx.gbl...
>>> 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
>>>
>>
>
>
 
Back
Top