Home Dashboard Directory Help
Search

SQL Server Reporting Services (MSSQLSERVER) service terminated unexpectedly on 2008 R2 x64 by KenChee


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


1
0
Sign in
to vote
Type: Bug
ID: 654472
Opened: 3/29/2011 8:05:19 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

We are experiencing intermittent issues with our Reporting Services 2008 R2 x64 . The site keeps on dropping out and looking at the event viewer, it's showing this 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: 0x0000000000000000
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13

Looking also at the log files, this error co-relates to
library!ReportServer_0-6!34c!03/30/2011-12:58:05:: i INFO: RenderForNewSession('/report_name')
library!ReportServer_0-6!34c!03/30/2011-12:58:39:: Using folder C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\RSTempFiles for temporary files.
webserver!ReportServer_0-6!34c!03/30/2011-12:58:41:: i INFO: Processed report. Report='/report_name', Stream=''
rshost!rshost!34c!03/30/2011-12:58:41:: e ERROR: HttpPipelineCallback::SendResponse(): failed writing response.
rshost!rshost!34c!03/30/2011-12:58:41:: e ERROR: Failed with win32 error 0x10DD, pipeline=0x0000000065828AF0.
Details
Sign in to post a comment.
Posted by Microsoft on 6/14/2011 at 12:01 PM
Thank you for filing this issue. Unfortunately, without additional information we are unable to progress on this issue.

If you could upload a copy of the entire trace log file that shows when the issue is occurring and provide a description of what the user is doing at the time the issue occurs that would help us evalute the issue.

The issue will automatically be re-opened when you reply with more information.

Thanks,
-Lukasz
Posted by Microsoft on 4/13/2011 at 9:09 AM
Thank you for filing this issue. In order to identify the root cause of this issue, we need some more information.

Could you upload a copy of the entire trace log file that shows when the issue is occurring?
Also, could you desicribe what the user is doing at the time the issue occurs?

Thanks,
-Lukasz
Sign in to post a workaround.