One of our report server which is SSRS 2008 R2 (10.50.1720.0) started to crash intermittently. The IE failed with Internet Explorer cannot display the webpage. The report server log files didn’t contain any other information. After few mins (~2 mins), the report server came alive. This was happening intermittently.
The system log had error message
The SQL Server Reporting Services (MSSQLSERVER) service terminated unexpectedly. It has done this 3 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service
and the application log had captured the below error
Faulting application name: ReportingServicesService.exe, version: 2009.100.1720.0, time stamp: 0x4c135194
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000100000002
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
Though we could see in Google that many have faced this issue, no solution was available.
Apart from the crashing, one of the report which was running fine in SSRS 2008 failed with an error
library!ReportServer_0-2!16a4!09/06/2011-10:07:12:: i INFO: RenderForNewSession(‘/Internal Reports/Report1’)
processing!ReportServer_0-2!16a4!09/06/2011-10:07:12:: e ERROR: An exception has occurred in data set ‘Dataset1’. Details: System.OverflowException: Value was either too large or too small for an Int32.
at System.Decimal.ToInt32(Decimal d)
Google helped in identifying this link which says that SSRS 2008 R2 report fails if it is using BIGINT for Grouping and a Cumulative Update is available to resolve the same.
We decided to bring the SQL SERVER 2008 R2 to SP1. When we applied the SP, System Overflow exception vanished. Also the Report Server did not crash after that 🙂