Service stuck in "Stopping" state

Discussion in 'Windows Server' started by Joe Murphy, Sep 18, 2007.

  1. Joe Murphy

    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
     
    Joe Murphy, Sep 18, 2007
    #1
    1. Advertisements

  2. Floris van Haaster, Sep 18, 2007
    #2
    1. Advertisements

  3. I've had ProcessExplorer for quite some time but was not
    aware of this facility. Nice tip coming from Holland!
     
    Pegasus \(MVP\), Sep 18, 2007
    #3
  4. Joe Murphy

    JB Guest

    bestop
    bestart


     
    JB, Sep 18, 2007
    #4
  5. Joe Murphy

    Joe Murphy Guest

    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
     
    Joe Murphy, Sep 18, 2007
    #5
  6. 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
     
    Floris van Haaster, Sep 19, 2007
    #6
  7. 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
     
    Floris van Haaster, Sep 19, 2007
    #7
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.