Error 1053 Windows Server 2008 R2
Contents |
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 windows server 2008 r2 download more about Stack Overflow the company Business Learn more about hiring developers or posting
Windows Server 2008 R2 End Of Life
ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community windows server 2008 r2 price 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 Windows could not start service on Win Server 2008 R2 windows server 2008 r2 standard vs enterprise 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 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
Windows Server 2008 R2 32 Bit
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() { InitializeComponent(); } protected override void OnStart(string[] args) { try { RequestAdditionalTime(10000); FireStarter.Instance.Execute(); } catch (Exception e) { Logger.Record(e); throw; } } The OnStart method is just starting a new thread, so it takes almost NO time load to execute. I used RequestAdditionalTime statement just in case - to reject this matter as a source of my problem. In addition, as you can see, I'm handling all of the excepti
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: windows server 2008 r2 requirements Reporting Server Error 1053: The service did not respond to the windows server 2008 r2 sp2 start or control request in a timely fashion SQL Server > SQL Server Reporting Services,
Windows Server 2008 R2 Product Key
Power View Question 0 Sign in to vote Hi, I'm not able to start reporting services after applying the last SQL Server 2005 hotfix http://stackoverflow.com/questions/14121079/windows-could-not-start-service-on-win-server-2008-r2-sp1-error-1053 (9.0.3068), I'm getting the followwing error 1053: The service did not respond to the start or control request in a timely fashion. Any clues ? Regards Dejan Friday, July 11, 2008 9:17 PM Reply | Quote Answers 4 Sign in to https://social.msdn.microsoft.com/Forums/sqlserver/en-US/b57ee42d-42ef-44a4-9670-be9088dbf9d4/reporting-server-error-1053-the-service-did-not-respond-to-the-start-or-control-request-in-a-timely?forum=sqlreportingservices vote Hi folks, As I said before I have this problem with DPM, so I oppened a call to PSSE. We managed to circumvent the problem with this instrucions: My name is xxxxx and I am the Support Engineer that will be helping you with this case. After looking over the case logs, I think I might have some information that will help. Below is a process that might correct the timeout issue. 1. Click Start, click Run, type regedit, and then click OK. 2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control 3. In the right pane, locate the ServicesPipeTimeout entry.Note If the ServicesPipeTimeout entry does not exist, you must create it. To do this, follow these steps: a. On the Edit menu, point to New, and then click DWORD Value. b. Type ServicesPipeTimeout, and then press ENTER. 4. Right-click ServicesPipeTimeout, and then
Favorite Rating: "Error 1053: The service did not respond to the start or control request in a timely fashion" when starting WECSThis document (7011402) is provided subject https://www.novell.com/support/kb/doc.php?id=7011402 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 sure that the .NET 4.0 is installed on the machine where windows server 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 press ENTER Right-click on the ServicesPipeTimeout value and choose to Modify it In the Base section windows server 2008 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 document solve your problem? Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple Request a Call Follow Us Facebook YouTube Twitter LinkedIn Newsletter Subscription RSS