Microsoft Knowledge Base Email Alertz

FIX: The ASP.NET State Server Sessions Active counter may be incremented incorrectly if you change the Session.TimeOut value on a computer that is running the .NET Framework 2.0 SP1 or the .NET Framework 3.5 SP1

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 954461 - Last Review: January 13, 2009 - Revision: 1.0

FIX: The ASP.NET State Server Sessions Active counter may be incremented incorrectly if you change the "Session.TimeOut" value on a computer that is running the .NET Framework 2.0 SP1 or the .NET Framework 3.5 SP1

On This Page

SYMPTOMS

You configure a computer that is running the .NET Framework 2.0 Service Pack 1 (SP1) or the .NET Framework 3.5 SP1 as a state server to maintain out-of-process session states for ASP.NET. On this computer, you run an application to store the session state and to monitor the State Server Sessions Active counter. If you change the Session.TimeOut value, the counter may be incremented incorrectly. A large value may appear in the counter when the session is reset.

RESOLUTION

The .NET Framework 3.5 SP1

If you are using the .NET Framework 3.5 SP1, install the update that is described in KB 959209 to resolve this problem.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
959209  (http://kbalertz.com/Feedback.aspx?kbNumber=959209/ ) An update for the .NET Framework 3.5 Service Pack 1 is available

The .NET Framework 2.0 SP1

If you are using the .NET Framework 2.0 SP1, install the hotfix that is described in this article to resolve this problem.

Note If you upgrade the .NET Framework 2.0 SP1 to the .NET Framework 3.5 SP1, you still have to install the update that is described in KB 959209 even if you already have the hotfix that is described in this article installed.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


NoteApply this hotfix only to servers that are running the IIS Session State service.

Prerequisites

You must have the .NET Framework 2.0 SP1 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, you have to stop and restart IIS and the ASP.NET State Service.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

x86 versions on Windows Server 2003

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Aspnet_perf.dll2.0.50727.184533,28822-Jul-2008Jul-200804:00x86
Aspnet_wp.exe2.0.50727.184533,28022-Jul-2008Jul-200804:00x86
aspnet_perf2.iniNot applicable895,67822-Jul-2008Jul-200804:00Not applicable
aspnet_perf.hNot applicable6,53722-Jul-2008Jul-200804:00Not applicable
aspnet_perf.iniNot applicable897,67622-Jul-2008Jul-200804:00Not applicable
aspnet_state_perf.hNot applicable31822-Jul-2008Jul-200804:00Not applicable
System.web.dll2.0.50727.18455,185,53622-Jul-2008Jul-200804:00x86
Webengine.dll2.0.50727.1845433,66422-Jul-2008Jul-200804:00x86

x64 versions on Windows Server 2003

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Aspnet_perf.dll2.0.50727.184540,96822-Jul-200802:03x64
Aspnet_perf.dll2.0.50727.184533,28822-Jul-200804:00x86
Aspnet_wp.exe2.0.50727.184545,05622-Jul-200802:03x64
Aspnet_wp.exe2.0.50727.184533,28022-Jul-200804:00x86
aspnet_perf2.iniNot applicable895,68421-Jul-200822:19Not applicable
aspnet_perf2.iniNot applicable895,67822-Jul-200804:00Not applicable
aspnet_perf.hNot applicable6,53721-Jul-200822:12Not applicable
aspnet_perf.hNot applicable6,53722-Jul-200804:00Not applicable
aspnet_perf.iniNot applicable897,68221-Jul-200822:19Not applicable
aspnet_perf.iniNot applicable897,67622-Jul-200804:00Not applicable
aspnet_state_perf.iniNot applicable31821-Jul-200822:12Not applicable
aspnet_state_perf.hNot applicable31822-Jul-200804:00Not applicable
System.web.dll2.0.50727.18455,263,36022-Jul-200802:03x64
System.web.dll2.0.50727.18455,185,53622-Jul-200804:00x86
Webengine.dll2.0.50727.1845737,79222-Jul-200802:03x64
Webengine.dll2.0.50727.1845433,66422-Jul-200804:00x86

IA-64 versions on Windows Server 2003

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Aspnet_perf.dll2.0.50727.184533,28822-Jul-200804:00x86
Aspnet_perf.dll2.0.50727.184582,44022-Jul-200804:04IA-64
Aspnet_wp.exe2.0.50727.184533,28022-Jul-200804:00x86
Aspnet_wp.exe2.0.50727.184583,96822-Jul-200804:04IA-64
aspnet_perf2.iniNot applicable895,68421-Jul-200822:22Not applicable
aspnet_perf2.iniNot applicable895,67822-Jul-200804:00Not applicable
aspnet_perf.hNot applicable6,53721-Jul-200822:14Not applicable
aspnet_perf.hNot applicable6,53722-Jul-200804:00Not applicable
aspnet_perf.iniNot applicable897,68221-Jul-200822:22Not applicable
aspnet_perf.iniNot applicable897,67622-Jul-200804:00Not applicable
aspnet_state_perf.iniNot applicable31821-Jul-200822:14Not applicable
aspnet_state_perf.hNot applicable31822-Jul-200804:00Not applicable
System.web.dll2.0.50727.18455,185,53622-Jul-200804:00x86
System.web.dll2.0.50727.18454,743,16822-Jul-200804:04IA-64
Webengine.dll2.0.50727.1845433,66422-Jul-200804:00x86
Webengine.dll2.0.50727.18451,213,95222-Jul-200804:04IA-64

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about how to configure an Out-of-Process Session State by using the ASP.NET State Service, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/cc775821.aspx (http://technet.microsoft.com/en-us/library/cc775821.aspx)

APPLIES TO
  • Microsoft .NET Framework 2.0 Service Pack 1 (x86)
  • Microsoft .NET Framework 3.5 Service Pack 1
Keywords: 
kbsurveynew kbhotfixserver kbexpertiseadvanced kbqfe KB954461
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate