When you try to remove a collection or other resource while an event query runs against a Windows Management Instrumentation (WMI) class, you experience both of the following symptoms:
- The SMS Administrator Console stops responding (hangs).
- The Windows Management Instrumentation service stops responding.
This problem may occur when Microsoft Systems Management Server(SMS) 2.0 Service Pack 5 (SP5) or the original released version of SMS 2003 is on a computer that is running Microsoft Windows 2000 Service Pack 3 (SP3) or Windows 2000 Service Pack 4 (SP4).
In Windows 2000 SP3 and in Windows 2000 SP4, a polling notification query against the SMS Extension Provider (Extnprov.dll) may cause a deadlock in the WMI subsystem. This problem occurs because of the way that the SMS Extension Provider synchronizes the WMI
DeleteClass method. While this problem does not occur during typical operations, you may experience this problem when you create custom procedures to directly monitor certain WMI events.
Systems Management Server 2003
Service pack information
To resolve this problem, obtain the latest service pack for Systems Management Server 2003. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
885643Â
(http://kbalertz.com/Feedback.aspx?kbNumber=885643/
)
How to obtain the latest Systems Management Server 2003 service pack
Hotfix information
Restart requirement
You do not have to restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The German 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.
Date Time Version Size File name
---------------------------------------------------------
25-Dec-2003 08:35 2.50.2726.119 376,832 Extnprov.dll
Systems Management 2.0
Hotfix information
A supported hotfix is 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 software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
You must be running Systems Management Server 2.0 SP5 to install this hotfix.
For additional information about how to obtain SP5 for SMS 2.0, click the following article number to view the article in the Microsoft Knowledge Base:
288239Â
(http://kbalertz.com/Feedback.aspx?kbNumber=288239/
)
How to obtain the latest Systems Management Server 2.0 service pack
Restart requirement
You do not have to restart your 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) 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.
Date Time Version Size File name
---------------------------------------------------------
31-Jul-2003 18:32 2.0.1493.5149 290,784 Extnprov.dll
The German version of this hotfix has the file attributes (or later) 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.
Date Time Version Size File name
----------------------------------------------------------
31-Jul-2003 12:33 2.0.1493.5149 290,784 Extnprov.dll
Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.Install this hotfix on an SMS Primary site server. However, if the SMS Provider is remote from the SMS Primary site server, you must also install this hotfix on the server where the SMS Provider is located.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The SMS Extension Provider synchronizes all incoming traffic with a critical section.
Consider the following sample scenario:
You activate a query with a 30-second interval to poll the SMS Extension Provider. This requires access to the critical section. While this polling query runs, if a call is made to remove (that is, delete) an SMS instance, such as a collection, the call is routed to ExtnProv.dll and through the critical section. This call results in an attempt to delete a class in the repository. As a result, the WMI core tries to fire an
__InstanceDeletionEvent event for the static class that was removed. However, instead, it triggers the polling query in the WMI Event subsystem.
The WMI Event subsystem tries to re-enter the critical section. This behavior results in a deadlock situation and results in the symptoms that are described in the "Symptoms" section of this article.
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684Â
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates