Hi brikeler,
Do you mean it always sits at 4294967167 when it reaches this value?
Although it doesn't look like the server is a heavy load one. Based on my understanding, you could still try following code to keep track of active session number in code. This can be used to compare to the current Session Active number. The session time out value in web.conf file was changed to one minute to make it easier to monitor the change of the active session number. In my test, the number is same as the Session Active counter. Otherwise we may need to go further to find out what is going on with the Session Active counter.
//Global.asax
void Application_Start(object sender, EventArgs e)
{
Application["ActiveSession"] = 0;
}
....
void Session_Start(object sender, EventArgs e)
{
Application["ActiveSession"] = (int)Application["ActiveSession"] + 1;
}
void Session_End(object sender, EventArgs e)
{
Application["ActiveSession"] = (int)Application["ActiveSession"] - 1;
}
// .aspx
Response.Write(Application["ActiveSession"]);
// Web.conf
<sessionState mode="InProc" timeout="1" />