StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<blockquote> <p>That's awfully suspicious to happen right at that time.</p> </blockquote> <p>I would agree, but it seems that in step #4 you redirect off the site, and then the user does data entry. If a user occasionally takes 10-20 minutes to enter that information (due to distraction, etc.), it makes it much more likely than if it were just a simple race condition.</p> <p>If you still have the data from all the errors, you may be able to look back to see if you can find a pattern to the times when this happens (or every xx hours--see below).</p> <ol> <li>Check your IIS settings to see when the app pool recycles. Does it recycle around 4am every night? Is it on a rolling schedule? By default, IIS recycles on some odd number of hours for some reason (I think every 28 hours).</li> <li>Get off of InProc Session state and into State Server (or SQL). InProc is only going to cause you pain anyway in the long run. Note that when you make this change, you have to ensure that all objects you put into session are serializable, otherwise you will get errors. InProc does not require objects to be serialized in session.</li> </ol> <p><strong>Edit:</strong> Ok, to check your app pool recycling:</p> <ol> <li>In IIS Manager, select the appropriate app pool and select Advanced Settings (right click or use right side menu).</li> <li>Scroll to the bottom, to section Recycling</li> <li>Regular Time Interval will reset the app pool every xx minutes. The default is 1740 minutes, or every 29 hours.</li> <li>The Specific Times setting allows you to set a scheduled time for it to recycle.</li> </ol> <p>In general, you DO want to recycle the app pool periodically (probably daily).</p> <p>To answer your second question: <strong>if</strong> this is indeed the cause, it's not a question of timeout; it's a question of whether the app pool recycles during the period of time between when they are redirected away and when they get redirected back. Changing your session state to something other than InProc should solve this problem.</p> <p>That said, the session expiring could ALSO be the cause of this, so setting your session timeout to a larger value could also resolve this.</p> <p>If you take a more extensive look at the logs during periods of time when this happened, it might give more clues to what is happening.</p> <p><strong>Edit #2</strong></p> <p>See if you can isolate the occurrences of the error in the logs. If you can, see if there is a pattern to the browser that is being used. I would also look for other patterns to see if anything jumps out.</p> <p>You might just test with a bunch of different browsers (including mobile) to see if you can reproduce. Also, try different versions of IE and different security settings on IE.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload