Following mjp's response to my earlier post re recycling app pools. After a LOT of rooting around I finally concluded that the IIS app pool idle timeout must be the reason I kept losing sessions, regardless of settings for auth and session timeouts. I was about to ask whether the IIS idle timeout was indeed set at the default 20 mins. I appreciate that this makes sense in a shared hosting environment - no problem. The only solution to this I can think of is to use DASP's scheduled task feature to make a request every 15 mins which will effectively act as a sort of keep-alive for my app pool, since I can't rely on there not being times when no user makes a request for 20 mins, and thus all lose their sessions and session data after the recycle. Grateful for any comments on whether this is a feasible solution to the problem, or help if I have misunderstood this. /emoticons/smile.gif
The scheduled task would certainly help, and it is probably the simplest way to try to force a "keep-alive." Assuming there is even a minimal amount of activity on the site you shouldsee a lot less timeoutshitting it with a scheduled task every 15 minutes, even if the task doesn't run exactly every 15 minutes. mjp --- DiscountASP.NET
