**Error: SQL Server Reporting Services 2008 Crashes\Unresponsive suddenly on Windows 2008 R2**
We had an issue in which the reporting services suddenly stops responding suddenly and when we connect to reporting services it’s not responding, even the configuration manager fails to load SSRS configuration.
When you look the SSRS logs you will see error like below
ERROR: Managed server timed out. Timeout=150 sec. Gc extension timeout=30 sec.
During investigation it seems like a bug in SSRS; investigation reveals that the major cause of SSRS un-responsiveness\crash of SSRS was slow GC (Garbage collection- it manages the allocation and release of memory for your application). Granting additional timeout of 30 sec.” indicates that managed server timed out while GC was in process, and so slow GC was the likely reason.
Slow GC occurs usually when you have a lot of RAM on the box and the report server process is using a lot of it. The problem is that for managed applications, a Garbage Collection (GC) occurs periodically. During a GC the process is suspended temporarily.
MS suggest that a process related to SSRS must be killed from query analyzer should resolve this issue.
Resolution which worked for US
We tried several things but at last the resolution which worked for us is to apply a latest SP3 for SQL 2008, after applying latest SP the reporting service went to its normal consistent state.
**Problem: Un-able to browse report as the report server is not responding **
If the report server is not responding to the user requests and when you check the event viewer and found below mentioned warning
Warning 1: The report server has detected a possible denial of service attack. The report server is dropping requests for service from the xxx.xxx.xxx.xx
Warning 2: Exception information:
Exception type: HttpException
Exception message: Server Too Busy
The reason could be here that the number of connections from the same user exceeds the maximum allowed number of concurrent connections from one user, the SSRS will not handle new requests and it will wait until existing requests have terminated.
By default SSRS can only allow 20 max connections from one user as shown below hence to resolve this issue you need to increase this value as per your requirement.
Resolution: To resolve this issue go below mentioned location or the location where reportserver config file is available as per your installation.
\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer
- Open the file in notepad and find “MaxActiveReqForOneUser” and change its valle as per your need.
<Add Key=”MaxActiveReqForOneUser” Value=”20″/>
Hope this will resolve your issue.
**Error: SSRS configuration error “The Authoutity/Host could not be parsed”**
The below error can be appear while accessing Web Service URL proprty in SSRS configuration manager and the main reason behind is a broken\invalid <UrlString> tag.
To confirm this go to location mentioned below and open rsreportserver.XML file in notepad. \Program Files\Microsoft SQL Server\MSRS10.SQL2008_PROD\Reporting Services\ReportServer
Correct the <UrlString> </URLString> accordingly and save the file, and it should work now.
**Error: “SQL Server 2008 Reporting Services Configuration Manager: “Invalid namespace”**
Cause 1. On a computer that is running Windows Vista, you install a default instance of Microsoft SQL Server 2005 Service Pack 2 or a later version of SQL Server 2005. On the same computer, you install a named instance of Microsoft SQL Server 2008. For example, you install an instance that is named “SQL2008.”
In this scenario, you may receive an error message that resembles the following when you start the SQL Server 2008 Reporting Services Configuration Manager:
No report servers were found. Details: Invalid namespace
This problem occurs if the SQL Server 2008 Reporting Services Configuration Manager points to the SQL Server 2005 Reporting Services instance and it cannot find the SQL Server 2008 instance.
As per MS there are 2 resolutions for this issue
Method 1: Install the Cumulative update package 1 for SQL Server 2008
For more information about how to install the Cumulative update package 1 for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
Method 2: Add a WMI namespace
Add a WMI namespace that corresponds to the namespace that the SQL Server 2008 Reporting Services Configuration Manager tool is trying to use. To do this, follow these steps:
Note This procedure refers to a sample instance that is named “SQL2008.”
- Locate the Reportingservices.mof file for the SQL Reporting Services 2008 instance that is named “SQL2008.” By default, this file is located in the following folder:
C:\Progam Files\Microsoft SQL Server\MSRS10.SQL2008\Reporting Services\ReportServer\bin
- Save or copy the Reportingservices.mof to a file that has a unique name, such as Reportingservicesalt.mof.
- Open Reportingservicealt.mof file by using a text editor, such as Notepad.
- On the Edit menu, click Replace.
- In the Find what area, type the changed instance name, such as RS_SQL2008.
- In the Replace with area, type the unmodified instance name, such as SQL2008.
- Click Replace All.
- Save the file, and then exit Notepad.
- Open a command prompt, and then move to the same folder that you used in step 1.
Type mofcomp reportingservicesalt.mof and then press ENTER.
**Error: SQL Services not starting, the service failed or the service did not start in a timely fashion.**
This was a newly installed SQL Server and after the restart the reporting services not starting and failed every time when we try to start it. We checked all the areas and found everything fine.
Then we came to know that this is a kind of generic error; the Microsoft Windows Service Control Manager controls the state (i.e., started, stopped, paused, etc.) of all installed Windows services and by default, the Service Control Manager will wait 30,000 milliseconds (30 seconds) for a service to respond but certain configurations, technical restrictions, or performance issues may result in the service taking longer than 30 seconds to start.
Resolution: By editing or creating the ServicesPipeTimeout DWORD value, the Service Control Manager Timeout period can be overridden, thereby giving the service more time to start up and report ready to the Service.
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
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:
On the Edit menu, point to New, and then click DWORD Value.
Type ServicesPipeTimeout, and then press ENTER.
- 4. Right-click ServicesPipeTimeout, and then click Modify.
5. Click Decimal, type 60000, and then click OK.
6. This value represents the time in milliseconds before a service times out.
**Error\Problem: Closing the parameter panel loses parameters when navigating between reports in SP integrated mode**
We are performing some testing on SSRS in which we have a number of reports that are linked together with report actions all surfaced within a Report Viewer web part in SharePoint Integrated Mode. We are on SharePoint 2010 Enterprise RTM and SQL Server 2008 R2 RTM. When user is trying to view a report and closes the parameters panel on the web part by clicking the bar on the right side and then uses one of the links in the report to go to a subsequent report via a report action (parameters are passed by the report action) and then re-opens the parameter panel on the child report, all of the parameters will be gone. Clicking the apply button again (or the refresh button on the report viewer toolbar) re-renders the report and the parameters reappear.
Resolution: Please apply Cumulative update package 2 for SQL Server 2008 R2 Service Pack 1
For more details: