Article ID: 931320
Article Last Modified on 11/15/2007
APPLIES TO
- Microsoft Windows Management Instrumentation 1.5, when used with:
- 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, Web Edition
SYMPTOMS
Consider the following scenario:
- An event consumer uses Windows Management Instrumentation (WMI). WMI provides asynchronous delivery of events.
- The event consumer registers an IWbemObjectSink interface with WMI. The event consumer does this to receive DCOM callbacks that contain these events.
- The event consumer uses the same IWbemObjectSink interface for many such event registrations.
In this scenario, the consumer's DCOM connection may be lost because of network issues or because the event consumer stops responding (hangs). If the consumer's DCOM connection is lost, each event registration remains active inside WMI. Therefore, WMI consumes resources for each registration that is associated to the IWbemObjectSink interface. WMI consumes these resources until a failed delivery attempt occurs for each registration.
CAUSE
This problem occurs if an event consumer loses connectivity with WMI. This problem also occurs if a WMI client loses DCOM communication with WMI because of network problems.
RESOLUTION
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
The computer must be running Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2) to install this hotfix.
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.
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Wbemcore.dll | 5.2.3790.2902 | 510,464 | 21-Mar-2007 | 05:27 | x86 | SP1 | SP1QFE |
| Wbemcore.dll | 5.2.3790.4043 | 510,464 | 21-Mar-2007 | 05:55 | x86 | SP2 | SP2QFE |
| Updspapi.dll | 6.3.4.1 | 379,184 | 01-Mar-2007 | 06:10 | x86 | None | Not Applicable |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information about the standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Keywords: kbqfe kbhotfixserver kbfix kbbug kbwinserv2003presp2fix kbexpertiseadvanced KB931320
