We are getting "Session has expired. Please, refresh the page." issue in the telerik report viewer while opening in IE8 browser. This issue only occurs in IE8 and SSO mode over SSL. The issue doesn't occurs in other version of IE browser like 10, 11 and in Chrome and Mozilla browsers. The application is hosted on IIS server. The report viewer is placed inside in a user control which is again placed in a user control and that is in a master page. The report viewer is getting bind on click of link button. Could you please suggest why are we getting "Session expired error". We also tried to analyse the issue in Fiddler but get the "SessionHasExpiredMessage" as below in Textview:
<html><head><title>Error</title></head><body style='overflow:hidden;'><script type='text/javascript'>window.ErrorMessage = "<div style=\"text-align:left;padding-left:10px;padding-right:10px;\"><br /> <span style=\"font-family:'Verdana';font-size:18pt;color:Red;text-align:left;\">##SessionHasExpiredError##<hr size=1 style='width:100%; color:silver' /></span><br/><span style='color: maroon; font-size: 14pt; text-align:left; font-family:\"Verdana\"; font-style:italic'>##SessionHasExpiredMessage##</span><br /></div>";</script></body></html>3 Answers, 1 is accepted
0
Hello Vijay,
The old ASP.NET WebForms ReportViewer depends on the ASP.NET Session and ASP.NET Cache in order to preserve reports' resources between requests.
Please check if the application's session state mode is configured based on the hosting, and if reports cover the requirements for the specific session state mode. Also check if the browser accepts cookies. More details are listed in the Report is unavailable or session has expired error message KB article.
Note that IE8 is not supported as it is not HTML5 compliant browser. The Reporting engine uses fallback mechanisms to render reports for preview in non HTML5 compliant browsers, which does not guarantee the browser can execute the viewer control's scripts. For more details, please check Design Considerations for HTML Rendering.
I hope this helps.
Regards,
Stef
Telerik
The old ASP.NET WebForms ReportViewer depends on the ASP.NET Session and ASP.NET Cache in order to preserve reports' resources between requests.
Please check if the application's session state mode is configured based on the hosting, and if reports cover the requirements for the specific session state mode. Also check if the browser accepts cookies. More details are listed in the Report is unavailable or session has expired error message KB article.
Note that IE8 is not supported as it is not HTML5 compliant browser. The Reporting engine uses fallback mechanisms to render reports for preview in non HTML5 compliant browsers, which does not guarantee the browser can execute the viewer control's scripts. For more details, please check Design Considerations for HTML Rendering.
I hope this helps.
Regards,
Stef
Telerik
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Feedback Portal
and vote to affect the priority of the items
0
Vijay
Top achievements
Rank 1
Rank 1
answered on 18 Jan 2016, 10:38 AM
Hi Stef,
We have created the application in non-SSO and SSO mode. The Telerik ReportViewer works well in IE8 in non-SSO over SSL. The Session expired issue occurs only in SSO mode for IE8. As suggested we are using Telerik ReportViewer not ASP.NET WebForms ReportViewer and also the ASP.NET session is not getting expired as we are able to access the application after closing the ReportViewer. Cookies are enabled in IE8 browser. As Telerik ReportViewer works well in IE8 in non-SSO mode, it should not be the HTML5 compliant browser issue.
We have created the application in non-SSO and SSO mode. The Telerik ReportViewer works well in IE8 in non-SSO over SSL. The Session expired issue occurs only in SSO mode for IE8. As suggested we are using Telerik ReportViewer not ASP.NET WebForms ReportViewer and also the ASP.NET session is not getting expired as we are able to access the application after closing the ReportViewer. Cookies are enabled in IE8 browser. As Telerik ReportViewer works well in IE8 in non-SSO mode, it should not be the HTML5 compliant browser issue.
0
Hello Vijay,
Based on your screenshot, you are using the old ASP.NET WebForms ReportViewer, which uses the ASP.NET Session. Thus the session state mode of the web application is important for how reports must be implemented - Design Considerations for Out-proc Session State.
Also the Session should not be cleared manually to avoid losing resources stored by the viewer in it. The rest settings are related to cookies, session expiration time and how the application is hosted - Report is unavailable or session has expired error message.
The recommended viewer is the HTML5 Viewer and its MVC and ASP.NET WebForms wrappers. The HTML5 Viewer does not rely on the ASP.NET Session.
Regards,
Stef
Telerik
Based on your screenshot, you are using the old ASP.NET WebForms ReportViewer, which uses the ASP.NET Session. Thus the session state mode of the web application is important for how reports must be implemented - Design Considerations for Out-proc Session State.
Also the Session should not be cleared manually to avoid losing resources stored by the viewer in it. The rest settings are related to cookies, session expiration time and how the application is hosted - Report is unavailable or session has expired error message.
The recommended viewer is the HTML5 Viewer and its MVC and ASP.NET WebForms wrappers. The HTML5 Viewer does not rely on the ASP.NET Session.
Regards,
Stef
Telerik
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Feedback Portal
and vote to affect the priority of the items