WMI does not clear event registrations when the corresponding sink becomes invalid in Windows Server 2003

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 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.

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.

Service pack information

To 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:

Software update information

This update has been superseded by update 931320. For more information about update 931320, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft 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.

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: