Sql Reporting Services Web Control Report Generation Times Out Bogs Down IIS

We have a web site that is running on a windows 2003 server (IIS 6.0).  This web site has a reporting services web control that allows a user to run reports.  Everything has been working fine, but now there is one report that takes a long time to run (runs fine using the reporting services web site and runs fine through the web site when it is able to run for a shorter period of time).  When the report is accessed through the web site, the report control continues to run the normail report generation time, but ends in throwing a page cannot be displayed error (Web Server has closed the connection).  Looking in the reporting services logs it shows that the report actually throws an error between 1 and 3 minutes during generation, although the report continues to run.  After the report throws the error Ithe web site has to be stopped and restarted or the users internet browser has to be taken down and restarted, and sometimes both to be able to connect to the web site again.  To this point we have increased timeout settings for the asp script excecution timeout, the web site connection timeout, asp.net execution timeout, the sql server remote query execution timeout, but nothing has made a difference.  I provided the reporting services log below where the error occurs.  Any help would be greatly appreciated.  Thanks.

ibrary!ReportServer_0-1!1e6c!05/10/2011-11:38:44:: i INFO: RenderForNewSession('/Customer Summary/Summary')
runningjobs!ReportServer_0-1!1e60!05/10/2011-11:40:01:: i INFO: Adding: 1 running jobs to the database
runningjobs!ReportServer_0-1!1e90!05/10/2011-11:43:01:: i INFO: RunningJobContext.IsClientConnected; found orphaned request
processing!ReportServer_0-1!1e90!05/10/2011-11:43:01:: i INFO: DataPrefetch abort handler called for Report with ID=. Aborting data sources ...
processing!ReportServer_0-1!1e6c!05/10/2011-11:43:01:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: Report processing has been canceled by the user. , ;
 Info: Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: Report processing has been canceled by the user.
processing!ReportServer_0-1!1e6c!05/10/2011-11:43:01:: w WARN: Data set 'DataSet1': Report processing has been aborted.
processing!ReportServer_0-1!1e6c!05/10/2011-11:43:01:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: Report processing has been canceled by the user. , ;
 Info: Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: Report processing has been canceled by the user.
processing!ReportServer_0-1!1e6c!05/10/2011-11:43:01:: w WARN: Data source 'DataSource1': Report processing has been aborted.
processing!ReportServer_0-1!1e6c!05/10/2011-11:43:01:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: Report processing has been canceled by the user. , ;
 Info: Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: Report processing has been canceled by the user.
chunks!ReportServer_0-1!1e6c!05/10/2011-11:43:01:: w WARN: Rolling back shared chunk transaction for snapshot '2f91d8b6-8e22-46c6-a626-c862aeb13740', Permanent=False.
library!ReportServer_0-1!1e6c!05/10/2011-11:43:01:: w WARN: Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: Report processing has been canceled by the user.
webserver!ReportServer_0-1!1e6c!05/10/2011-11:43:01:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.RSException: Report processing has been canceled by the user.  ---> Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: Report processing has been canceled by the user.


rcblevinsAsked:
Who is Participating?
 
rcblevinsAuthor Commented:
I ended findin the problem.  The application pool was for some reason reaching it's maximum virtual memory limit and inititating a recycle of the process.  The application pool has a setting that determines how long it trys to gracefully shutdown the process and if that time is exceeded it forces the shutdown.  Anyway increasing allowed virtual memory and the time limit to 900 seconds has solved the issue.  Thanks for the help.
0
 
planoczCommented:
I do not know if this will help you but we placed this code in the web page for extended timeouts

Sample:
        Dim rs As New ReportExecutionService()
        Other code........        
         rs.Timeout = 600 * 1000   'timeout in milliseconds (defaults to 100,000 = 100 seconds)
0
 
rcblevinsAuthor Commented:
Thanks. Sorry I should have included this when I posted.  This is the code that is used to generate the report using the reportviewer control.  We incorporated some timeouts in it as well, but no luck.  It almost seems like it has something to do with the data part of the report.  Is there some kind of setting that will abandon the data processing if it doesn't reach a certain point within 60 to 180 seconds?  Thanks.

Dim ReportServerUrl As String
        Dim ReportName As String
        Dim ReportProject As String
        Dim paramList As Generic.List(Of ReportParameter)
        Dim pinfo As ReportParameterInfoCollection
               
        If Request.IsAuthenticated = False Then
            Response.Redirect("/Admin/AccessDenied.aspx")
		End If
		
        ReportName = Request.Params("ReportName")
        ReportServerUrl = "http://cei-sql/ReportServer"
        ReportProject = "WebReports"
       
        Server.ScriptTimeout = 1200
       
       
        ReportViewer.ServerReport.Timeout = -1

        ReportViewer.ProcessingMode = ProcessingMode.Remote

        ReportViewer.ServerReport.ReportServerUrl=  New System.Uri(ReportServerUrl)

        ReportViewer.ServerReport.ReportPath = "/Customer Summary/" + ReportName

        ReportViewer.ServerReport.ReportServerCredentials = new CustomReportCredentials("username","password", "CEI")

        paramList = New Generic.List(Of ReportParameter)

        pinfo = ReportViewer.ServerReport.GetParameters()
   
        For Each p As ReportParameterInfo In pinfo    
   
            paramList.Add(New ReportParameter(p.Name, Request.Params(p.Name)))
             
        Next
       
        Me.ReportViewer.ServerReport.SetParameters(paramList)  
       
        Me.ReportViewer.ServerReport.Refresh()
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
planoczCommented:
we have been using the regular parametervalue namespace for the parameters.
Has your  paramList = New Generic.List(Of ReportParameter) been working alright with SSRS?
0
 
rcblevinsAuthor Commented:
Yes, it sure has.  This has worked fine for a long time and this report has worked fine as well, but now it has been required to run a much larger amount of data.
0
 
rcblevinsAuthor Commented:
The problem ending up being the application pool that was associated to the web site.  It was forcibly shutting down the process because the virtually memory limit was met and the report was taking longer than the time limit that the application pool had in place to forcibly shut down the process if it could not shut it down gracefully.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.