Windows Management Instrumentation (WMI) Team Blog

Welcome to WMI Team Blog

Enough has been written about WMI since its first release as an out of band package for Windows NT 4.0 SP4 and as part of the platform for every release of Windows since. WMI has been and will be a critical core Windows Platform Infrastructure piece to aid manageability of systems and applications.

A critical missing form of communication for ad-hoc musings from the core product development team that brings you WMI release after release has always been missing. You have heard our collective input in the form of MSDN documentation put out by our documentation folks. Additionally we have fielded questions from time to time on existing issues you have faced with consuming WMI or building WMI Providers via our newsgroups. It is time that we added bloging to the arsenal of communication we have with outside world.

On this blog you can expect to find interesting tidbits that we encounter in our daily life in designing and engineering this product for the next release of WMI. It isn’t always easy to explain on how we designed a feature in the way you see in its finished form. The lengthy discussions we had, trials and tribulations we went through in shaping the feature is lost in the process.

Of course there are going to be many Intellectual Property type of thingys and hence we will obviously refrain from discussing detailed algorithms used, etc, but you can surely find other musings on this blog in the months to come interesting enough for you to come back. This will also hopefully get you good insight in the way we think and build WMI features.

We don’t promise to reply to all your comments, but we are surely watching and reading most of them.

Published Thursday, September 29, 2005 11:47 PM by rajeshmi

Comments

 

hermillion said:

Hi Team

I think WMI is a great tool but we've been having major problem monitoring IIS and SQL2005 with it. We offer remote monitoring and management of client's IT infrastructure and we use WMI and SNMP to monitor the health of their system services. It works great with the exception of ISS and sql monitoring which keep failling. We checked the wmi repository cimv2 and we notice when wmi monitoring of these services fail, there is no instance of them in the wmi repository. We have to force a wmi resynch and get the iis and sql to register themselves again but sooner or later they fail with most clients. This happened on so many clients iis and sql servers, we're wondering if its a bug. Can you provide any pointers on this problem since its really bug-ing us, excuse the pun. thanks

Hermon

October 18, 2006 9:39 PM
 

ramonEEZA said:

I have a BIG problem with WMI.

It found a DUPLICATE KeyID in a Class that doesn't admit it.

Every TEST goes OK but the error continue and I can't Delete bad instances. (GetObject Returns ERROR enumerating instances of that clase beacouse KeyID is duplicate.

Is there a solution???

The Class with bad instances is:

Exchange_MessageTrackingEntry

When I browse for instances I obtain an error in GetObject:

------------

El objeto solicitado posee un identificador no único y no puede recuperarse.

Dispositivo: Win32

Nº de Id.: c007219d

--------

If I change KeyID as not key... no error but no instances... so I can't delete bad data.

When I restore KeyID as a unique Key... Error goes again.

April 20, 2007 7:39 AM
 

fallenidol said:

Hi, I have a problem using WMI on Windows Server 2003. I have code which i developed on Win XP which uses the root\directory\ldap namespace....however this namespace is not available on my clean install of Windows Server 2003. It just doesnt seem to be there. Are you able to help? Is this namespace available in w2k3 server and how do i enable it? Cheers, Paul.

May 10, 2007 5:06 AM
 

JustLikeThat said:

I am attmpting to install SMS 2003 SP2 on Windows Server 2003 SP2.  I just did a FRESH install of Windows Server 2003, loaded SP2 for Windows Server 2003.  After running critical updates, I reboot and then ran the WMIDiag.vbs, and it returned that WMI is Operating Properly.

I than loaded SMS SP2, let it sit over night, checked Status and logs and all seemed to be working properly.

I than ran the WMIDiag again.  It reported numerous probelms with Security issues in the WMI Control, stating that the Defaults have changed and it may hinder WMI from functioning normally.

Besides those, the first warnings I recieved reference directly to SMS and CCM.  Here is the part of the report I am concerned with:

In a fresh install is this normal reaction?  Is WMI having problems?  What would cause this on a totally fresh installation?  Thank you for having a blogging section for WMI, I appreciate any assistance that I may obtain.

Thanks,

Skye

-------------------------------------------------------------------------------------------------------------------------

29801 09:24:55 (2) !! WARNING: WMI provider DCOM registrations missing for the following provider(s): ..................................... 2 WARNING(S)!

29802 09:24:55 (0) ** - ROOT/CIMV2/SMS, SMS_CIMV2 ({********-E1EC-11D2-846E-************}) (i.e. WMI Class 'SMS_Processor')

29803 09:24:55 (0) **   Provider DLL: 'C:\WINDOWS\SYSTEM32\CCM\SMSPROC.DLL'

29804 09:24:55 (0) ** - ROOT/CIMV2/SMS, SMS_CIMLD ({********-2801-11D3-88DA-************}) (i.e. WMI Class 'SMS_LogicalDisk')

29805 09:24:55 (0) **   Provider DLL: 'C:\WINDOWS\SYSTEM32\CCM\SMSCCMLD.DLL'

29806 09:24:55 (0) ** => This is an issue because there are still some WMI classes referencing this list of providers

29807 09:24:55 (0) **    while the DCOM registration is wrong or missing. This can be due to:

29808 09:24:55 (0) **    - a de-installation of the software.

29809 09:24:55 (0) **    - a deletion of some registry key data.

29810 09:24:55 (0) **    - a registry corruption.

29811 09:24:55 (0) ** => You can correct the DCOM configuration by:

29812 09:24:55 (0) **    - Executing the 'REGSVR32.EXE <Provider.DLL>' command.

29813 09:24:55 (0) **    Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.

29814 09:24:55 (0) **          (This list can be built on a similar and working WMI Windows installation)

29815 09:24:55 (0) **          The following command line must be used:

29816 09:24:55 (0) **          i.e. 'WMIDiag CorrelateClassAndProvider'

29817 09:24:55 (2) !! WARNING: Re-registering with REGSVR32.EXE all DLL from 'C:\WINDOWS\SYSTEM32\WBEM\'

29818 09:24:55 (0) **          may not solve the problem as the DLL supporting the WMI class(es)

29819 09:24:55 (0) **          can be located in a different folder.

29820 09:24:55 (0) **          You must refer to the class name to determine the software delivering the related DLL.

29821 09:24:55 (0) ** => If the software has been de-installed intentionally, then this information must be

29822 09:24:55 (0) **    removed from the WMI repository. You can use the 'WMIC.EXE' command to remove

29823 09:24:55 (0) **    the provider registration data.

29824 09:24:55 (0) **    i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\CIMV2\SMS path __Win32Provider Where Name='SMS_CIMP' DELETE'

29825 09:24:55 (0) ** => If the namespace was ENTIRELY dedicated to the intentionally de-installed software,

29826 09:24:55 (0) **    the namespace and ALL its content can be ENTIRELY deleted.

29827 09:24:55 (0) **    i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\CIMV2 path __NAMESPACE Where Name='SMS' DELETE'

29828 09:24:55 (0) **    - Re-installing the software.

29829 09:24:55 (0) **

-------------------------------------------------------------------------------------------------------------------------

May 10, 2007 11:17 AM
 

rharmeson said:

My Windows 2003 server is missing HKLM\Software\Microsoft\Wbem\Transports

Decoupled\Client entries?? DFSR has stopped working since WMI is missing namespaces such as \root\Microsoftdfs Any assistance you would great.

August 22, 2007 2:43 AM
 

augerp said:

I have a problem, The WMI repository get corrupt on new build computers, I noticed that the corruption occur when the GPO gets re-applied completely, that is every 16 hours in our environment. Once this happen , I can't loggon the machine, not true it will eventually go but it will take many minutes. I can remotely connect to the C$ drive and delete the repository then restart the machine and I m able to bring it back to life. I need to find the root cause of this I have wasted a lot of time on this. It's important to say that the computers are build from a sysprep images and it seems to happen on one type of laptop only not on other models we have in the company. I just don't know how to troubleshoot this one and I'm running out of Ideas and time.

Thanks for any help

Patrice Auger

December 12, 2007 6:31 PM
 

SyncMaster said:

I try to remove my High Performance WMI Counter and I don't know how to do it programaticly.

Manually it's easy :

1.  WMIC.EXE /NAMESPACE:\\ROOT\CIMV2 path __Win32Provider Where Name='PerfRouter_Client' DELETE

2. Run WMI CIM Studio and find class Win32_PerfRawData_Router_Client then delete it from the tree

Could you point me to MSDN where thre is info about it.

Thanks

January 11, 2008 11:14 AM
 

jeanicobb said:

I am running Vosta Ulitmate 32 and my WMi has errors.  This is the part where the errors are let me know if you need more - I am desparate...

WMI MONIKER CONNECTIONS: ............................................................................................ OK.

25252 15:19:19 (0) ** WMI CONNECTIONS: .................................................................................................... OK.

25253 15:19:19 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 8 ERROR(S)!

25254 15:19:19 (0) ** - Root/CIMv2, Win32_Process.Handle=1384, 0x80004002 - No such interface supported.

25255 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'

25256 15:19:19 (0) ** - Root/CIMv2, Win32_Process.Handle=1384, 0x80004002 - No such interface supported.

25257 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'

25258 15:19:19 (0) ** - Root/CIMV2, Win32_Service='WSCSVC', 0x80004002 - No such interface supported.

25259 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'

25260 15:19:19 (0) ** - Root/CIMv2, Win32_Process.Handle=1384, 0x80004002 - No such interface supported.

25261 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'

25262 15:19:19 (0) ** - Root/CIMv2, Win32_Process.Handle=1384, 0x80004002 - No such interface supported.

25263 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'

25264 15:19:19 (0) ** - Root/CIMv2, Win32_Process.Handle=2336, 0x80004002 - No such interface supported.

25265 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'

25266 15:19:19 (0) ** - Root/CIMv2, Win32_Process.Handle=2336, 0x80004002 - No such interface supported.

25267 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'

25268 15:19:19 (0) ** - Root/CIMv2, Win32_Process.Handle=2336, 0x80004002 - No such interface supported.

25269 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'

25270 15:19:19 (0) **

25271 15:19:19 (0) ** WMI MOF representations: ............................................................................................ OK.

25272 15:19:19 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.

25273 15:19:19 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 24 ERROR(S)!

25274 15:19:19 (0) ** - ROOT/CIMV2, InstancesOfAsync, 'CIM_USBDevice', 0x80004002 - .

25275 15:19:19 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'

25276 15:19:19 (0) ** - ROOT/CIMV2, InstancesOfAsync, 'CIM_USBHub', 0x80004002 - .

25277 15:19:19 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'

25278 15:19:19 (0) ** - ROOT/CIMV2, InstancesOfAsync, 'CIM_StorageVolume', 0x80004002 - .

25279 15:19:19 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'

25280 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_ComputerSystem', 0x80004002 - No such interface supported.

25281 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'

25282 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_Service', 0x80004002 - No such interface supported.

25283 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'

25284 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_Process', 0x80004002 - No such interface supported.

25285 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'

25286 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_OperatingSystem', 0x80004002 - No such interface supported.

25287 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'

25288 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_BIOS', 0x80004002 - No such interface supported.

25289 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\CIMWIN32.MOF / C:\WINDOWS\SYSTEM32\WBEM\SECRCW32.MOF'

25290 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Cache', 0x80004002 - No such interface supported.

25291 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'

25292 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Memory', 0x80004002 - No such interface supported.

25293 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'

25294 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Objects', 0x80004002 - No such interface supported.

25295 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'

25296 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_PagingFile', 0x80004002 - No such interface supported.

25297 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'

25298 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Processor', 0x80004002 - No such interface supported.

25299 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'

25300 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_System', 0x80004002 - No such interface supported.

25301 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'

25302 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfProc_Process', 0x80004002 - No such interface supported.

25303 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'

25304 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfProc_Thread', 0x80004002 - No such interface supported.

25305 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'

25306 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_ICMP', 0x80004002 - No such interface supported.

25307 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'

25308 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_ICMPv6', 0x80004002 - No such interface supported.

25309 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'

25310 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_IPv4', 0x80004002 - No such interface supported.

25311 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'

25312 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_IPv6', 0x80004002 - No such interface supported.

25313 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'

25314 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_TCPv4', 0x80004002 - No such interface supported.

25315 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'

25316 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_TCPv6', 0x80004002 - No such interface supported.

25317 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'

25318 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_UDPv4', 0x80004002 - No such interface supported.

25319 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'

25320 15:19:19 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_UDPv6', 0x80004002 - No such interface supported.

25321 15:19:19 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'

25322 15:19:19 (0) **

25323 15:19:19 (1) !! ERROR: WMI EXECQUERY operation errors reported: ..................................................................... 17 ERROR(S)!

25324 15:19:19 (0) ** - Root/CIMV2, Select * From Win32_LogicalDisk WHERE FreeSpace > 10000000 AND DriveType = 3, 0x80004002 - No such interface supported.

25325 15:19:19 (0) ** - Root/CIMV2, Select DriveType From Win32_LogicalDisk WHERE Name='C:', 0x80004002 - No such interface supported.

25326 15:19:19 (0) ** - Root/CIMV2, Select * From Win32_Service, 0x80004002 - No such interface supported.

25327 15:19:19 (0) ** - Root/CIMV2, Select * From Win32_PageFileUsage, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.

25328 15:19:19 (0) ** - Root/CIMV2, Select * From Win32_BIOS WHERE Version IS NOT NULL, 0x80004002 - No such interface supported.

25329 15:19:19 (0) ** - Root/CIMV2, Select * From Win32_NetworkAdapter WHERE AdapterType IS NOT NULL AND AdapterType != "Wide Area Network (WAN)" AND Description != "Packet Scheduler Miniport", 0x80004002 - No such interface supported.

25330 15:19:19 (0) ** - Root/CIMV2, Select * From Win32_Processor WHERE Name IS NOT NULL, 0x80004002 - No such interface supported.

25331 15:19:19 (0) ** - Root/CIMV2, Select * From Win32_DiskDrive, 0x80004002 - No such interface supported.

25332 15:19:19 (0) ** - Root/CIMV2, Select * From Win32_ComputerSystem, 0x80004002 - No such interface supported.

25333 15:19:19 (0) ** - Root/CIMV2, Select * From Win32_DiskPartition, 0x80004002 - No such interface supported.

25334 15:19:19 (0) ** - Root/CIMV2, Select * From Win32_LogicalDisk WHERE Description != "Network Connection", 0x80004002 - No such interface supported.

25335 15:19:19 (0) ** - Root/CIMV2, Select * From Win32_VideoController, 0x80004002 - No such interface supported.

25336 15:19:19 (0) ** - Root/CIMV2, Select * From Win32_USBController, 0x80004002 - No such interface supported.

25337 15:19:19 (0) ** - Root/CIMV2, Select * From Win32_DesktopMonitor, 0x80004002 - No such interface supported.

25338 15:19:19 (0) ** - Root/CIMV2, Select * From Win32_PointingDevice WHERE Status = "OK", 0x80004002 - No such interface supported.

25339 15:19:19 (0) ** - Root/CIMV2, Select * From Win32_Keyboard, 0x80004002 - No such interface supported.

25340 15:19:19 (0) ** - Root/CIMV2, Select * From Win32_SystemDriver WHERE StartMode != "Disabled", 0x80004002 - No such interface supported.

25341 15:19:19 (0) **

25342 15:19:19 (0) ** WMI GET VALUE operations: ........................................................................................... OK.

25343 15:19:19 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.

25344 15:19:19 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.

25345 15:19:19 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.

25346 15:19:19 (0) ** WMI static instances retrieved: ..................................................................................... 1604.

25347 15:19:19 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.

25348 15:19:19 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.

25349 15:19:19 (0) ** ----------------------------------------------------------------------------------------------------------------------------------

25350 15:19:19 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):

25351 15:19:19 (0) **   DCOM: ............................................................................................................. ERROR!

25352 15:19:19 (0) **   WINMGMT: .......................................................................................................... ERROR!

25353 15:19:19 (0) **   WMIADAPTER: ....................................................................................................... ERROR!

25354 15:19:19 (0) **

25355 15:19:19 (0) ** # of additional Event Log events AFTER WMIDiag execution:

25356 15:19:19 (0) **   DCOM: ............................................................................................................. ERROR!

25357 15:19:19 (0) **   WINMGMT: .......................................................................................................... ERROR!

25358 15:19:19 (0) **   WMIADAPTER: ....................................................................................................... ERROR!

25359 15:19:19 (0) **

25360 15:19:19 (0) ** 48 error(s) 0x80004002 - (WBEM_UNKNOWN) This error code is external to WMI.

25361 15:19:19 (0) ** => This error is not a WMI error. It is a DCOM error due to the following reasons:

25362 15:19:19 (0) **    - An application has changed the COM/DCOM settings of OLE32.DLL and/or OLEAUT32.DLL.

25363 15:19:19 (0) **    - The registry settings of COM/DCOM has been damage or wrongly modified.

25364 15:19:19 (0) ** => To correct this situation, you must re-register the original COM/DCOM DLLs with REGSVR32.EXE

25365 15:19:19 (0) **    i.e. 'REGSVR32.EXE OLE32.DLL'

25366 15:19:19 (0) **    i.e. 'REGSVR32.EXE OLEAUT32.DLL'

25367 15:19:19 (0) **

25368 15:19:19 (0) **

25369 15:19:19 (0) ** 1 error(s) 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema

25370 15:19:19 (0) ** => This error is typically due to the following major reasons:

25371 15:19:19 (0) **    - The application queried by the WMI provider is not installed, not available or not running

25372 15:19:19 (0) **      at the time of the request was made. This error can also be generated because

25373 15:19:19 (0) **      the application supporting the providers has been uninstalled.

25374 15:19:19 (0) **    - Some WMI providers (i.e. RSOP Planning Mode, Exchange 2003) are implemented as a WMI service.

25375 15:19:19 (0) **      Make sure the required services are successfully started.

25376 15:19:19 (0) **    - The WMI provider binary files are not accessible (i.e. access denied ACL).

25377 15:19:19 (0) **    - A WMI provider registration problem at the CIM level (MOFCOMP.EXE) or at the COM level (REGSVR32.EXE).

25378 15:19:19 (0) **      You must re-register the WMI provider by recompiling its associated MOF file with MOFCOMP.EXE

25379 15:19:19 (0) **    Note: - If the WMI provider DLL CIM and COM registrations are correct, this error can

25380 15:19:19 (0) **            be returned because the provider has a dependency on another DLL that cannot be

25381 15:19:19 (0) **            loaded (missing or bad DLL)

25382 15:19:19 (0) **          - Dependencies can be found with the DEPENDS.EXE tool coming with the

25383 15:19:19 (0) **            Windows XP and Windows 2003 Support Tools. The command line is as follows:

25384 15:19:19 (0) **            i.e. DEPENDS.EXE <PATH><Provider.DLL>

25385 15:19:19 (0) ** => When a WMI provider fails to load, it is possible to trace the provider load process by

25386 15:19:19 (0) **    submitting, via WBEMTEST and asynchronously, the following WMI event query:

25387 15:19:19 (0) **    'Select * From MSFT_WmiSelfEvent'

25388 15:19:19 (0) **    Then you can trace the following WMI events:

25389 15:19:19 (0) **    - Msft_WmiProvider_ComServerLoadOperationEvent

25390 15:19:19 (0) **    - Msft_WmiProvider_InitializationOperationEvent

25391 15:19:19 (0) **    - Msft_WmiProvider_LoadOperationEvent

25392 15:19:19 (0) **    and depending on the WMI operation executed, you can trace the following WMI events:

25393 15:19:19 (0) **    i.e. for an enumeration:

25394 15:19:19 (0) **    - Msft_WmiProvider_CreateInstanceEnumAsyncEvent_Pre and Msft_WmiProvider_CreateInstanceEnumAsyncEvent_Post

25395 15:19:19 (0) **    i.e. for a put operation:

25396 15:19:19 (0) **    - Msft_WmiProvider_PutInstanceAsyncEvent_Pre and Msft_WmiProvider_PutInstanceAsyncEvent_Post

25397 15:19:19 (0) **

February 3, 2008 3:33 PM
 

jwiner said:

Evidently, this forum does not receive much attention from the WMI team.  That is unfortunate.  WMI offers a lot of unrealized promise within the development community.  Scores of development teams use less adept and robust systems for logging, monitoring, etc.  But there is no one actively leading the charge to exhibit this technology, so this is not unexpected.  

I recently began utilizing WMI for monitoring our internal applications.  A co-worker in my office suggested it and provided some initial insight into its purpose and possible uses.  There is a small learning curve, but more importantly, there are unforeseen issues that arise depending on the OS, the application or the task attempting to be accomplished.  Now that I have overcome the obstacles to using WMI, I am a strong proponent of it, but the road to becoming proficient at using WMI and understanding its nuances is too big a task (I believe) for the development community at large to embrace it.

This blog and other forums need to actively post and communicate issues, fixes, strategies, etc. in working with WMI.  My countless hours searching the web for factual information has been daunting and frustrating.  This portal could have made the task much easier.

To outline some of the issues I've had to date:

- improperly installed/registered windows components with the WMI repository

- incomplete custom event class registration within the WMI repository

- partial performance counter registration within the WMI repository

- WMI CIM Studio and wbemtest reporting different information about classes than Perfmon

- lacking complete and accurate online tutorials/information around WMI Tools, wbemtest, WMI Diagnosis Utility and winmgmt

- latency in displaying newly registered classes within the WMI repository within the WMI CIM Studio tools

- difficulties in assessing the minimum permissions for reading values from WMI (performance counters, queues, etc.)

I would love to see an increased presence on the web from the WMI team.  I hope my criticism is taken constructively and not as the rantings of a slighted developer.

--Regards

October 23, 2008 3:48 PM
Anonymous comments are disabled

This Blog

Syndication

Tags

No tags have been created or used yet.

© 2008 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Microsoft
Page view tracker