Thoughts from the EPS Windows Server Performance Team
Useful Microsoft Blogs
Some of the most difficult issues we face here on the Performance Team are WMI related issues. WMI is very pervasive, and when it breaks, you can experience a myriad of symptoms that are often very difficult to troubleshoot and fix. Here are a few examples of the symptoms that can occur, and that are addressed by the hotfixes listed at the bottom of this post:
More granular symptoms:
And here are the hotfixes that we recommend if you are experiencing WMI problems in Windows:
Hotfix list for Windows 7 and Windows Server 2008 R2
2831347 Roaming user profiles are corrupted when a monitoring program executes a WMI query on a Windows Server 2008 R2 SP1-based RDS serverhttp://support.microsoft.com/?id=2831347
2705357 The WMI process stops sending events to WMI clients from a Windows 7-based or Windows Server 2008 R2-based serverhttp://support.microsoft.com/kb/2705357
2692929 "0x80041001" error when the Win32_Environment WMI class is queried by multiple requestors in Windows 7 or in Windows Server 2008 R2http://support.microsoft.com/kb/2692929
2617858 Unexpectedly slow startup or logon process in Windows Server 2008 R2 or in Windows 7http://support.microsoft.com/kb/2617858
2465990 "0x80041002 (WBEM_E_NOT_FOUND)" error occurs when you try to open a WMI namespace on a computer that is running Windows 7 or Windows Server 2008 R2http://support.microsoft.com/kb/2465990
2492536 Msinfo32.exe takes a long time to display or export system information on a computer that has many MSI-X-supported devices and that is running Windows 7 or Windows Server 2008 R2http://support.microsoft.com/kb/2492536
982293 The Svchost.exe process that has the WMI service crashes in Windows Server 2008 R2 or in Windows 7http://support.microsoft.com/kb/982293
974930 An application or service that queries information about a failover cluster by using the WMI provider may experience low performance or a time-out exceptionhttp://support.microsoft.com/kb/974930
Hotfix list for Windows Vista and Windows Server 2008
2639845 The memory usage of an application or a service keeps increasing when it loads and unloads the Netshell.dll module frequently in Windows Vista or in Windows Server 2008http://support.microsoft.com/kb/2639845
2464876 The WMI repository is corrupted on a computer that is running Windows Server 2008 or Windows Vistahttp://support.microsoft.com/kb/2464876 973243 The default gateway is missing on a computer that is running Windows Server 2008 or Windows Vista after the computer restarts if the default gateway is set by using the Netsh commandhttp://support.microsoft.com/kb/973243
Hotfix list for Windows Server 2003 SP2
2257980 "0x80041002 (WBEM_E_NOT_FOUND)" error code occurs when you try to open a WMI namespace on a computer that is running Windows Server 2003 SP2http://support.microsoft.com/kb/2257980 For all supported x86-based versions of Windows Server 2003
Hotfix list for Windows XP
933062 A hotfix is available that improves the stability of the Windows Management Instrumentation repository in Windows XPhttp://support.microsoft.com/kb/933062
Til next time,
Congratulations great post
I had KB2492536 missing in my list (social.technet.microsoft.com/.../list-of-wmi-related-hotfixes-for-windows-7-and-windows-server-2008-r2.aspx).
Wait, how is support.microsoft.com/.../2617858 different from support.microsoft.com/.../2505348 ? Don't they both fix wmi verification of large repositories?
Isn't 2465990 superseded by 2617858? They replace the same files.
Justin: yes it does, but 2465990 was left on the list.
Hotfixes supersede each other only if the replaced files are from the same servicing branch. Please see blogs.technet.com/.../how-does-windows-choose-which-version-of-a-file-to-install.aspx for some information on that process.
I applied the Hotfix list for Windows Server 2003 SP2 and reboot the server.
Then I run wmidiag tool. The error of 0x80041002 still occur.
I am having problems with "Repository growing large related to OBJECTS.DATA file" and at some point when the repository file get very bloated on our RDS servers i need to ResetRepository to get things up and running for a couple of months.
No i need to install all the hotfixes or is there just one that will fix my issue ?
I feel it is helpful to note that if you work in a domain environment where multiple users log in to a single computer your repository could grow again even after it has been rebuilt. We were finding that it would take upwards of an hour to get to the login screen. We just found this out today as we are currently dealing with an issue with the WMI repository bloating. There is a group policy we need to change to keep each user from registering the same software in the repository which can lead to corruption and bloat.