SQL Server Reporting Services fails to start. Why?

Most of the time the issue occurs after doing the below operations.

• New Service Pack installation
• SQL Server Service account change
• Any security patch installation

Error:

What is the Problem?

This problem occurs when .NET framework trying to verify the Microsoft assemblies are correctly loaded, these can be done by connecting to the internet. Where as .NET application has less timeout settings compare to the Framework, Which is trying to setup the connection to the server to check, if it has access to the internet. 

The below error is triggered.

Error 1053: The service did not respond to the start and control request in a timely fashion.

Workaround:

1) Increase the default timeout value

Edit the registry values as mentioned below.

1. Start -> RUN, Enter regedit and click OK

2. Drop down to the below registry value

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

3. Right Pane, Locate ServicesPipeTimeout. If the value is not present, create one

4. Go to EDIT menu, Right Click, Select NEW -> DWORD

             

5. Right-click ServicesPipeTimeout DWORD value, click Modify

6. Click Decimal Value and enter 60000,  click OK

NOTE: Restart the server to effect the changes.

2) Disable CRL checking

This has worked many times, when the server restart is not possible/ required.

To do it, Edit the configuration file. By doing the below steps.

Go to <Drive>:\Program Files\Microsoft SQL Server\MSRSXXX.MSSQLSERVER\Reporting   Services\ReportServer\bin

Open ReportingServicesService.exe.config

Add <generatePublisherEvidence enabled= "false"/> just before </runtime>

Example: