Article ID: 923197 - Last Review: January 7, 2008 - Revision: 3.1 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.0On This PageSYMPTOMSConsider 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 1When 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 2When 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 3When 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 4When 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: Event Type: Warning
Event Source: W3SVC Event Category: None Event ID: 1041 Description: The 'Application Pool' 'DefaultAppPool' failed range validation for property 'PeriodicRestartMemory'. The configured value 'VirtualMemorySize' is outside of the range '0' to '4194303'. The value will default to '512000'. When you experience Problem 3 or Problem 4, the following error message is logged in the system event log: Event Type: Warning
Event Source: W3SVC Event Category: None Event ID: 1041 Description: The 'Application Pool' 'DefaultAppPool' failed range validation for property 'PeriodicRestartPrivateMemory'. The configured value 'VirtualMemorySize' is outside of the range '0' to '3145728'. The value will default to '0'. RESOLUTIONService pack informationTo 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:889100
(http://support.microsoft.com/kb/889100/
)
How to obtain the latest service pack for Windows Server 2003 Hotfix informationPrerequisitesTo apply this hotfix, you must have Windows Server 2003 SP1 installed on the computer.Restart requirementYou must restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.File informationThe 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 versionsCollapse this table
Windows Server 2003, Itanium-based versionsCollapse this table
STATUSMicrosoft 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. MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe
Microsoft software updates
APPLIES TO
| Article Translations
|
Back to the top
