A computer that is running Windows Server 2003 or Systems Management Server 2003 may stop responding (895477)

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:
Can't create instance of CSecuredSource for SMS_Site SQL Error: [IM005][0][Microsoft][ODBC Driver Manager] Driver's SQLAllocHandle on SQL_HANDLE_DBC failed
SQL Error: [01000][768][Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (SECDoClientHandshake()). [08001][18][Microsoft][ODBC SQL Server Driver][Shared Memory]SSL Security error -- [01000][768][Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (SECDoClientHandshake()).

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, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

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

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:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/__providerhostquotaconfiguration.asp