Intermittent loss of data in trace.axd RRS feed

  • Question

  • User-506338690 posted


    I am troubleshooting intermittent (about 1.5% of the time) in our application. The issues only happen for one of our many customers and we cannot reproduce it, so I believe it to be environmental but have not proved that. This is a Web Forms application on .NET 4.5. The issue can be reproduced on a search page - the user performs search after search until it fails. Refreshing the page will cause it to work again.


    In order to troubleshoot, I asked the customer to enable tracing in their web.config. I then asked them to reproduce the issue and examined the trace output. The trace for that request was strange:

    • Request Details Section: Session ID is blank
    • Control Tree Section: Column headers are there, but there are no entries
    • Session State Section: Column headers are there, but there are no entries
    • Application State Section: Column headers are there, but there are no entries
    • Request Cookies: Column headers are there, but there are no entries
    • Response Headers Collection Section: completely missing

    The trace for the requests before and after the issue occurred are normal: I see the session id, control tree, session state, application state, etc.

    What I've Checked

    • Tried logging into the web server and hitting the page via localhost in order to rule out the load balancer. We could still reproduce the issue.
    • Temporarily turned off virus scanner, thinking maybe it was touching the web.config and causing application restarts. The problem could still be reproduced.
    • Ran Perfmon and checked Application Restarts - numbers look fine.


    What would cause some information to go missing from the trace.axd? Is it proof that session state is being lost (among other things), or is it possibly a red herring? This weird trace is 100% correlated with the intermittent issue (i.e. whenever the issue happens, we get the weird trace).

    Friday, April 27, 2018 1:05 PM

All replies

  • User283571144 posted

    Hi pandojc,

    According to your description, we couldn't directly find the reason why it return nothing to client side.

    Does the application show any error when you reproduce the issue?

    It sounds like the client side doesn't send the request with the right information.

    Does the client side browser send too many request to server?

    If you could post more details information, it will be more easily for us to find the reason and solution.

    Best Regards,


    Monday, April 30, 2018 5:49 AM