none
DCOM Error Event ID 10010

    Question

  • Hi, I am getting an error on my 2012R2 server. It repeats each minute for the last few weeks.

    The server {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} did not register with DCOM within the required timeout.

    AppId for {1F87137D-0E7C-44D5-8C73-4EFFB68962F2} is Microsoft WMI Provider Subsystem Secured Host.


    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
      <EventID Qualifiers="0">10010</EventID>
      <Version>0</Version>
      <Level>2</Level>
      <Task>0</Task>
      <Opcode>0</Opcode>
      <Keywords>0x8080000000000000</Keywords>
      <TimeCreated SystemTime="2016-02-20T10:31:29.622764800Z" />
      <EventRecordID>80207</EventRecordID>
      <Correlation />
      <Execution ProcessID="824" ThreadID="20040" />
      <Channel>System</Channel>
      <Computer>xxxxxxxxxxxxxxxxx</Computer>
      <Security UserID="S-1-5-20" />
      </System>
    - <EventData>
      <Data Name="param1">{1F87137D-0E7C-44D5-8C73-4EFFB68962F2}</Data>
      </EventData>
      </Event>

    I did the following steps and after restart there was no error, but after few days it appeared again.

    1.      Go to run and type   Start DCOMCNFG,Computer>My Computer> DCOM Config > Microsoft WMI Provider Subsystem Secured Host > properties
    2.      Click the Security tab.
    3.      Select Customize in  Access permissions, click Edit, and then click OK. The Custom access permissions are registered.
    4.      Restart the machine

    Checked permissions in registry HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{1F87137D-0E7C-44d5-8C73-4EFFB68962F2}, but everything is as it should be. Security configuration in DCOM for Microsoft WMI Provider Subsystem Secured Host is also set as it should be. No events before first DCOM error that could show something to happen.



    Saturday, March 5, 2016 3:37 AM

All replies

  • Hi,

    I did the following steps and after restart there was no error, but after few days it appeared again.

    Is there a pattern when the issue re-occurs? Such as timing, running applications, operations performed.

    Here are some causes of this event from others:

    Event ID: 10010 Source: DCOM

    http://www.eventid.net/display-eventid-10010-source-DCOM-eventno-508-phase-1.htm

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    Best Regards,

    Amy


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, March 7, 2016 10:00 AM
    Moderator
  • I can't see any pattern - error reappears after 3-5 days, no scheduled tasks starting or different events at that time when error apears.

    I ran WMIDIAG tool It shows some errors with WMI

    37562 17:04:30 (0) ** WMIDiag v2.2 started on Saturday, 19 March 2016 at 15:36.
    37563 17:04:30 (0) **
    37564 17:04:30 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
    37565 17:04:30 (0) **
    37566 17:04:30 (0) ** This script is not supported under any Microsoft standard support program or service.
    37567 17:04:30 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
    37568 17:04:30 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
    37569 17:04:30 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
    37570 17:04:30 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
    37571 17:04:30 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
    37572 17:04:30 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
    37573 17:04:30 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
    37574 17:04:30 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
    37575 17:04:30 (0) ** of the possibility of such damages.
    37576 17:04:30 (0) **
    37577 17:04:30 (0) **
    37578 17:04:30 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    37579 17:04:30 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
    37580 17:04:30 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    37581 17:04:30 (0) **
    37582 17:04:30 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    37583 17:04:30 (0) ** Windows Server 2012 R2 - No Service Pack - 64-bit (9600) - User 'XXX' on computer 'XXX'.
    37584 17:04:30 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    37585 17:04:30 (0) ** Environment: ........................................................................................................ OK.
    37586 17:04:30 (0) ** There are no missing WMI system files: .............................................................................. OK.
    37587 17:04:30 (0) ** There are no missing WMI repository files: .......................................................................... OK.
    37588 17:04:30 (0) ** WMI repository state: ............................................................................................... N/A.
    37589 17:04:30 (0) ** AFTER running WMIDiag:
    37590 17:04:30 (0) ** The WMI repository has a size of: ................................................................................... 25 MB.
    37591 17:04:30 (0) ** - Disk free space on 'C:': .......................................................................................... 436059 MB.
    37592 17:04:30 (0) **   - INDEX.BTR,                     4726784 bytes,      19/03/2016 4:04:18 PM
    37593 17:04:30 (0) **   - MAPPING1.MAP,                  73844 bytes,        19/03/2016 12:46:18 PM
    37594 17:04:30 (0) **   - MAPPING2.MAP,                  73844 bytes,        19/03/2016 2:26:18 PM
    37595 17:04:30 (0) **   - OBJECTS.DATA,                  21725184 bytes,     19/03/2016 4:04:18 PM
    37596 17:04:30 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    37597 17:04:30 (2) !! WARNING: Windows Firewall: .......................................................................................... DISABLED.
    37598 17:04:30 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    37599 17:04:30 (0) ** DCOM Status: ........................................................................................................ OK.
    37600 17:04:30 (0) ** WMI registry setup: ................................................................................................. OK.
    37601 17:04:30 (0) ** INFO: WMI service has dependents: ................................................................................... 1 SERVICE(S)!
    37602 17:04:30 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
    37603 17:04:30 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
    37604 17:04:30 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
    37605 17:04:30 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
    37606 17:04:30 (0) **          this can prevent the service/application to work as expected.
    37607 17:04:30 (0) **
    37608 17:04:30 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
    37609 17:04:30 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
    37610 17:04:30 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    37611 17:04:30 (0) ** WMI service DCOM setup: ............................................................................................. OK.
    37612 17:04:30 (0) ** WMI components DCOM registrations: .................................................................................. OK.
    37613 17:04:30 (0) ** WMI ProgID registrations: ........................................................................................... OK.
    37614 17:04:30 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
    37615 17:04:30 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
    37616 17:04:30 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
    37617 17:04:30 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
    37618 17:04:30 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    37619 17:04:30 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
    37620 17:04:30 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
    37621 17:04:30 (0) **    i.e. You can start your scripts or WMIC commands from an elevated command
    37622 17:04:30 (0) **         prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
    37623 17:04:30 (0) **         selecting 'Run as Administrator'.
    37624 17:04:30 (0) **    i.e. You can also execute the WMI scripts or WMIC commands as a task
    37625 17:04:30 (0) **         in the Task Scheduler within the right security context.
    37626 17:04:30 (0) **
    37627 17:04:30 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
    37628 17:04:30 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
    37629 17:04:30 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
    37630 17:04:30 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
    37631 17:04:30 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
    37632 17:04:30 (0) **
    37633 17:04:30 (0) ** Overall DCOM security status: ....................................................................................... OK.
    37634 17:04:30 (0) ** Overall WMI security status: ........................................................................................ OK.
    37635 17:04:30 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
    37636 17:04:30 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 1.
    37637 17:04:30 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
    37638 17:04:30 (0) **   'select * from MSFT_SCMEventLogEvent'
    37639 17:04:30 (0) **
    37640 17:04:30 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
    37641 17:04:30 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 4 NAMESPACE(S)!
    37642 17:04:30 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
    37643 17:04:30 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
    37644 17:04:30 (0) ** - ROOT/MICROSOFTIISV2.
    37645 17:04:30 (0) ** - ROOT/SERVICEMODEL.
    37646 17:04:30 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
    37647 17:04:30 (0) **    use an encrypted connection by specifying the PACKET PRIVACY authentication level.
    37648 17:04:30 (0) **    (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
    37649 17:04:30 (0) **    i.e. 'WMIC.EXE /NODE:"XXX" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
    37650 17:04:30 (0) **
    37651 17:04:30 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
    37652 17:04:30 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
    37653 17:04:30 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 8 ERROR(S)!
    37654 17:04:30 (0) ** - Root/CIMv2, Win32_Process.Handle=984, 0x80080005 - Server execution failed.
    37655 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37656 17:04:30 (0) ** - Root/CIMv2, Win32_Process.Handle=8084, 0x80080005 - Server execution failed.
    37657 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37658 17:04:30 (0) ** - Root/CIMv2, Win32_Process.Handle=24176, 0x80080005 - Server execution failed.
    37659 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37660 17:04:30 (0) ** - Root/CIMv2, Win32_Process.Handle=8084, 0x80080005 - Server execution failed.
    37661 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37662 17:04:30 (0) ** - Root/CIMv2, Win32_Process.Handle=984, 0x80080005 - Server execution failed.
    37663 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37664 17:04:30 (0) ** - Root/CIMv2, Win32_Process.Handle=8084, 0x80080005 - Server execution failed.
    37665 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37666 17:04:30 (0) ** - Root/CIMv2, Win32_Process.Handle=8084, 0x80080005 - Server execution failed.
    37667 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37668 17:04:30 (0) ** - Root/CIMv2, Win32_Process.Handle=8084, 0x80080005 - Server execution failed.
    37669 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37670 17:04:30 (0) **
    37671 17:04:30 (0) ** WMI MOF representations: ............................................................................................ OK.
    37672 17:04:30 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
    37673 17:04:30 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 32 ERROR(S)!
    37674 17:04:30 (0) ** - ROOT/CIMV2, InstancesOfAsync, 'CIM_USBDevice', 0x80080005 - .
    37675 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37676 17:04:30 (0) ** - ROOT/CIMV2, InstancesOfAsync, 'CIM_USBHub', 0x80080005 - .
    37677 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37678 17:04:30 (0) ** - ROOT/CIMV2, InstancesOfAsync, 'CIM_StorageVolume', 0x80080005 - .
    37679 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37680 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_IKEProposal', 0x80080005 - .
    37681 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37682 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'MSFT_NetIKEAuthProposal', 0x80080005 - .
    37683 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37684 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'MSFT_NetIKECryptoProposal', 0x80080005 - .
    37685 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37686 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_IPAssignmentSettingData', 0x80080005 - .
    37687 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37688 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_DNSGeneralSettingData', 0x80080005 - .
    37689 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37690 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'MSFT_NetAdapterSettingData', 0x80080005 - .
    37691 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37692 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_LogicalPort', 0x80080005 - .
    37693 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37694 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_NetworkPort', 0x80080005 - .
    37695 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37696 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_ProtocolEndpoint', 0x80080005 - .
    37697 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37698 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_LANEndpoint', 0x80080005 - .
    37699 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37700 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_DNSProtocolEndpoint', 0x80080005 - .
    37701 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37702 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_SecurityAssociationEndpoint', 0x80080005 - .
    37703 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37704 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_IKESAEndpoint', 0x80080005 - .
    37705 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37706 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_IPsecSAEndpoint', 0x80080005 - .
    37707 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37708 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_IPProtocolEndpoint', 0x80080005 - .
    37709 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37710 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_RemoteServiceAccessPoint', 0x80080005 - .
    37711 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37712 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_NetworkPipe', 0x80080005 - .
    37713 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37714 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_NextHopRoute', 0x80080005 - .
    37715 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37716 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_IKEAction', 0x80080005 - .
    37717 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37718 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'MSFT_NetIKEAuthSet', 0x80080005 - .
    37719 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37720 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'MSFT_NetIKECryptoSet', 0x80080005 - .
    37721 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37722 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_PolicyRule', 0x80080005 - .
    37723 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37724 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_SARule', 0x80080005 - .
    37725 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37726 17:04:30 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'MSFT_NetSARule', 0x80080005 - .
    37727 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37728 17:04:30 (0) ** - Root/CIMV2, InstancesOf, 'Win32_ComputerSystem', 0x80080005 - Server execution failed.
    37729 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37730 17:04:30 (0) ** - Root/CIMV2, InstancesOf, 'Win32_Service', 0x80080005 - Server execution failed.
    37731 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37732 17:04:30 (0) ** - Root/CIMV2, InstancesOf, 'Win32_Process', 0x80080005 - Server execution failed.
    37733 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37734 17:04:30 (0) ** - Root/CIMV2, InstancesOf, 'Win32_OperatingSystem', 0x80080005 - Server execution failed.
    37735 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37736 17:04:30 (0) ** - Root/CIMV2, InstancesOf, 'Win32_BIOS', 0x80080005 - Server execution failed.
    37737 17:04:30 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    37738 17:04:30 (0) **
    37739 17:04:30 (1) !! ERROR: WMI EXECQUERY operation errors reported: ..................................................................... 17 ERROR(S)!
    37740 17:04:30 (0) ** - Root/CIMV2, Select * From Win32_LogicalDisk WHERE FreeSpace > 10000000 AND DriveType = 3, 0x80080005 - Server execution failed.
    37741 17:04:30 (0) ** - Root/CIMV2, Select DriveType From Win32_LogicalDisk WHERE Name='C:', 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    37742 17:04:30 (0) ** - Root/CIMV2, Select * From Win32_Service, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    37743 17:04:30 (0) ** - Root/CIMV2, Select * From Win32_PageFileUsage, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    37744 17:04:30 (0) ** - Root/CIMV2, Select * From Win32_BIOS WHERE Version IS NOT NULL, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    37745 17:04:30 (0) ** - Root/CIMV2, Select * From Win32_NetworkAdapter WHERE AdapterType IS NOT NULL AND AdapterType != "Wide Area Network (WAN)" AND Description != "Packet Scheduler Miniport", 0x80080005 - Server execution failed.
    37746 17:04:30 (0) ** - Root/CIMV2, Select * From Win32_Processor WHERE Name IS NOT NULL, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    37747 17:04:30 (0) ** - Root/CIMV2, Select * From Win32_DiskDrive, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    37748 17:04:30 (0) ** - Root/CIMV2, Select * From Win32_ComputerSystem, 0x80080005 - Server execution failed.
    37749 17:04:30 (0) ** - Root/CIMV2, Select * From Win32_DiskPartition, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    37750 17:04:30 (0) ** - Root/CIMV2, Select * From Win32_LogicalDisk WHERE Description != "Network Connection", 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    37751 17:04:30 (0) ** - Root/CIMV2, Select * From Win32_VideoController, 0x80080005 - Server execution failed.
    37752 17:04:30 (0) ** - Root/CIMV2, Select * From Win32_USBController, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    37753 17:04:30 (0) ** - Root/CIMV2, Select * From Win32_DesktopMonitor, 0x80080005 - Server execution failed.
    37754 17:04:30 (0) ** - Root/CIMV2, Select * From Win32_PointingDevice WHERE Status = "OK", 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    37755 17:04:30 (0) ** - Root/CIMV2, Select * From Win32_Keyboard, 0x80080005 - Server execution failed.
    37756 17:04:30 (0) ** - Root/CIMV2, Select * From Win32_SystemDriver WHERE StartMode != "Disabled", 0x80080005 - Server execution failed.
    37757 17:04:30 (0) **
    37758 17:04:30 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
    37759 17:04:30 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    37760 17:04:30 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    37761 17:04:30 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    37762 17:04:30 (0) ** WMI static instances retrieved: ..................................................................................... 2004.
    37763 17:04:30 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    37764 17:04:30 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
    37765 17:04:30 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    37766 17:04:30 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
    37767 17:04:30 (0) **   DCOM: ............................................................................................................. ERROR!
    37768 17:04:30 (0) **   WINMGMT: .......................................................................................................... ERROR!
    37769 17:04:30 (0) **   WMIADAPTER: ....................................................................................................... ERROR!
    37770 17:04:30 (0) **
    37771 17:04:30 (0) ** # of additional Event Log events AFTER WMIDiag execution:
    37772 17:04:30 (0) **   DCOM: ............................................................................................................. ERROR!
    37773 17:04:30 (0) **   WINMGMT: .......................................................................................................... ERROR!
    37774 17:04:30 (0) **   WMIADAPTER: ....................................................................................................... ERROR!
    37775 17:04:30 (0) **
    37776 17:04:30 (0) ** 47 error(s) 0x80080005 - (WBEM_UNKNOWN) This error code is external to WMI.
    37777 17:04:30 (0) **
    37778 17:04:30 (0) ** 10 error(s) 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema
    37779 17:04:30 (0) ** => This error is typically due to the following major reasons:
    37780 17:04:30 (0) **    - The application queried by the WMI provider is not installed, not available or not running
    37781 17:04:30 (0) **      at the time of the request was made. This error can also be generated because
    37782 17:04:30 (0) **      the application supporting the providers has been uninstalled.
    37783 17:04:30 (0) **    - Some WMI providers (i.e. RSOP Planning Mode, Exchange 2003) are implemented as a WMI service.
    37784 17:04:30 (0) **      Make sure the required services are successfully started.
    37785 17:04:30 (0) **    - The WMI provider binary files are not accessible (i.e. access denied ACL).
    37786 17:04:30 (0) **    - A WMI provider registration problem at the CIM level (MOFCOMP.EXE) or at the COM level (REGSVR32.EXE).
    37787 17:04:30 (0) **      You must re-register the WMI provider by recompiling its associated MOF file with MOFCOMP.EXE
    37788 17:04:30 (0) **    Note: - If the WMI provider DLL CIM and COM registrations are correct, this error can
    37789 17:04:30 (0) **            be returned because the provider has a dependency on another DLL that cannot be
    37790 17:04:30 (0) **            loaded (missing or bad DLL)
    37791 17:04:30 (0) **          - Dependencies can be found with the DEPENDS.EXE tool coming with the
    37792 17:04:30 (0) **            Windows XP and Windows 2003 Support Tools. The command line is as follows:
    37793 17:04:30 (0) **            i.e. DEPENDS.EXE <PATH><Provider.DLL>
    37794 17:04:30 (0) ** => When a WMI provider fails to load, it is possible to trace the provider load process by
    37795 17:04:30 (0) **    submitting, via WBEMTEST and asynchronously, the following WMI event query:
    37796 17:04:30 (0) **    'Select * From MSFT_WmiSelfEvent'
    37797 17:04:30 (0) **    Then you can trace the following WMI events:
    37798 17:04:30 (0) **    - Msft_WmiProvider_ComServerLoadOperationEvent
    37799 17:04:30 (0) **    - Msft_WmiProvider_InitializationOperationEvent
    37800 17:04:30 (0) **    - Msft_WmiProvider_LoadOperationEvent
    37801 17:04:30 (0) **    and depending on the WMI operation executed, you can trace the following WMI events:
    37802 17:04:30 (0) **    i.e. for an enumeration:
    37803 17:04:30 (0) **    - Msft_WmiProvider_CreateInstanceEnumAsyncEvent_Pre and Msft_WmiProvider_CreateInstanceEnumAsyncEvent_Post
    37804 17:04:30 (0) **    i.e. for a put operation:
    37805 17:04:30 (0) **    - Msft_WmiProvider_PutInstanceAsyncEvent_Pre and Msft_WmiProvider_PutInstanceAsyncEvent_Post
    37806 17:04:30 (0) **
    37807 17:04:30 (0) ** => If the software has been de-installed intentionally, then this information must be
    37808 17:04:30 (0) **    removed from the WMI repository. You can use the 'WMIC.EXE' command to remove the provider
    37809 17:04:30 (0) **    registration data and its set of associated classes.
    37810 17:04:30 (0) ** => To correct this situation, you can:
    37811 17:04:30 (0) **    - Install or start the application supporting these providers.
    37812 17:04:30 (0) **    - Register the providers in CIM (MOFCOMP) or DCOM (REGSVR32).
    37813 17:04:30 (0) **    Note: In this case the provider should also be listed in the 'missing WMI
    37814 17:04:30 (0) **          provider DCOM registrations' or in the 'missing WMI provider files' section.
    37815 17:04:30 (2) !! WARNING: Re-registering with REGSVR32.EXE all DLL from 'C:\WINDOWS\SYSTEM32\WBEM\'
    37816 17:04:30 (0) **          may not solve the problem as the DLL supporting the WMI class(es)
    37817 17:04:30 (0) **          can be located in a different folder.
    37818 17:04:30 (0) **          You must refer to the class name to determine the software delivering the related DLL.
    37819 17:04:30 (0) **
    37820 17:04:30 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    37821 17:04:30 (0) ** WMI Registry key setup: ............................................................................................. OK.
    37822 17:04:30 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    37823 17:04:30 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    37824 17:04:30 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    37825 17:04:30 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    37826 17:04:30 (0) **
    37827 17:04:30 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    37828 17:04:30 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
    37829 17:04:30 (0) ** ----------------------------------------------------------------------------------------------------------------------------------


    • Edited by VaidasT Sunday, March 20, 2016 3:24 PM
    Sunday, March 20, 2016 3:22 PM
  • Hi,

    Please try to rebuild WMI to see whether the issue persists.

    More information for you:

    WMI: Rebuilding the WMI Repository

    https://blogs.technet.microsoft.com/askperf/2009/04/13/wmi-rebuilding-the-wmi-repository/

    WMI corrupt - how to reinstall/repair

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/8ed26d46-9994-4052-a307-5b071805aea8/wmi-corrupt-how-to-reinstallrepair?forum=winservergen

    Best Regards,

    Amy


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, March 25, 2016 9:19 AM
    Moderator
  • Do you think it is necessary to rebuild it, because if I run winmgmt /verifyrepository it shows that WMI repository is consistent.
    Wednesday, March 30, 2016 6:56 PM