what are consequences to user experience after setting SessionKeepAlive to false?

• KoldCoffee

  SSCoach

  Points: 18971

  More actions

  March 2, 2015 at 10:08 am

  #298234

  Goal in my space is to reduce the quantities of the below error generated in the log files after nightly IIS reset:

  Exception:

  Source: Microsoft.ReportViewer.WebForms

  Message: ASP.NET session has expired or could not be found

  StackTrace: at Microsoft.Reporting.WebForms.ViewerDataOperation..ctor()

  at Microsoft.Reporting.WebForms.SessionKeepAliveOperation..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.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

  at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

  Googling it I see frequently advised to set the SessionKeepAlive to false.

  MY 2 QUESTIONS

  If I do that just before our nightly IIS resets, and then back to true after the reset, then

  (1) will that minimize impact to client experience overall ie cause timeouts only at time of IIS reset?

  (2) will users in the middle of actively editing a report in Report Builder loose their changes? Say they started editing a report at 11pm, IIS reset at 11:01pm, and a report in report builder was in the middle of being editted. (what would user experience be?).

  Thanks in advance.