HKEY_LOCAL_MACHINESYSTEMCurrentControlSetcontrolSession ManagerMemory Management
5. Ensure you have the most current hotfix updates for
6. HTTP.sys is designed to stop servicing requests if the system comes within 20 MB of the non-paged pool limitation. As per KB 934878 , you can set the EnableAggressiveMemoryUsage registry key to allow the system to get closer to the Non-Paged Pool limit before HTTP.sys stops servicing requests:
7. Ensure settings are in place to capture a complete memory dump if necessary as per the following KB article:
972110 How to generate a kernel dump file or a complete memory dump file in Windows Server 200...
8. Reboot the system
When Microsoft is engaged for troubleshooting these issues, we often find that the highest consumers of Non-Paged Pool are Exchange / EXIFS related pool tags (AuxL or Flst). This is typical of a heavily loaded Exchange server. When you see this it is a good indicator that there are more users than the server can handle. You should consider the following:
- Bring another Exchange server online and redistribute the user load
- Move to a Server 2008 64bit solution for your Exchange server
- If there is plenty of paged pool available, you can move AuxL and Flst to paged pool as was the default behavior in SP1.
Helpful Articles / References
934878 Users receive a "The page cannot be displayed" error message, and "Connections_refused" entries are logged in the Httperr.log file on a server that is running Windows Server 2003, Exchange 2003, and IIS 6.0
912376 How to monitor and troubleshoot the use of paged pool memory in Exchange Server 2003 or in Exchange 2000 Server
823440 Use of the /3GB switch in Exchange Server 2003 on a Windows Server 2003-based system
810371 Using the /Userva switch on Windows Server 2003-based computers that are running Exchange Server
AskPerf Blog - Memory Management - Demystifying /3GB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.