none
Report session timeout and other errors suddenly happening after over a year of no problems... RRS feed

  • Question

  • Hello,

    Reports have been running perfectly for a long time. All of a sudden, today they are not the same. Now getting session timeout errors and the stuff below. Also the toggle image intermittently disappears.

    I have placed this in the config file:

    <system.web>
            <sessionState mode="InProc" timeout="1440" />
            <httpRuntime maxRequestLength="20000" executionTimeout="1440"/>

    and

    <httpHandlers>
                <add path="Reserved.ReportViewerWebControl.axd" verb="*" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
                    validate="false" />

     

    But still errors keep happening. Any ideas would be helpful. Here is the EventViewer error:

    Event code: 3005
    Event message: An unhandled exception has occurred.
    Event time: 6/23/2008 2:07:25 PM
    Event time (UTC): 6/23/2008 6:07:25 PM
    Event ID: a4afc02fdaf247d783ac5620fe75b2ee
    Event sequence: 4
    Event occurrence: 1
    Event detail code: 0
     
    Application information:
        Application domain: /LM/W3SVC/1/Root/reports-1-128587180452129940
        Trust level: Full
        Application Virtual Path: /qareports
        Application Path: C:\Program Files\Reports\
        Machine name: HOST
     
    Process information:
        Process ID: 5276
        Process name: w3wp.exe
        Account name: HOST\Administrator
     
    Exception information:
        Exception type: AspNetSessionExpiredException
        Exception message: ASP.NET session has expired
     
    Request information:
        Request URL: http://host/path/Reserved.ReportViewerWebControl.axd?Mode=true&ReportID=4bcdefaad29748c0b606046b673f2426&ControlID=87790dc8be5d490b8509067dcb2e209c&Culture=1033&UICulture=1033&ReportStack=1&OpType=ReportImage&ResourceStreamID=8.0.50727.762ToggleMinus.gif
        Request path: /path/Reserved.ReportViewerWebControl.axd
        User host address: 10.68.234.42
        User: 
        Is authenticated: False
        Authentication Type: 
        Thread account name: HOST\Administrator
     
    Thread information:
        Thread ID: 1
        Thread account name: HOST\Administrator
        Is impersonating: False
        Stack trace:    at Microsoft.Reporting.WebForms.ReportDataOperation..ctor()
       at Microsoft.Reporting.WebForms.HttpHandler.GetHandler()
       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)
     

    --PhB
    Tuesday, June 24, 2008 1:51 PM

Answers

  • ...also, I found that App Pools' Max Number of Worker Processes had been set to 5 when it ought to have been 1. After making this change and removing the above config changes all is back to normal.

    So, Max Number of Worker Processes should be 1!
    --PhB
    • Marked as answer by PhrankBooth Tuesday, June 24, 2008 5:55 PM
    Tuesday, June 24, 2008 5:55 PM

All replies

  • After a couple of days of looking at this, I finally fixed it by adding this to the web.config file:

    <sessionState mode="InProc" timeout="1440"  stateConnectionString="tcpip=127.0.0.1:42424" stateNetworkTimeout="864000" cookieless="false"/>

    However, I have no idea why it would have stopped failing in the first place and I have no idea why this would work.

    But there it is.

    Hope it helps someone.

    --PhB
    Tuesday, June 24, 2008 2:59 PM
  • ...also, I found that App Pools' Max Number of Worker Processes had been set to 5 when it ought to have been 1. After making this change and removing the above config changes all is back to normal.

    So, Max Number of Worker Processes should be 1!
    --PhB
    • Marked as answer by PhrankBooth Tuesday, June 24, 2008 5:55 PM
    Tuesday, June 24, 2008 5:55 PM
  • Hello sir,

    I have also this problem in my asp.net application. and as par your suggestion <sessionState mode="InProc" timeout="1440"  stateConnectionString="tcpip=127.0.0.1:42424" stateNetworkTimeout="864000" cookieless="false"/> your problem has been solved.

    I want to know sir in this session tag your are using stateConnectionString="tcpip=127.0.0.1:42424", this is your database id & port or just it is a way (default) to solve this problem? Can i use this in same way or not? Please sir reply me.

    Waiting for your reply, also my mail id is anshu.jaipur2009@gmail.com.

    Thanks and Regards.

     

    Wednesday, September 12, 2012 8:58 AM