Error 1053 Starting Service 2008 R2
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta error 1053 starting service windows server 2008 r2 Discuss the workings and policies of this site About Us Learn
Error 1053 Starting Service Windows 7
more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us
Error 1053 Starting Service Windows Server 2012
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
Error 1053 While Starting Service
you, helping each other. Join them; it only takes a minute: Sign up Windows could not start service on Win Server 2008 R2 SP1 (Error 1053) up vote 10 down vote favorite 2 This issue seems to be widely discussed, but I have problems with finding the solution in my particular case. My service is set up 1053 error starting service windows 8 to be running under Local System account. On my first machine with Windows 7 SP1 (64-bit) installed, everything works as expected. But, just after I try to start the service on my second machine with Windows Server 2008 R2 SP1 (64-bit), not even a second passes, and I'm facing this annoying error: Windows could not start the ProService service on Local Computer Error 1053: The service did not respond to the start or control request in a timely fashion The System Log shows 2 entries: The ProService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. and: A timeout was reached (30000 milliseconds) while waiting for the ProService service to connect. The implementation looks following: Program.cs: static void Main() { AppDomain.CurrentDomain.UnhandledException += CurrentDomainUnhandledException; ServiceBase.Run(new ServiceBase[] { new ProService() }); } static void CurrentDomainUnhandledException(object sender, UnhandledExceptionEventArgs e) { if (e != null && e.ExceptionObject != null) { Logger.Record(e.ExceptionObject); } } ProService.cs: public ProService() { InitializeCom
360 games PC games the service did not respond to the start or control request in a timely fashion sql server 2008 r2 Windows games Windows phone games Entertainment All Entertainment error 1053 the service did not respond windows server 2008 r2 Movies & TV Music Business & Education Business Students & educators error 1053 windows server 2012 r2 Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet http://stackoverflow.com/questions/14121079/windows-could-not-start-service-on-win-server-2008-r2-sp1-error-1053 Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/886695 Windows phones Microsoft HoloLens 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 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 (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
Favorite Rating: "Error 1053: The service did not respond to the start or control request in a timely fashion" when starting WECSThis https://www.novell.com/support/kb/doc.php?id=7011402 document (7011402) is provided subject to the disclaimer at the end of this document. Environment NetIQ Sentinel Windows Event Collection Service Microsoft Windows 2008 R2 64-bit Situation Message appears when trying tostart the Sentinel Windows Event Collection Service (WECS) on Windows machine: Error 1053: The service did not respond to the start or control request in a timely fashion Resolution Make error 1053 sure that the .NET 4.0 is installed on the machine where the service is running. Create the registry entry for the Services Pipe Timeout and give it higher than the default value: Start the registry editor (regedit.exe) navigate to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control Right-click on the above key and choose New, then DWORD Value Type ServicesPipeTimeout as the name for it and error 1053 starting press ENTER Right-click on the ServicesPipeTimeout value and choose to Modify it In the Base section click Decimal In the Value data text box type for example 60000 as the value of timeout period and click OK Restart the computer Note: The computer needs to be restarted for the Service Control Manager to apply this change. Cause By default a service has 30000 milliseconds (30 seconds) to respond to the Service Control Manager which controls the states of installed services. Sometimes performance issues or some configurations may cause the service to require more than default 30 seconds to start. Additional Information Value of 60000 in step 7 is just an example. If the service requires longer than 60000 milliseconds (60 seconds) to start, increase that value appropriately. DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. Document ID:7011402Creation Date:20-NOV-12Modified Date:12-DEC-12NetIQSentinel Did this d