Error 1053 Service Timely Fashion Windows 7
Contents |
and greatly increased scalability for larger networks Learn more CommunitySupportProductsGFI ArchiverGFI EndPointSecurityGFI EventsManagerGFI FaxMakerGFI FaxMaker OnlineGFI LanGuardGFI MailEssentialsGFI WebMonitorProduct DocumentationProduct FeedbackContact supportContact usLog inGFI FaxMaker error 1053 the service did not respond in a timely fashion OnlineCustomer PortalPartner Portal Company ProductsGFI SecurityGFI LanGuardGFI WebMonitorGFI EventsManagerGFI EndPointSecurityGFI CommunicationsGFI error 1053 the service did not start in a timely fashion MailEssentialsGFI ArchiverGFI FaxMakerGFI FaxMaker OnlineAll ProductsGFI WebMonitorGFI LanGuardGFI MailEssentialsGFI EventsManagerGFI ArchiverGFI EndPointSecurityGFI FaxMakerGFI FaxMaker OnlineCompanyCareersCareersWhy work at error 1053 windows server 2008 r2 GFIPress centerIn the newsPress releasesBlogAbout usBrand PillarsAwardsCustomersLeadershipTrusted ExpertsContactWebcasts and eventsPartnersBecome a GFI PartnerGFI Partner Program: Frequently Asked QuestionsWhy Resell GFI?Find a distributorFind a resellerGFI Partner AreaGFI OEM error 1053 windows server 2012 r2 PartnersGFI Technology PartnersDownloadsLanguagesEnglishDeutschEspañolFrançaisItalianoNederlands简体中文繁体中文Store GFI Archiver Error: 'The service did not respond in a timely fashion' (ServicesPipeTimeout) when attempting when attempting to start, stop or pause a service PROBLEM When attempting to start, stop or pause a service, one of the following error messages is encountered: 'Error 1053: The service did not respond to the
Error 1053 Windows 10
start or control request in a timely fashion.' 'Error 7000: The
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 Learn more about hiring developers
Error 1053 Windows Server 2003
or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x the service did not respond in a timely fashion windows 7 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 error 1053 windows 8 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 have recently inherited a couple of applications that run http://www.gfi.com/support/products/gfi-archiver/Error-The-service-did-not-respond-in-a-timely-fashion-ServicesPipeTimeout-when-attempting-when-attempting-to-start-stop-or-pause-a-service 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 up, and everything behaves correctly etc. When I install the service via "installutil" using a http://stackoverflow.com/questions/158371/error-1053-the-service-did-not-respond-to-the-start-or-control-request-in-a-tim 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 Account (with named user/pwd), if I could get the service to interact with the desktop (that is, have a context menu available from the system tray). Is this
games Xbox 360 games Windows https://support.microsoft.com/en-ca/kb/886695 games Games for Windows phone PC games Entertainment All entertainment Movies & TV Music PC games Business & Education Business Store Education Store Developer Deals Sale Microsoft Surface deals Free shipping. Free returns. Gift cards Find a store error 1053 Products Software & services Windows Office Free downloads & security Internet Explorer Microsoft Edge Skype OneNote OneDrive MSN Bing Microsoft Groove Microsoft Films & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets error 1053 windows PC Accessories Xbox & games For business Cloud platform Microsoft Azure Microsoft Dynamics Windows for business Office for Business Skype for Business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in the classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (Canada) Terms of use Privacy & cookies Trademarks © 2016 Microsoft