Article ID: 895477
Article Last Modified on 7/24/2007
APPLIES TO
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Systems Management Server 2003
SYMPTOMS
You may experience one or more of the following symptoms on a computer that is running Microsoft Windows Server 2003 or Microsoft Systems Management Server (SMS) 2003:
The following event is logged in the Application event log:
Source Srv Type Error Description The server was unable to allocate from the system nonpaged pool because the pool was empty. Details Comments and links for event id 2019 from source Srv
- Applications perform slowly on the computer.
- The computer stops responding. Additionally, the computer does not respond to a ping command and must be restarted to recover.
- The SMS Administrator Console stops responding for 5 to 10 minutes on SMS 2003 primary site servers. Additionally, error messages that are similar to the following are logged in the Smsprov.log file:
CAUSE
These issues may occur because a Microsoft Windows Management Instrumentation (WMI) provider or a third-party WMI provider exceeds values that are set for the MemoryPerHost or HandlesPerHost properties. These values are defined in the __ProviderHostQuotaConfiguration class of the root namespace.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest Windows Server 2003 service pack. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
No prerequisites are required.
Restart requirement
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfix.
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 tool in Control Panel.
Windows Server 2003, Itanium-based versions
Date Time Version Size File name -------------------------------------------------------------- 10-Mar-2005 15:52 5.2.3790.286 1,725,440 Wbemcore.dll IA-64
Windows Server 2003, x86-based versions
Date Time Version Size File name -------------------------------------------------------------- 11-Mar-2005 07:54 5.2.3790.286 468,480 Wbemcore.dll
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section. This bug was corrected in Windows Server 2003 Service Pack 1.
MORE INFORMATION
If you increase the values for the MemoryPerHost property or for the HandlesPerHost property, this problem may occur less frequently.
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
177415 How to use Memory Pool Monitor (Poolmon.exe) to troubleshoot kernel mode memory leaks
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information about the __ProviderHostQuotaConfiguration class, visit the following Microsoft Developer Network (MSDN) Web site:
Keywords: kberrmsg kbbug kbfix kbwinserv2003presp1fix kbpubtypekc kbhotfixserver kbqfe KB895477