Error 1053 Service Timely Fashion Windows Xp
Contents |
in a timely fashion" when attempting to start, stop or pause a service Modified on: Tue, 26 Apr, 2016 at 12:13 1053 error starting service windows xp PM PROBLEM When attempting to start, stop or pause a
Error 1053 Service Timely Fashion Windows 7
service, one of the following error messages is encountered: "Error 1053: The service did not respond to error 1053 service timely fashion windows 2003 the start or control request in a timely fashion.""Error 7000: The
Error 1053 Service Timely Fashion Windows 2008 R2
the start or control request in a timely fashion.""Error 7009: Timeout (30000 milliseconds) waiting for the
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 06:44:49 GMT by s_wx1094 (squid/3.5.20)
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business http://stackoverflow.com/questions/158371/error-1053-the-service-did-not-respond-to-the-start-or-control-request-in-a-tim Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Error 1053: the service did not respond to the start or control request in a timely fashion up vote 34 down vote favorite 17 I error 1053 have recently inherited a couple of applications that run as windows services, and I am having problems providing a gui (accessible from a context menu in system tray) with both of them. The reason why we need a gui for a windows service is in order to be able to re-configure the behaviour of the windows service(s) without resorting to stopping/re-starting. My code works fine in debug mode, and I get the context menu come error 1053 service up, and everything behaves correctly etc. When I install the service via "installutil" using a named account (i.e., not Local System Account), the service runs fine, but doesn't display the icon in the system tray (I know this is normal behavior because I don't have the "interact with desktop" option). Here is the problem though - when I choose the "LocalSystemAccount" option, and check the "interact with desktop" option, the service takes AGES to start up for no obvious reason, and I just keep getting Could not start the ... service on Local Computer. Error 1053: the service did not respond to the start or control request in a timely fashion. Incidentally, I increased the windows service timeout from the default 30 seconds to 2 minutes via a registry hack (see http://support.microsoft.com/kb/824344, search for TimeoutPeriod in section 3), however the service start up still times out. My first question is - why might the "Local System Account" login takes SOOOOO MUCH LONGER than when the service logs in with the non-LocalSystemAccount, causing the windows service time-out? what's could the difference be between these two to cause such different behavior at start up? Secondly - taking a step back, all I'm trying to achieve, is simply a windows service that provides a gui for configuration - I'd be quite happy to run using the non-Local System