Quantcast
Channel: SQL Server Reporting Services
Viewing all articles
Browse latest Browse all 1418

Repeated AspNetSessionExpiredException errors, even after session has ended

$
0
0

I have a traditional ASP.NET application written in VS 2010 against .NET 4.0.  It is hosted on a Windows 2003 server, with IIS 6.0.

Within the application, I have a page with an SSRS Report Viewer (version 10) on it.  This connects to our SQL Server 2008 Report Server.  (It is not R2.)

Every few months, I start to see errors, logged every nine minutes, that look like this:

Exception information:
Exception type: AspNetSessionExpiredException
Exception message: ASP.NET session has expired or could not be found
at Microsoft.Reporting.WebForms.ViewerDataOperation..ctor()
at Microsoft.Reporting.WebForms.HttpHandler.GetHandler(String operationType)
at Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

These errors are thrown repeatedly and without any clear end.  No user says they have ever seen evidence of them.  They continue after hours, long after everyone has logged out.  This latest "flare up" has gone on for nearly two days.  

In the past, the only thing that seemed to stop them was:

  1. Stopping the website in IIS
  2. Deleting the virtual directory for the application
  3. Re-creating the virtual directory for the application
  4. Starting the website again

What has not worked:

  1. Killing the w3wp process
  2. Forcing app pool recycling
  3. Bouncing our application server
  4. Bouncing our SQL Server

Trouble is, my so-called fix is no longer working at this point, either!

I considered writing some "shut up" logic to ignore errors of this specific type in global.asax, but this is unacceptable, because:

  1. My users are complaining about degraded performance
  2. The errors are still thrown, so performance degradation will continue regardless of what we do with the errors.

Any help would be tremendously appreciated!


Viewing all articles
Browse latest Browse all 1418

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>