FIX: Actual property values of memory properties differ from the values that you manually set when you enable application pool recycling based on memory usage in IIS 6.0

Consider the following scenario. You have a Microsoft Windows Server 2003 Service Pack 1 (SP1)-based computer that is running Microsoft Internet Information Services (IIS) 6.0. You configure IIS to enable application pool recycling based on memory usage. In this scenario, you experience one of the following problems:

Problem 1

When you manually set the value of the PeriodicRestartMemory property to a value that is more than 4194303 KB, the actual PeriodicRestartMemory property value reverts to 512 MB.

Problem 2

When you use IIS Manager to set the value of the Maximum virtual memory property to a value that is more than 4095 MB, the actual Maximum virtual memory property value reverts to 512 MB.

Problem 3

When you set the value of the PeriodicRestartPrivateMemory property to a value that is more than 3145728 KB, the actual PeriodicRestartPrivateMemory property value reverts to 0.

Problem 4

When you use IIS Manager to set the value of the Maximum used memory property to a value that is more than 3072 MB, the actual Maximum virtual memory property value reverts to 0.

Additionally, when you experience Problem 1 or Problem 2, the following error message is logged in the system event log:Note VirtualMemorySize represents the virtual memory size that you configure.

When you experience Problem 3 or Problem 4, the following error message is logged in the system event log:Note VirtualMemorySize represents the virtual memory size that you configured.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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: 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.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 SP1 installed on the computer.

Restart requirement

You must restart the computer after you apply this hotfix.

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.

Windows Server 2003, x64-based versions

Windows Server 2003, Itanium-based versions

Note In Windows Server 2003, the described behavior is by design. This hotfix is not for any 32-bit versions of Windows Server 2003.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

This behavior is by design in the 32-bit and x86 versions of Windows Server 2003.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: