Could Not Start The Sql Server Reporting Services Error 1053
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home2012Previous VersionsLibraryForumsGallery Ask a question Quick access Forums home error 1053 starting service windows server 2008 r2 Browse forums users FAQ Search related threads the service did not respond to the start or control request in a timely fashion sql server 2008 r2 Remove From My Forums Answered by: I cannot start the "SQL Server error 1053 the service did not respond windows server 2008 r2 Reporting Services (SCE)" service System Center > System Center Essentials - General Question 1 Sign in to vote error 1053 sql server reporting service won't start Attempts to run any of the Windows Computer Reports fail with an error: Date: 10/29/2008 10:19:30 AMApplication: System Center EssentialsApplication Version: 6.0.1251.0Severity: ErrorMessage: Cannot initialize report. Microsoft.Reporting.WinForms.ReportServerException: The Report Server Windows service 'ReportServer$SCE' is not running. The
The Sql Server Reporting Services Service On Local Computer Started And Then Stopped
service must be running to use Report Server. (rsReportServerServiceUnavailable) at Microsoft.Reporting.WinForms.ServerReport.GetExecutionInfo() at Microsoft.Reporting.WinForms.ServerReport.GetParameters() at Microsoft.EnterpriseManagement.Mom.Internal.UI.Reporting.Parameters.ReportParameterBlock.Initialize(ServerReport serverReport) at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ReportForm.SetReportJob(Object sender, ConsoleJobEventArgs args) My attempts to start the "SQL Server Reporting Services (SCE)" service fail with an error: Could not start the SQL Server Reporting Service (SCE) service on Local Computer.Error 1053: The service did not respond to the start or control request in a timely fashion. The application log in the event viewer has hundreds of instances of Event ID 107: Event Type: ErrorEvent Source: Report Server (SCE)Event Category: Management Event ID: 107Date: 10/29/2008Time: 10:36:25 AMUser: N/AComputer: DCDescription:Report Server (SCE) cannot connect to the report server database. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Please help. Wednes
EstebanNovember 12, 20126 0 0 0 If you are using Reporting Services and Integration Services and you noticed that the service couldn't
Error 1053 Sql Server 2008 R2
start after the installation of the MS12-070 security patch (http://support.microsoft.com/kb/2716429) the sql server reporting services service failed to start due to the following error: you can use the following 2 workarounds below. (the issue alreadyappeared in the past and sql server reporting services service error starting sharepoint 2013 was solved byhttp://support.microsoft.com/kb/936707/en-us) Why is this happening? When a .NET application startup the .NET Framework it tries to check if the Microsoft assemblies are right https://social.technet.microsoft.com/Forums/systemcenter/en-US/bd613e3a-3c77-4a85-ad02-c81de5a21287/i-cannot-start-the-sql-server-reporting-services-sce-service?forum=systemcenter and have not been modified, this is done connecting to a server that has a revocation list in internet. When the framework tries to connect to the server to check if it has access to internet with an elevated timeout, this makes that any other .NET application that has less timeout setting https://blogs.msdn.microsoft.com/mariae/2012/11/12/reporting-services-service-doesnt-start-after-the-installation-of-ms12-070-security-patch/ fails (as SSIS or SSRS) with the error message you are getting. The error message you are getting when you try to start SSRS: "The request failed or the service did not respond in a timely fashion." Means that the SSRS timeout is lower than the timeout of the connection to the revoke list server. Some recent windows updates have introduced this issue after you installed SP2 of SSRS 2008 R2. We are aware of this problem and we have already provided several workarounds. This issue affects to all applications that runs on .NET framework 2.0 and there are several workarounds for this problem: 1st workaround: Modify the registry to increase the default time-out value for the service control manager. To increase this value to 60 seconds, follow these steps: 1. Click Start, click Run, type regedit,and then click OK. 2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\Curr
local computer. Error 1053: The service did not respond to the start or control request in a timely fashion. This problem is detailed here:http://support.microsoft.com/kb/2745448, and it's a result of the SSRS service checking for certificate revocation lists (CRL). If http://tech.lanesnotes.com/2014/02/sql-server-reporting-services-service.html you're like most people, you've got a firewall blocking Internet 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 http://www.sqlteam.com/forums/topic.asp?topic_id=97849 ways of 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 sql server of the problem, that SSRS is taking a long time to start. Now, generally a CRL is a good thing, even 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 sql server reporting ReportingServicesService.exe.config file. By default, this file is in the
SQL Server experts to answer whatever question you can come up with. Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums. SQL Server Forums Profile | ActiveTopics | Members | Search | ForumFAQ Register Now and get your question answered! Username: Password: Save Password Forgot your Password? All Forums Development Tools ASP.NET error 1053, unable to start windows service Reply to Topic Printer Friendly Author Topic juicyapple Posting Yak Master 176 Posts Posted-02/25/2008: 04:26:18 Hi, I have build an windows service in vb.net and installed it successfully. But when I start the service, I get the error:error 1053, the service did not respond to the start or control request in a timely fashionI can't see any useful information from net (and the msdn as well, which talks about upgrading the service pack...) Please advise. mahesh_bote Constraint Violating Yak Guru India 298 Posts Posted-02/27/2008: 04:13:20 hopes u havn't tried this yet.http://support.microsoft.com/kb/839174http://www.hiteksoftware.com/knowledge/articles/050.htmError 1053: The service did not respond to the start or control request in a timely fashion. Even this information I got from net.When attempting to tart a service, you may receive above error. The resolutions are 1) Depending on your system setup, you may try to run the service under Local System or the administrator account. 2) make sure dependencies is running. 3) Make sure the related files have correct permission. For example, if you can't start the Task Schedule service, you may need to check the if the %SystemRoot%\Schedlgu.txt file has the Read-Only attribute. If yes, you may want to assign write permission.try this and let us know.Thanks,Mahesh Topic Reply to Topic Printer Friendly Jump To: Select Forum General SQL Server Forums New to SQL Server Programming New to SQL Server Administration Script Library Data Corruption Issues Database Design and Application Architecture SQL Server 2012 Forums Transact-SQL (2012) SQL Server Administration (2012) SSIS and Import/Export (2012) Analysis Server and Reporting Services (2012) Replication (2012) Availability Groups and DR (2012) Other SQL Server 2012 Topics SQL Server 2008 Forums Transact-SQL (2008) SQL Server Administration (2008) SSIS and Import/Export (2008) High Availability (2008) Replication (2008) Analysis Server and Reporting Services (2008) Other SQL Server 2008 Topics SQL Server 2005 Forums Transact-SQL (2005) SQL Server Administration (2005) .NET Inside SQL Ser