Microsoft KB Archive/816485

= Server Stops Responding When Win32_NetworkLoginProfile Performs Enumeration =

Article ID: 816485

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Windows 2000 Service Pack 3
 * Microsoft Windows 2000 Service Pack 2
 * Microsoft Windows 2000 Service Pack 1
 * Microsoft Windows 2000 Standard Edition

-



SYMPTOMS
When the Win32_NetworkLoginProfile class in Windows Management Instrumentation (WMI) performs an enumeration process, and this causes the Ntuser.dat registry hives of all cached profiles to be loaded, the server where the enumeration process is running may stop responding (hang).



CAUSE
This issue occurs if the hive load procedure is performed in the context of the WMI service (Local System). Local System has the correct permissions to read and load the registry hives in cached profiles. The hotfix described in this article makes sure that the hive load is performed under the context of the user. However, no security principal (including Local System) has implicit permissions to unload registry hives. Additionally, the Restore permissions must be specified during the connection process to make sure that the cached profile hives are unloaded, as specified in the following sample code: Set objWbemServices = GetObject(&quot;winmgmts:{impersonationLevel=impersonate, (Restore)}!root/cimv2&quot;) Only users with administrative permissions are permitted to load and examine cached profile hives. Additionally, if the Restore permission (also known as a moniker) is not specified when you connect to the Common Information Management (CIM) object model, the hives are not unloaded and they continue to consume registry quota space (paged pool memory) indefinitely.



Service Pack Information
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix 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 20-Mar-2003 13:03   1.50.1085.103  1,089,637   Cimwin32.dll



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.

Additional query words: crash freeze quit

Keywords: kbhotfixserver kbqfe kbsysadmin kbwin2ksp4fix kbwinnt400presp7fix kbwin2000presp4fix kbfix kbbug KB816485

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.