views:

67

answers:

2

I have checked the servers (Win Server 2003) application event logs for the following problem http://support.microsoft.com/kb/308097 which doesn't show up. It just appears that sessions drop randomly for random users

It's a single server setup, no web farms and no load balancing

Even though the issue I point to above doesn't occur in the logs, is it worth increasing the stateNetworkTimeout attribute anyway? The configuration at the moment is simply

<sessionState mode="StateServer" cookieless="false" stateConnectionString="tcpip=localhost:42424" timeout="60"/>

UPDATES:

Using FormsAuth and the Timeout is set to 60

IIS6 Settings

  1. Recycle worker processes (in minutes) = 120
  2. Recycle worker processes (number of requests) = 35000
  3. Recycle worker processes at the following times = Unchecked
  4. Maximum virtual memory = Unchecked
  5. Maximum used memory = Unchecked
  6. Shutdown worker processes after being idle = 90
  7. Limit the kernel request queue = 1500
  8. Everthing else = Unchecked
A: 

Are you using Forms Auth? If so, what is it's timeout set to?

Nicholas H
Yep Forms Auth, the timeout is set to 60
Nick Allen - Tungle139
What about your application pool settings for IIS?
Nicholas H
Updated the question. Thanks
Nick Allen - Tungle139
A: 

you also need to set the timeout in forms authentication section (30 min by default)

http://weblogs.asp.net/scottgu/archive/2005/11/08/430011.aspx

Sonic Soul