none
Error 1053: The service did not respond to the start or control request in a timely fashion

    Question

  • Hello friends :

    I have a problem with starting my windows time service an i get this error every time i try to start the service :
    "

    Error 1053: The service did not respond to the start or control request in a timely fashion


    1-I restarted the server
    2-I changed the Parameters in the registry to NT5DS and the NTP server to " My domain.local "
    3-I want to use an internal Time server
    4-I configured the domain group policy settings to enable NTP and configured them to use my domain.local as their  NTP server

    What should i do and how can i solve it ?
    Network is my LOVE
    Saturday, August 29, 2009 5:18 AM

Answers

  • Hi Mohammad,

    Please check to see if the resolution in this KB is helpful.

    FIX: You receive an "Error 1053: The service did not respond to the start or control request in a timely fashion" error message when you stop or pause a managed Windows service
    http://support.microsoft.com/kb/839174

    Thanks.

    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Proposed as answer by David Shen Monday, August 31, 2009 10:37 AM
    • Marked as answer by David Shen Saturday, September 05, 2009 9:42 AM
    Monday, August 31, 2009 10:35 AM
  • I have de same problem...

    I'm using service pack 2 and microsoft netframework 2.0 the hotfix from http://support.microsoft.com/kb/839174 is only for version 1.1

    but my service not started =(

    someone has an idea?




    ############################

    My problem has solved...

    I detect a missing library (mfc71u.dll), i put this dll in dir C:\Windows\system32 and my services already running

    I hope this solve your issue.


    Please enter this link and register your figther

    http://www.kobox.org/kobox-fande-Sergios.html


    • Proposed as answer by Serch79 Thursday, September 17, 2009 10:28 PM
    • Marked as answer by David Shen Monday, September 21, 2009 2:34 AM
    Thursday, September 17, 2009 5:11 PM

All replies

  • Hi Mohammad,

    Please check to see if the resolution in this KB is helpful.

    FIX: You receive an "Error 1053: The service did not respond to the start or control request in a timely fashion" error message when you stop or pause a managed Windows service
    http://support.microsoft.com/kb/839174

    Thanks.

    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Proposed as answer by David Shen Monday, August 31, 2009 10:37 AM
    • Marked as answer by David Shen Saturday, September 05, 2009 9:42 AM
    Monday, August 31, 2009 10:35 AM
  • I am using the latest service pack , but i still have the problem
    Network is my LOVE
    Saturday, September 05, 2009 10:01 AM
  • I have de same problem...

    I'm using service pack 2 and microsoft netframework 2.0 the hotfix from http://support.microsoft.com/kb/839174 is only for version 1.1

    but my service not started =(

    someone has an idea?




    ############################

    My problem has solved...

    I detect a missing library (mfc71u.dll), i put this dll in dir C:\Windows\system32 and my services already running

    I hope this solve your issue.


    Please enter this link and register your figther

    http://www.kobox.org/kobox-fande-Sergios.html


    • Proposed as answer by Serch79 Thursday, September 17, 2009 10:28 PM
    • Marked as answer by David Shen Monday, September 21, 2009 2:34 AM
    Thursday, September 17, 2009 5:11 PM
  • I have de same problem...

    I'm using service pack 2 and microsoft netframework 2.0 the hotfix from http://support.microsoft.com/kb/839174 is only for version 1.1

    but my service not started =(

    someone has an idea?




    ############################

    My problem has solved...

    I detect a missing library (mfc71u.dll), i put this dll in dir C:\Windows\system32 and my services already running

    I hope this solve your issue.


    Please enter this link and register your figther

    http://www.kobox.org/kobox-fande-Sergios.html



    The service is a web service? If starting the service from cmd go?
    Tuesday, October 13, 2009 1:59 PM
  • I Got the same problem while starting the service. But my problem is due to the code in Main() method.

    static void Main()

    {

    #if

    (!DEBUG)

    ServiceBase[] ServicesToRun;

    ServicesToRun = new ServiceBase[]

    {

    new MyTestService()

    };

    ServiceBase.Run(ServicesToRun);

    #else

     

    MyTestService service = new MyTestService();

    service.Test();

    #endif

    }



    I used this code to debug the service. By this code i am able to debug but after the service is installed its not able to start.
    I changed this code as given below and every thing is working fine.

     

    static void Main()

    {

     

    ServiceBase[] ServicesToRun;

    ServicesToRun =

    new ServiceBase[]

    {

     

    new MyTestService()

    };

     

    ServiceBase.Run(ServicesToRun);

    }

    • Proposed as answer by Ahwagy Tuesday, June 07, 2011 10:00 PM
    Monday, February 15, 2010 6:36 AM
  • Yes, thank you. It worked for me.
    Tuesday, March 30, 2010 11:47 AM
  • I had this problem and the solution was extremely simple.

    First I tried the various accounts to run the service under, none worked, even a local administrator - all timed out.

    Then I realised the service connected to a SQL Server database that I hadn't finished setting up yet. I finished building the database and the service starts fine.

    What a shame the error (even in the event log) didn't provide any meaningful help!

    Thursday, April 14, 2011 2:43 PM
  • I had the same problem with starting windows search service. I fixed it after reinstalling micro$oft .net framework like they recommended
    Wednesday, July 03, 2013 12:11 PM
  • Equallogic HIT Kit:

    Start Setup64.exe, not the .msi

    This will install .net 4 profile... with all required dlls

    Tuesday, August 27, 2013 3:49 PM
  • Go to windows search, type sql configuration manager, then start services for SQL services, then restart the services of Instance, problem solved :)

    Thursday, December 19, 2013 5:10 PM