have relevant question for this old posting. Goal in my space is to reduce the quantities of this error generated in the log files after night 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)

If I set the SessionKeepAlive to false 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.