Dear all,

When I deploy my web project into my Web server,everything is work,but except the report does not work properly.

The config of my webserver is win2003 with IIS 6.0.And Imake use of the report in the local processing mode and set "sessions state mode=InProc","cookieless mode=UseCookie"on the page of the state management in IIS.

The error message is showed below

Server Error in '/' Application.

---

ASP.NET session has expired

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: Microsoft.Reporting.WebForms.AspNetSessionExpiredException: ASP.NET session has expired

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[AspNetSessionExpiredException: ASP.NET session has expired] Microsoft.Reporting.WebForms.ReportDataOperation..ctor() +683 Microsoft.Reporting.WebForms.HttpHandler.GetHandler() +553 Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) +10 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +154 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

Dear Brian:

It is still giving the same error, even if I set the cookieless mode to true or false. I am using custom database on SQL 2000 to set the session state. Can you please advice. If there is a bug do we have patch.

Regards

Gaurav

I apologize, I had things backwards in my original post.  Our known issue is with cookieless session.  Cookie sessions (which you had set originally and is the default) should be fine.

Are you receiving the error immediately or do you need to let the browser sit idle for a while?  Have you confirmed that your browser has cookies enabled?  Which browser are you using?

After I add "ReportViewer1.localReport.Refresh()" in the PageLoad() method in the page that contain Report Viewer.Then it works properly ,but I don't knowwhy it work.The brower that I used is IE and it is support cookies.

Now I have another problem that I need to deploy my source code,otherwise the report viewer doesn't work properly.I have tried to deploy the source code for report only,it works but the export function cause error.Can anyonehelp me?

I alsoadd "<sessionstate stateConnectionString="tcpip=127.0.0.1:8001"/>" into the web.configfile

But I don't know why it works.

I I am having the same issue, but mine only occurs once when the application starts. If I press Refresh it works fine. I've set cookieless="false" and I've set cookieless="true" with the same results.

I do want to ask Microsoft when we can see a fix to this problem? I would also guess that additional bugs to VS 2005 also needs to occur. Even though VS 2005 is an absolutely terrific product, I think it's completely arrogant on Microsoft's part not to deploy an SP release on VS 2005.

We are investigating this issue and I will report back as soon as I have more information.

For information on the Visual Studio 2005 Service Pack, please look here: http://msdn.microsoft.com/vstudio/support/servicing

Hi, I am getting the same "ASP.NET session has expired" error in the report viewer control.

1. The error page doesn't appear immediately.

2. I am running sql server 2000 and VS2005

3.Tried without success:

a) Refresh on page load,

b) <sessionstate stateConnectionString="tcpip=127.0.0.1:8001"/> ,

c) cookieless="false"

4. Can't see a bin folder in my app folder?

The app works fine from the developer's machine.

Any suggestion will be highly appreciated!!

If you cannot work with it, you cancopy your whole project with source code to the webserver.(it means that your source code will be seen by other)

It may be work!

I hope it can help you......

I too have been struggling with this session expiration message. My work-around has been to set the session timeout to 1440 min (1 day). This seems to work, most of the time. I would love to hear the MS solution to this...

I have also been unable to solve the 'Execution 'sessionID' not found.' message that appears in the ReportViewer in my web app. I have not been able to pinpoint exactly why this error occurs, but it seems to show up in the ReportViewer every so often. If I choose and render another report, it works just fine. If anyone has any suggestions about this one, let me know please.

thanks,

Michael R.

I was using the machine name when accessing the application. My machine name includes an underscore: abc_1234 and that was creating the problem.

I tried using the ip address and it works just fine.

Hope this helps you as well.

I was having the same problem. I had to change the reportviewer AsyncRendering property to False in order for the problem to go away. It seems there is a problem with the controls asyncronous process.

Performance was somewhat impacted but at least it generates the report without an error.

Brian,

I was able to work around the session timeout error by changing the reportviewer's AsyncRendering property to False.

I suspect there may be a problem with the underying Asyncronous processing in .NET 2.0. I have also experienced some problems with IAsysncReult interface.

Any update on the status of this issue?

Brian Hartman-

Any update on the "ASP.NET Session Expired" error message. Haven't heard anything in this thread for about 4 months.

I assume it will be fixed in Vis Studio 2005 SP1 which is supposedly due Q3 2006 (running short on time for that to be true ;-) In the meantime, is there a hotfix number you can refer us to? Or a workaround?

Thanks.

Hello Brian,

Has there been any updates on this issue? I'm also encounteringthe "ASP.NET session has expired"error inside of the ReportViewer control when my application is deployed to a load-balanced environment. My web.config sessionState settings are the default settings (as seen here.)

<sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes" cookieless="false" timeout="20"/>

Your timely response is appreciated as I'm supposed to rollout a production version soon and this bug is a show-stopper.

Thanks, Erik

In regards to using a SQL Server db to save the ASP.NET session info, I've tried it using only the core objects needed to hook up to a report server and retrieve and render a report. However, I did not have any luck with this either because each object implementing ViewState needs to be serializable, and serializing the low-levelNetworkCredentials object (needed to hook up to the report server) pukes. If anyone has had luck with this, please let me know!

FYI. We turned affinity on on our web servers and things work great - no hokey code changes at all. We have the luxury of doing this because we're not supporting thousands of users.

Here's my runtime code:

My situation is that im getting asp.net session expired unless i shut asyncrendering off, which if I do that it causes the graphics on the report viewer control for sorting to be the dreaded red x (missing graphic). I've been reading others using a frame instead of the reportviewer control. Thinking about trying this maybe. I have another problem in that an ISAPI filter for single sign on purposes is causing me to have to keep this directory inside of the parent directory for the whole site. I have a 1.1xx framework main site, and this project sits inside a subfolder and is configured as .net 2.0. Again im frustrated in that i can get things to run locally. Any help anyone can provide is appreciated of course:)

Thanks, Mike

Does installing Visual Studio 2005 on web server solve this issue?

Thanks,

Tanmaya

I have spent the last 4 days working on this same issue and wanted to share what I have learned.

I have a user control that contains a reportviewer. I have recently upgraded VS to SP1. SP1 contains a newer version of the reportviewer.

I am using inProc for session state. Any time a report would run longer than about 40 minutes I would get the dreaded ASP session state error.

There are so many “States�to deal with that it gets confusing as to where to start. I have spent much of my time doing the shot gun approach. Hopefully you will not have to do that.

So here is how I would do it again:

1) Look at the “SessionAccessTimeout�on the Report Server. Each report has a unique ID that the Report Server uses to keep track. This information is stored in the ReportServerTempDB database. Look at the dbo.SessionData table. I made changes to this setting but it is very possible I did not need to. If you look at the Timeout column in the SessionData table you can see what your default is. If you look at the bottom of IE you can most likely see what session ID you are using. For more information on this setting and how to change it see: http://blogs.msdn.com/jgalla/ this is the only place I have seen this setting talked about. (The possible symptom of this is that the report would error out before it has run completely processed, but make changes here last.)

2) Next look at the session settings on the virtual directory that you are running the viewer from. In IIS right click on the virtual directory, go to the ASP.NET tab, click on “Edit Configuration�and then go to the “State Management�tab. Here is where the settings are for session state. This really just is a UI for making changes to the Web.config. I believe the default is 20 and is taken from the global settings for IIS. If you change this setting and anentry will be made in the Web.config under <system.web>. Some thing like <sessionState timeout=�20�/> if you set it to 120 minutes.

3) If you really do not want to change the session timeout for the whole website, you can change the settings on the control or page that the reportviewer is contained by. I have this as a variable that I can set per report (In my ascx control). The syntax is something like (VB) Me.Session.Timeout = “timeout in minutes� Each control on the page actually has access to page session state via the Session property. For more information on this go to: http://msdn2.microsoft.com/en-us/library/system.web.sessionstate.httpsessionstate(VS.80).aspx

4) How you set up your worker process recycling can greatly affect inProc session state. To see a great article on how IIS recycling affects inProc session state to: http://blogs.msdn.com/david.wang/archive/2005/09/19/Why_do_I_lose_ASP_Session_State_on_IIS6.aspx

I have changed settings on the ReportServer IIS but none of these settings are related (at least with my issue) to the session timeout.

There are also more issues you could run into if you are using the webfarm on IIS. I hope that some of you take less time on this than I did. Good luck!

Mark, you didn't mention if you had resolved the issue on your site. Do you still see the session timeout?

thanks,

michael

Hello Michael,

YES!!!!!

By adjusting the timeout in the control I have solved the issue in my situation. I did this because I did not want to change the session time out for the whole site. (Default is 20 minutes). If the report was to take longer to run than the time out I have specified, it would still error out.

OK, we ran into the "asp.net session timed out" error as well.

Reading this thread, I am pretty sure there are several different errors/problems occuring for various people.  The one we are having is when the user first hits the site...basically initializing their session.  So things like session time outs and the like do not really apply in this case.  I have tried twiddling with the session settings on the site with no effect that I can discern.  Simply closing the browser and hitting the site again causes the problem every time.  Additional refreshes of the page will not show the error.

Our topology consists of 2 virtual directories on the same web site.  One VD has a ReportViewer page and is fed information from the other virtual directory on the QueryString.  In the example I am providing below, one virtual directory has a single file...a simple html web page with two IFRames in it.  Each IFrame is pointed to a page in the other virtual directory that has a report viewer control on it.  The other virtual directory only has a default.asx page in it and a sample report rdl file.  The default.aspx page has a reportviewer controll on it and the page load event does nothing more than to feed it the report file name and a datatable object that is created in code...no database/sql required.

Here is a URL to the zipped up example:

http://www.ascmclarencoupe.com/misc/ReportViewerTest.zip

To reproduce this problem:

1.  Unzip the zip file.
2.  Copy the ReportViewerIFrame directory and the INNERMOST ReportViewerTest to the c:\inetpub\wwwroot directory.
3.  In IIS, right click on each directory and click properties.
4.  Click the "Create" button to create an application and virtual directory.

You now should have two virtual directories under your default web site.  Point your browser to http://<servername>/ReportViewerIFrame/iframe.htm and see the asp.net session timeout error happen in only one of the iframes.

This example is about as simple as I could make it.  I am hoping this post is complete enough and simple enough that maybe one of the Microsoft guys will notice it and run with it...please post back or email me if somebody in MS is looking at it....or tell me how dumb I am if this issue has been resolved or some other solution has been posted for this case.

My initial theory is that the browser is creating a race condition for one of the ReportViewers.  When the browser goes to pull the pages that are to be loaded in the IFrames from the ReportViewerTest virtual directory, the first ReportViewer is intializing the session and the other ReportViewer thinks that the session has been started and valid...but it isn't yet. 

Things I have noticed:

If you put everything under one virtual directory the problem seems to disappear (not an option for us...but may lead to a workaround). 
If you set the report viewer so that async=false, the problem goes away except for graphs which will get a big red x occasionaly.
A single ReportViewer IFrame does not cause a problem.
The event viewer will log an aspweb info message about a timed out session:

Hmmmm...not so much as a peep. Kind of a waste of effort on my part I guess.

We did figure out a workaround. We placed a hidden ReportViewer control on an aspx page that sets up a javascript timer to redirect to the actual report page after 1 millisecond. No "asp.net Expiration" errors or red "x"s....at least not yet.

-Mike

I'm gettinga similarproblem:

We get this if anyone tries to do an Excel or PDF export. We are using local reports in asp.net.
The export process takes several gig of memory and 85% cpu on a 4 cpu box and finally crashes.
This naturally destroys all the session memory. So for us the sympton is session time out,
but the cause is exports.

I noticed someone already wrote this, but is there a fix for it?

This has no affect for my situation.

After meaning weeks searching the message boards I finally broke down and called Microsoft Support cashing in one of my support tickets. To my delight, they actually fixed this issue for me. Like many of you, I was having the 'ASP.NET Session Expired' problem when displaying a page with the ReportViewer control inside of an iframe from another page.

Turns out, there is a known bug in IE6 and above regarding cookies and authentication. The following link

http://support.microsoft.com/default.aspx/kb/323752gave me instructions on resolving my issue. I used the P3P custom header approach and my app is now running smoothly.

This may not help all of you but maybe it does address some of you.

Thank you, thank you. Two days of headbanging round the internet and my problem is solved. Now to find out why report/printing requires cookies in Framework 2 whereas it didn't in 1.1.

Server Error in '/' Application.

---

ASP.NET session has expired

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: Microsoft.Reporting.WebForms.AspNetSessionExpiredException: ASP.NET session has expired

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Mlhoop -- did you solve your problem? I had the same problem - asp.net issue, fixed with asyncrendering off, but I now get a red x instead of the report. My report is rendered within an iframe.

I hate to piggy back an issue that has been around for a while but looks like this is still an active issue since the last posting was done in August.  And I'm encountering similar issues.  The report will render locally but when I deploy to a web server, I get no output and the page eventually times out.  I have tried a few of the suggestions listed here but no luck in resolving the problem.  Please let me know if I need to supply more information.

Development environment XP sp2, VS2005, C#
Deployed on Windows2000 2.0 framework
Attempted to render report while logged into the web server (IE 6.0)
Attempted to render report from development machine hitting intranet based URL (local IE is 8.0).

I'm feeding the report my own datasource since it's coming from DB2 instead of SQL Server.
Here is my code snippet:

aspx portion:

<rsweb:ReportViewer ID="ReportViewer1" runat="server" BorderWidth="5px" <br />	Width="100%" Height="100%" Font-Names="Verdana" Font-Size="8pt" <br />	Visible="false" AsyncRendering="false">
	<LocalReport ReportPath="Reports\RptAudit.rdlc"></LocalReport>
</rsweb:ReportViewer>

C# code behind:

this.ReportViewer1.Visible = true;
//render report
ReportViewer1.ProcessingMode = ProcessingMode.Local;
this.ReportViewer1.LocalReport.SetParameters(paramList);
this.ReportViewer1.LocalReport.DataSources.Clear();
ReportDataSource reportData = new ReportDataSource("DataSet2_AUDIT_LOG", m_DS.Tables[0]);
this.ReportViewer1.LocalReport.DataSources.Add(reportData);
this.ReportViewer1.LocalReport.Refresh();

The data in my dev environiment is the same data that works on this dev web server.  I have converted from Crystal Repors 9.1 to use the ReportViewer control so I can remove a 3rd party dependency.  The report had worked in CR9.1 before removing from this deployment instance.

Any help is greatly appreciated.

Regards,

Mike