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

Question

I have created and installed a service a couple of times  Initially it was working fine  but after some changes in the service Code it start giving the error when I restart the service in Services msc       Error 1053  the service did not respond to the start or control request in a    timely fashion   Code   public partial class AutoSMS   ServiceBase       public AutoSMS                 InitializeComponent            eventLog1 Clear             if   System Diagnostics EventLog SourceExists  MySource                          System Diagnostics EventLog CreateEventSource                   MySource    MyNewLog                      eventLog1 Source    MySource           eventLog1 Log    MyNewLog            Timer checkForTime   new Timer 5000           checkForTime Elapsed    new ElapsedEventHandler checkForTime Elapsed           checkForTime Enabled   true              protected override void OnStart string   args                eventLog1 WriteEntry  In OnStart               protected override void OnStop                 eventLog1 WriteEntry  In onStop                 void checkForTime Elapsed object sender  ElapsedEventArgs e                string Time    15 05 00           DateTime dateTime   DateTime ParseExact Time   HH mm ss                                           CultureInfo InvariantCulture            if  DateTime Now    dateTime                eventLog1 WriteEntry Time             Here is my main method code  static void Main         ServiceBase   ServicesToRun      ServicesToRun   new ServiceBase                   new AutoSMS               ServiceBase Run ServicesToRun       I also tried the following steps     Go to Start   Run   and type regedit Navigate to  HKEY LOCAL MACHINE SYSTEM CurrentControlSet Control With the control folder selected  right click in the pane on the right and - select new DWORD Value Name the new DWORD  ServicesPipeTimeout  Right-click ServicesPipeTimeout  and then click Modify Click Decimal  type  180000   and then click OK Restart the computer   I used to install and uninstall it with following command    installutil AutoSMS exe  installutil  u AutoSMS exe

User · Answer

I have just tried this code locally in  Net 4 5 and the service starts and stops correctly for me  I suspect your problem may be around creating the EventLog source   The method   EventLog SourceExists  MySource     requires that the user running the code must be an administrator  as per the documentation here   http   msdn microsoft com en-us library x7y6sy21 v vs 110  aspx  Check that the service is running as a user that has administrator privileges

User · Answer

I faced this problem because of a missing framework on the box running my service  The box had  NET 4 0 and the service was written on top of  NET 4 5    I installed the following download on the box  restarted  and the service started up fine  http   www microsoft com en-us download details aspx id 30653

User · Answer

I had this problem too  I made it to work by changing Log On account to Local System Account  In my project I had it setup to run as Local Service account  So when I installed it  by default it was using Local Service  I m using  net 2 0 and VS 2005  So installing  net 1 1 SP1 wouldn t have helped

User · Answer

I want to echo mdb s comments here   Don t go this path   Your service is not supposed to have a UI      No user interaction  is like the definining feature of a service   If you need to configure your service  write another application that edits the same configuration that the service reads on startup   But make it a distinct tool -- when you want to start the service  you start the service   When you want to configure it  you run the configuration tool   Now  if you need realtime monitoring of the service  then that s a little trickier  and certainly something I ve wished for with services    Now you re talking about having to use interprocess communications and other headaches   Worst of all  if you need user interaction  then you have a real disconnect here  because services don t interact with the user   In your shoes I would step back and ask why does this need to be a service   And why does it need user interaction   These two requirements are pretty incompatible  and that should raise alarms

User · Answer

In my case the problem was missing version of  net framework   My service used    lt startup gt     lt supportedRuntime version  v4 0  sku   NETFramework Version v4 5    gt   lt  startup gt    But  net Framework version of server was 4  so by changing 4 5 to 4 the problem fixed    lt startup gt     lt supportedRuntime version  v4 0  sku   NETFramework Version v4 0    gt   lt  startup gt

User · Answer

In service class within OnStart method don t do huge operation  OS expect short amount of time to run service  run your method using thread start   protected override void OnStart string   args        Thread t   new Thead new ThreadStart MethodName       e g      t Start

User · Answer

This worked for me  Basically make sure the Log on user is set to the right one  However it depends how the account infrastructure is set  In my example it s using AD account user credentials     In start up menu search box search for  Services   -In Services find the required service  -right click on and select the Log On tab  -Select  This account  and enter the required content credentials  -Ok it and start the service as usual

User · Answer

Release build did not work for me  however  I looked through my event viewer and Application log and saw that the Windows Service was throwing a security exception when it was trying to create an event log  I fixed this by adding the event source manually with administration access   I followed this guide from Microsoft    open registry editor  run --  regedit Locate the following registry subkey  HKEY LOCAL MACHINE SYSTEM CurrentControlSet Services Eventlog Application Right-click the Application subkey  point to New  and then click Key  Type event source name used in your windows service for the key name  Close Registry Editor

User · Answer

Took me hours  should have seen the event viewer get AppSettings     A change in the app config  caused the problem

User · Answer

I was running into a similar problem with a Service I was writing  It worked fine then one day I started getting the timeout on Start errors  It happened in one  amp  or both Release and Debug depending on what was going on  I had instantiated an EventLogger from System Diagnostics  but whatever error I was seeing must have been happening before the Logger was able to write      If you are not aware of where to look up the EventLogs  in VS you can go to your machine under the Server Explorer  I started poking around in some of the other EventLogs besides those for my Service  Under Application -  NETRuntime  I found the Error logs pertinent to the error on startup  Basically  there were some exceptions in my service s constructor  one turned out to be an exception in the EventLog instance setup - which explained why I could not see any logs in my Service EventLog   On a previous build apparently there had been other errors  which had caused me to make the changes leading to the error in the EventLog set up    Long story short - the reason for the timeout may be due to various exceptions errors  but using the Runtime EventLogs may just help you figure out what is going on  especially in the instances where one build works but another doesn t    Hope this helps

User · Answer

I had this problem  it took about a day to fix  For me the problem was that my code skipped the  main content  and effectively ran a couple of lines then finished  And this caused the error for me  It is a C  console application which installs a Windows Service  as soon as it tried to run it with the ServiceController  sc Run     then it would give this error for me    After I fixed the code to go to the main content  it would run the intended code    ServiceBase Run new ServiceHost      Then it stopped showing up    As lots of people have already said  the error could be anything  and the solutions people provide may or may not solve it  If they don t solve it  like the Release instead of Debug  adding generatePublisherEvidence false into your config  etc   then chances are that the problem is with your own code    Try and get your code to run without using sc Run    i e  make the code run that sc Run   would have executed

User · Answer

Also  you need to check your configuration file content    You need to check below the section    lt startup gt       lt supportedRuntime version  v4 0  sku   NETFramework Version v4 5 2   gt   lt  startup gt    Coz above section need to match with yours  net framework

User · Answer

I scratched my head to clear this error This error might be caused if you are debugging it in the code like  static void Main       if DEBUG             MailService service   new MailService                 service Ondebug      else              ServiceBase   ServicesToRun               ServicesToRun   new ServiceBase                                   new MailService                                ServiceBase Run ServicesToRun     endif                     After clearing the if else and endif in the code like this the error has not appeared again    hope it helps      static void Main          ServiceBase   ServicesToRun      ServicesToRun   new ServiceBase                 new MailService              ServiceBase Run ServicesToRun

User · Answer

I encountered the same issue and was not at all sure how to resolve it  Yes this occurs because an exception is being thrown from the service  but there are a few general guidelines that you can follow to correct this    Check that you have written the correct code to start the service   ServiceBase   ServicesToRun  ServicesToRun   new ServiceBase           new WinsowsServiceToRun       ServiceBase Run ServicesToRun    You need to ensure that there is some kind of infinite loop running in the class WinsowsServiceToRun Finally  there may be some code which is not logging anything and closing the program abruptly  which was the case with me   in this case you will have to follow the old school of debugging which needed to write a line to a source  text db wherever   What I faced was that since the account running the service was not  Admin   the code was just falling off and not logging any exceptions in case it was trying to write to  Windows Event Log  even though the code was there to log exceptions  Admin privilege is actually not needed for logging to Even Log but it is needed to define the source  In case source of the event is not already defined in the system and the service tries to log it for the first time without admin privilege it fails  To solve this follow below steps    Open command prompt with admin privilege Paste the command   eventcreate  ID 1  L APPLICATION  T INFORMATION   SO  lt  lt Source gt  gt   D   lt  lt SourceUsingWhichToWrite gt  gt   Press enter Now start the service

User · Answer

Check ConnectionStrings if you are using EntityFramework or any other means to initiate database connections at the service startup   In my case when i got the error Error 1053 the service did not respond to the start or control request in a timely fashion this is what was going wrong   I was using EntityFramework and had the connection strings wrong  So basically at startup the EntityFramework failed to connect to the database using the incorrect Connection String and timed out   Just had to replace the database connection string with the correct one and it worked fine   Did not need any framework update or any other system configuration change at all

User · Answer

open the services window as administrator Then try to start the service That worked for me

User · Answer

I also faced similar problem and found that there was issue loading assembly  I was receiving this error immediately when trying to start the service   To quickly debug the issue  try to run service executable via command prompt using ProcDump http   technet microsoft com en-us sysinternals dd996900  It shall provide sufficient hint about exact error   http   bytes com topic net answers 637227-1053-error-trying-start-my-net-windows-service helped me quite a bit

User · Answer

Install the  net framework 4 5  It worked for me   https   www microsoft com en-us download details aspx id 57768

User · Answer

In case you have a windows form used for testing  ensure that the startup object is still the service and not the windows form

User · Answer

I have installed  Net 4 6 on my WindowsServer computer and the error was fixed   Your control should be this way    Check the  net version of your WindowsService Then check the  net version of your computer Match that version  since it s probably not matched

User · Answer

I had the same issue  Seems like when starting the service the main thread shouldnt be the main worker thread  By simply creating a new thread and handing the main work to that thread solved my issue

User · Answer

My issue was the one with appsettings json not copying to release build folder during build and simple putting it into the     bin Release folder and copying launchSettings json content to appsettings json solved the problem for me

User · Answer

In the case I ran into this morning  the culprit was a malformed config file  The config file had an close comment tag without the open comment tag  So  double check your config files for errors

User · Answer

Build project in Release Mode  Copy all Release folder files to source path  Execute Window service using command prompt window in administrative access   Never delete files from source path    At lease this works for me

User · Answer

To debug the startup of your service  add the following to the top of the OnStart   method of your service    while  System Diagnostics Debugger IsAttached  Thread Sleep 100     This will stall the service until you manually attach the Visual Studio Debugger using Debug -  Attach to Process     Note  In general  if you need a user to interact with your service  it is better to split the GUI components into a separate Windows application that runs when the user logs in  You then use something like named pipes or some other form of IPC to establish communication between the GUI app and your service  This is in fact the only way that this is possible in Windows Vista

User · Answer

One of possible solutions for this problem  It fixed issue at my end and my application is JAVA based application     1  check your application is pointing to correct java version check the java version and path in your application    OR  2 check the configured java version i e check whether it is 32-bit version or 64-bit version based on your application   if you are using 32-bit then you should use 32-bit version JSL  else JSL will cause this issue

User · Answer

My issue was due to target framework mentioned in windows service config was    lt startup gt   lt supportedRuntime version  v4 0  sku   NETFramework Version v4 6   gt    lt  startup gt    and my server in which I tried to install windows service was not supported for this  Net version   Changing which   I could able to resolve the issue

User · Answer

In my case it was permission for user account in AD  After set it correctly  it works perfect

User · Answer

this error can be caused due to various reasons  to identify the reason add try  catch when service is run           try                               ServiceBase   ServicesToRun                  ServicesToRun   new ServiceBase                                           new Service1                                        lt span class  skimlinks-unlinked  gt ServiceBase Run ServicesToRun lt  span gt                              catch  Exception ex                                EventLog WriteEntry  Application   ex ToString     lt span class  skimlinks-unlinked  gt EventLogEntryType Error lt  span gt

User · Answer

After spending some time on the issue  trying solutions that didn t work  I run into this blog  It suggests to wrap the service initialization code in a try catch block  like this  and adding EventLog  using System  using System Diagnostics  using System ServiceProcess   namespace WindowsService       static class Program               static void Main                         try                               ServiceBase   ServicesToRun                  ServicesToRun   new ServiceBase                                           new Service1                                       ServiceBase Run ServicesToRun                             catch  Exception ex                                EventLog WriteEntry  Application   ex ToString    EventLogEntryType Error                                     Then  uninstall the old service  redeploy the service with these modifications  Start the service and check out the Event Viewer Application logs   You ll see what the real problem is  which is the underlying reason for the timeout

User · Answer

Copy the release DLL or get the dll from release mode rather than Debug mode and paste it to installation folder  it should work

User · Answer

As nobody has mentioned I will add it  even if it is a stupid mistake   In case you are on Windows 10 you don t usually need to restart  but  -  Make sure to CLOSE any open properties pages of the  services -window in case you have just installed the service  and still have opened the properties page of the old service     I m talking about this window     After closing all services windows and re-trying -  it worked  In contrast to the OP I got Error 1053 basically immediately   without windows waiting on anything

User · Answer

I was getting exactly same issue  All I have done is to to change the Debug mode to Release while compiling the dll  This has solved my probelm  how why  I dont know I have already asked a question on SO

User · Answer

This problem usually occurs when there is some reference missing on your assembly and usually the binding fails at the run time   to debug put Thread Sleep 1000  in the main    and put a break point in the next line of execution   Then start the process and attach the debugger to the process while it is starting  Press f5 after it hit the break point  It will throw the exception of missing assembly or reference    Hopefully this will resolve this error

User · Answer

I m shooting blind here  but I ve very often found that long delays in service startups are directly or indirectly caused by network function timeouts  often when attemting to contact a domain controller when looking up account SIDs - which happens very often indirectly via GetMachineAccountSid   whether you realize it or not  since that function is called by the RPC subsystem   For an example on how to debug in such situations  see The Case of the Process Startup Delays on Mark Russinovich s blog

User · Answer

In my case  I was publishing service while it was in debug mode   Solution was    Changing solution to release mode  Uninstall old service with command InstallUtil -u WindowsServiceName exe installing service again  InstallUtil -i WindowsServiceName exe   It worked perfectly after

User · Answer

I had this similar issue  Stops i followed   Put a Debugger Launch   in the windows service constructor  Followed step by step to see where it is stuck   My issue wasn t due to any error   I had a BlockingCollection GetConsumingEnumerable   in the way  That caused the windows service to wait

User · Answer

If you continue down the road of trying to make your service interact with the user s desktop directly  you ll lose  even under the best of circumstances  i e   before Vista    this is extremely tricky    Windows internally manages several window stations  each with their own desktop  The window station assigned to services running under a given account is completely different from the window station of the logged-on interactive user  Cross-window station access has always been frowned upon  as it s a security risk  but whereas previous Windows versions allowed some exceptions  these have been mostly eliminated in Vista and later operating systems   The most likely reason your service is hanging on startup  is because it s trying to interact with a nonexistent desktop  or assumes Explorer is running inside the system user session  which also isn t the case   or waiting for input from an invisible desktop    The only reliable fix for these issues is to eliminate all UI code from your service  and move it to a separate executable that runs inside the interactive user session  the executable can be started using the global Startup group  for example    Communication between your UI code and your service can be implemented using any RPC mechanism  Named Pipes work particularly well for this purpose  If your communications needs are minimal  using application-defined Service Control Manager commands might also do the trick   It will take some effort to achieve this separation between UI and service code  however  it s the only way to make things work reliably  and will serve you well in the future   ADDENDUM  April 2010  Since this question remains pretty popular  here s a way to fix another common scenario that causes  service did not respond     errors  involving  NET services that don t attempt any funny stuff like  interacting with the desktop  but do use Authenticode signed assemblies  disable the verification of the Authenticode signature at load time in order to create Publisher evidence  by adding the following elements to your  exe config file    lt configuration gt       lt runtime gt           lt generatePublisherEvidence enabled  false   gt       lt  runtime gt   lt  configuration gt    Publisher evidence is a little-used Code Access Security  CAS  feature  only in the unlikely event that your service actually relies on the PublisherMembershipCondition will disabling it cause issues  In all other cases  it will make the permanent or intermittent startup failures go away  by no longer requiring the runtime to do expensive certificate checks  including revocation list lookups

User · Answer

I had two services running who were accidentally coupled to the same EventSource eventLog Source    MySource   After uninstalling both services  and reinstalling the one that suffered from error 1053  my service started up normally

User · Answer

This is usually caused by an uncaught exception in the service itself   Configuration file errors eg   Opening a command prompt and starting the service executable manually wil perhaps reveal the exception been thrown

User · Answer

In my experience  I had to stop my existing service to update code  after updating the code and while START the Service I got the same error  Error 1053 the service did not respond to the start or control request in a timely fashion     But this got resolve after RESTARTING THE MACHINE

User · Answer

I know this is old question  I used to write my own VB NET windows service  and it has no issue to start on MS windows 7 and MS windows 10    I have this issue when I install the windows services on latest MS windows 10 patch  The reason the windows service doesn t run it is because the  NET version that needed for the window services to run is not presented in the installed PC   After you have installed the windows services  go to the install folder for example C  Program files  x86  Service1 Service1 exe and double click to run it  If there is missing  NET framework package  it will prompt the user to download it  Just download and and wait for it to install   After that restart the windows services in services msc   Hope this answer will help someone who face the issue  I know issue is caused by  NET framework version

User · Answer

We have Log4Net configured to log to a database table  The table had grown so large that the service was timing out trying to log messages

User · Answer

In my case  I had this trouble due to a genuine error  Before the service constructor is called  one static constructor of member variable was failing       private static OracleCommand cmd       static SchedTasks                 try                       cmd   new OracleCommand  select   from change notification                      catch  Exception e                        Log e Message                    The provider is not compatible with the version of Oracle client                    By adding try-catch block I found the exception was occuring because of wrong oracle version  Installing correct database solved the problem

User · Answer

Once try to run your exe file  I had the same problem  but when I ran it direct by double click on the exe file  I got a message about  Net framework version  because I was released the service project with a framework which it wasn t installed on target machine

User · Answer

After spending too much time on this issue  I found the EventLog cause all that mess although I used it properly   Whoever tackle this issue  I would suggest you to get rid of the EventLog  Use better tools like  log4net

User · Answer

After fighting this message for days  a friend told me that you MUST use the Release build   When I InstallUtil the Debug build  it gives this message   The Release build Starts fine

User · Answer

Check if the service starting code is correct   ServiceBase   ServicesToRun  ServicesToRun   new ServiceBase           new WinsowsServiceToRun       ServiceBase Run ServicesToRun     Also  remove any debug codes  ie       If Debug                                                 else                                    endif

User · Answer

In my case  the issue was about caching configuration which is set in the App config file  Once I removed below lines from the App config file  the issue was resolved    lt cachingConfiguration defaultCacheManager  MyCacheManager  gt   lt cacheManagers gt     lt add name  MyCacheManager  type  Microsoft Practices EnterpriseLibrary Caching CacheManager  Microsoft Practices EnterpriseLibrary Caching  Version 5 0 414 0  Culture neutral  PublicKeyToken 31bf3856ad364e35         expirationPollFrequencyInSeconds  60         maximumElementsInCacheBeforeScavenging  50000         numberToRemoveWhenScavenging  1000         backingStoreName  NullBackingStore    gt   lt  cacheManagers gt   lt backingStores gt     lt add type  Microsoft Practices EnterpriseLibrary Caching BackingStoreImplementations NullBackingStore  Microsoft Practices EnterpriseLibrary Caching  Version 5 0 414 0  Culture neutral  PublicKeyToken 31bf3856ad364e35         name  NullBackingStore    gt   lt  backingStores gt

User · Answer

If you would like to register a  NET core 3 1 executable as a Windows Service  please ensure that you added the nuget package Microsoft Extension Hosting WindowsServices in version 3 1 7 or above and initialize the hostBuilder like in the following example  using Microsoft Extensions Hosting   namespace ConsoleApp1       class Program               static void Main string   arguments                        IHostBuilder hostBuilder   Host CreateDefaultBuilder arguments               hostBuilder UseWindowsService                hostBuilder Build   Run                       Now you are able to install the executable and start it as a windows service  sc exe create ConsoleApp1 binPath   quot  lt BIN PATH gt  ConsoleApp1 exe quot

User · Answer

I d like to add my solution to this  Must admit  I use an additional configuration file   quot ServiceIni xml quot   with some settings to be changed by user on the fly  When I faced this error I made a research and did following   Changed Program cs to following code           static void Main                         try                               ServiceBase   ServicesToRun                  ServicesToRun   new ServiceBase                                     new MyService                                      ServiceBase Run ServicesToRun                             catch  Exception ex                                LogChanges   quot Error -  ex Message  nInner -  ex InnerException  quot                                     static void LogChanges string message                        string LogPath   AppDomain CurrentDomain BaseDirectory    quot MyServiceLog txt quot               using  StreamWriter wr   File AppendText LogPath                                 wr WriteLine message                             Then I discovered an exception on startup from the log  it showed even error line number       Error - Configuration system failed to initialize Inner - System Configuration ConfigurationErrorsException  A section using  configSource  may contain no other attributes or elements   C      bin Release MyService exe Config line 24     at System Configuration ConfigurationSchemaErrors ThrowIfErrors Boolean ignoreLocal     at System Configuration BaseConfigurationRecord ThrowIfParseErrors ConfigurationSchemaErrors schemaErrors     at System Configuration BaseConfigurationRecord ThrowIfInitErrors      at System Configuration ClientConfigurationSystem EnsureInit String configKey    It appeared that one of builds changed my App config file from    lt  -- Setting to use appSettings from external file -- gt     lt appSettings configSource  quot ServiceIni xml quot   gt   to    lt appSettings configSource  quot ServiceIni xml quot  gt       lt add key  quot ClientSettingsProvider ServiceUri quot  value  quot  quot    gt     lt  appSettings gt   which generated this error  Fixing back to original App config solved the issue

User · Answer

I had same problem  Unchecking  Sing the ClickOnce manifest    Sign the assembly  and  Enable ClickOnce security settings  in project properties helped

User · Answer

In my case I apparently had some extra symbols in my App config file that I did not notice when building my solution  So I recomend to check the configuration file for errors first before taking steps with changing registry keys  switching configuration modes  etc

User · Answer

As others have pointed out  this error can have a multitude of causes   But in the hopes that this will help somebody out  I ll share what happened in our case   For us  our service had been upgraded to  NET 4 5  but the server did not have  NET 4 5 installed

User · Answer

Both Local System Account and Local Service would not work for me  i then set it to Network Service and this worked fine

User · Answer

Adding 127 0 0 1 crl microsoft com to the  Hosts  file solved our issue

User · Answer

Install the debug build of the service and attach the debugger to the service to see what s happening

User · Answer

It is because of the Microsoft Windows Service Control  it controls sometimes the state of the services  If the service don  t send a respond in 30 seconds  then you will have this error   You can modified the registry  so the service will have more time to respond  Go to Start  gt  Run  gt  and type regedit Navigate to  HKEY LOCAL MACHINE SYSTEM CurrentControlSet Control With the control folder selected  right click in the pane on the right and select new DWORD Value Name the new DWORD  ServicesPipeTimeout  Right-click ServicesPipeTimeout  and then click Modify Click Decimal  type  180000   and then click OK Restart the computer   Or be sure that in that moment there is not another process talking with the service  maybe there is a conflict I don  t know

User · Answer

This worked for me  Basically make sure the Log on user is set to the right one  However it depends how the account infrastructure is set  In my example it s using AD account user credentials     In start up menu search box search for  Services   -In Services find the required service  -right click on and select the Log On tab  -Select  This account  and enter the required content credentials  -Ok it and start the service as usual

User · Answer

I have removed  EventLog Exists  and fixed

User · Answer

I had this problem and it drove me nuts for two days    If your problem similar to mine   I have settings    User settings    in my windows service  so the service can do self-maintenance  without stopping and starting the service  Well  the problem is with the    user settings     where the config file for these settings is saved in a folder under the user-profile of the user who is running the windows service under the service-exe file version    This folder for some reason was corrupted  I deleted the folder and service start working back again happily as usual

User · Answer

If you are using Debug code as below in your service the problem may arise    if  DEBUG  ServiceBase   ServicesToRun  ServicesToRun   new ServiceBase     new EmailService      ServiceBase Run ServicesToRun    else   direct call function what you need to run  endif   To fix this  while you build your windows service remove  if condition because it didn t work as it is   Please use argument for debug mode instead as below   if  args    null  amp  amp  args Length  gt  0     isDebug   args 0  ToLower   Contains  debug

[c#] Error 1053 the service did not respond to the start or control request in a timely fashion

Examples related to c#

Examples related to .net

Examples related to timer

Examples related to windows-services