Error 1053 Starting Reporting Services
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Reporting Server Error 1053: The service did not respond windows could not start the sql server reporting services error 1053 to the start or control request in a timely fashion SQL Server error 1053 sql server reporting service won't start > SQL Server Reporting Services, Power View Question 0 Sign in to vote Hi, I'm not able error 1053 starting service windows server 2008 r2 to start reporting services after applying the last SQL Server 2005 hotfix (9.0.3068), I'm getting the followwing error 1053: The service did not respond to the start or control request error 1053 windows server in a timely fashion. Any clues ? Regards Dejan Friday, July 11, 2008 9:17 PM Reply | Quote Answers 4 Sign in to 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
Error 1053 The Service Did Not Respond Windows Server 2008 R2
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 click Modify. 5. Click Decimal, type 60000, and then click OK.This value represents the time in milliseconds before a service times out. 6. Restart the computer. Now it's working. But they didn't agree that this is a bug, so they charged me the call. I do not agree with this because everything was worki
local computer. Error 1053: The service did not respond to the start or control request in a timely fashion. This problem
Error 1053 Windows Server 2003
is detailed here:http://support.microsoft.com/kb/2745448, and it's a result of the SSRS service the service did not respond to the start or control request in a timely fashion sql server 2008 r2 checking for certificate revocation lists (CRL). If you're like most people, you've got a firewall blocking Internet error 1053 windows server 2012 r2 access from your server, so each call for a CRL has to time out before SSRS will start. The above KB article mentions a handful of ways of 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 dealing with this problem; the most-frequently used method is to increase the service start timeout in the registry. This works, but it requires a server reboot. And it doesn't really get to the root of the problem, that SSRS is taking a long time to start. Now, generally a CRL is a good thing, even http://tech.lanesnotes.com/2014/02/sql-server-reporting-services-service.html if only in theory. But if your server can't get to the Internet, anyway, there's precious little danger of it getting to a revoked certificate. After all, you're not using the server to browse the web. Right? So: disable CRL checking within SSRS. This is done with the generatePublisherEvidence element in the ReportingServicesService.exe.config file. By default, this file is in the
in a timely fashion" when attempting to start, stop or pause a service Modified on: Tue, 26 Apr, 2016 at 12:13 PM https://support.threattracksecurity.com/support/solutions/articles/1000071019-error-1053-the-service-did-not-respond-in-a-timely-fashion-when-attempting-to-start-stop-or-pause 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 start http://www.sqlteam.com/forums/topic.asp?topic_id=97849 or control request in a timely fashion.""Error 7000: The