Few days ago while we were analyzing the results we saw that the Sessions Active value was not related to any profile we use – we saw a very large number e.g. 4294967114 that started to occur after a very short period of time.

Also as a side note if by any chance you do manual collect you will see that every collection makes the number goes down, this is weird!

I started searching for this symptom and i have found similar issue in State Server Sessions Active counter which tells me that there is a bug that would probably be in another section of code – only time will tell (we use In proc session handling).

Today while speaking with TAM of Microsoft i understood that the issue is currently open and pending investigation by Microsoft, i will update once we have any progress here.

Do you have any clever way to get the number of sessions until the above issue will be solved – but without code :) ?