none
DCOM Event 10010 Errors on Server 2012 R2 with Exchange 2016

    Question

  • Hello,

     Not too long after we setup a new Exchange 2016 Standard server, on Windows Server 2012 R2, we began seeing Event ID 10010, DistributedCOM errors in the System event log:

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

    These seem to occur about every 1-2 minutes.   By all appearances, Exchange (the only application running on this machine) is running fine.   The machine is a Dell PowerEdge R430 with 32GB of RAM.

    I found a thread about this same issue, though, virtualization and backup snapshots seem to have been a culprit, in that case.  We use Unitrends to backup the store and file system in the evenings, and early AM, though these errors are appearing throughout the day in the System log.   Other applications that are installed on this server include Trend Micro OfficeScan, Oracle Client for ODBC, and two third party transport agents.   (This is a standalone Exchange server using local storage.)

    Any tips would be greatly appreciated!

    M

     


    Maurice


    • Edited by MauriceSC Monday, October 17, 2016 6:47 PM spell check
    Monday, October 17, 2016 6:46 PM

Answers

  • Hi,

    Thanks for your post.

    Please follow steps below to troubleshoot it,

    Using the GUID in the error message to find what application it is.

    1. Using Regedit, navigate to the following registry value: HKEY_CLASSES_ROOT\CLSID\clsid value\LocalServer32. The clsid value is the information displayed in the message.
    2. In the right pane, double-click Default. The Edit String dialog box is displayed. Leave this dialog box open.
    3. Click Start, and then click This PC.
    4. Using the information displayed in the Value data box of the Edit String dialog box, navigate to the program.
    5. Right-click the program name, and then click Properties. The Properties dialog box for the program is displayed.
    6. To determine who the vendor is for this program, refer to the Version tab.

    If you can’t find the file in the corresponding path, please replace with a good file.

    Check if the related service have started. Stop and try to restart it.

    If you have third party application, please disable it temporary, to see if this issue was caused by it.

    Regarding to Event ID 10010, please refer to the following article.

    Event ID 10010 — COM General Functionality

    There is a thread that provide some causes and resolutions for the Event ID 10010, please also refer to.

    DistributedCOM Error ID 10010

    Best Regards,

    Alvin Wang


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

    • Marked as answer by MauriceSC Wednesday, October 19, 2016 5:22 PM
    Tuesday, October 18, 2016 8:18 AM
    Moderator
  • Hi,

    Thanks for your update.

    Below article may be helpful to you:

    WMI: Missing or Failing WMI Providers or Invalid WMI Class

    https://blogs.technet.microsoft.com/askperf/2014/08/11/wmi-missing-or-failing-wmi-providers-or-invalid-wmi-class/

    Best Regards,

    Alvin Wang


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

    • Marked as answer by MauriceSC Wednesday, October 19, 2016 5:22 PM
    Wednesday, October 19, 2016 2:00 AM
    Moderator

All replies

  • Hi,

    Thanks for your post.

    Please follow steps below to troubleshoot it,

    Using the GUID in the error message to find what application it is.

    1. Using Regedit, navigate to the following registry value: HKEY_CLASSES_ROOT\CLSID\clsid value\LocalServer32. The clsid value is the information displayed in the message.
    2. In the right pane, double-click Default. The Edit String dialog box is displayed. Leave this dialog box open.
    3. Click Start, and then click This PC.
    4. Using the information displayed in the Value data box of the Edit String dialog box, navigate to the program.
    5. Right-click the program name, and then click Properties. The Properties dialog box for the program is displayed.
    6. To determine who the vendor is for this program, refer to the Version tab.

    If you can’t find the file in the corresponding path, please replace with a good file.

    Check if the related service have started. Stop and try to restart it.

    If you have third party application, please disable it temporary, to see if this issue was caused by it.

    Regarding to Event ID 10010, please refer to the following article.

    Event ID 10010 — COM General Functionality

    There is a thread that provide some causes and resolutions for the Event ID 10010, please also refer to.

    DistributedCOM Error ID 10010

    Best Regards,

    Alvin Wang


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

    • Marked as answer by MauriceSC Wednesday, October 19, 2016 5:22 PM
    Tuesday, October 18, 2016 8:18 AM
    Moderator
  • Hello Alvin,

     Thank you very much for the advice!

     I checked and it is related to "wmiprvse.exe", which appears to be a WMI component.

     The WMI service is running in windows.  However, when I pulled up the properties for WMI Control under Services and Applications, it takes a very long time for the window to come up.   When it does appear, it shows:

    Failed to initialize all required WMI classes...
    Win32_Processor: Windows: Server execution failedWin32_WMISetting: Successful
    Security information: Successful
    Win32_OperatingSystem: Windows: Server execution failed

    I'll do some research into this and will follow up with any resolution that I find, thanks again.


    Maurice

    Tuesday, October 18, 2016 12:27 PM
  • Hi,

    Thanks for your update.

    Below article may be helpful to you:

    WMI: Missing or Failing WMI Providers or Invalid WMI Class

    https://blogs.technet.microsoft.com/askperf/2014/08/11/wmi-missing-or-failing-wmi-providers-or-invalid-wmi-class/

    Best Regards,

    Alvin Wang


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

    • Marked as answer by MauriceSC Wednesday, October 19, 2016 5:22 PM
    Wednesday, October 19, 2016 2:00 AM
    Moderator
  • Thanks Alvwan I'm looking that over now.   I did run wmidiag, and got these results --

    (I saw the suggestion to change DCOM Default Impersonation to 'Identify' in the results.   Its currently set to 'Impersonate', which I did not want to change because I'm assuming that Exchange setup set that..???)


    Windows Server 2012 R2 - No Service Pack - 64-bit (9600) 
    43146 10:54:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    43147 10:54:18 (0) ** Environment: ........................................................................................................ OK.
    43148 10:54:18 (0) ** There are no missing WMI system files: .............................................................................. OK.
    43149 10:54:18 (0) ** There are no missing WMI repository files: .......................................................................... OK.
    43150 10:54:18 (0) ** WMI repository state: ............................................................................................... N/A.
    43151 10:54:18 (0) ** AFTER running WMIDiag:
    43152 10:54:18 (0) ** The WMI repository has a size of: ................................................................................... 61 MB.
    43153 10:54:18 (0) ** - Disk free space on 'C:': .......................................................................................... 83299 MB.
    43154 10:54:18 (0) **   - INDEX.BTR,                     8454144 bytes,      10/18/2016 10:43:46 AM
    43155 10:54:18 (0) **   - MAPPING1.MAP,                  180256 bytes,       10/18/2016 10:43:46 AM
    43156 10:54:18 (0) **   - MAPPING2.MAP,                  180256 bytes,       10/18/2016 10:29:16 AM
    43157 10:54:18 (0) **   - OBJECTS.DATA,                  55427072 bytes,     10/18/2016 10:43:46 AM
    43158 10:54:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    43159 10:54:18 (2) !! WARNING: Windows Firewall: .......................................................................................... DISABLED.
    43160 10:54:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    43161 10:54:18 (2) !! WARNING: DCOM Status: ............................................................................................... WARNING!
    43162 10:54:18 (2) !! WARNING: => The DCOM Default Impersonation is NOT set to 'Identify'.
    43163 10:54:18 (0) **    This could prevent WMI to work correctly.
    43164 10:54:18 (0) **    You can fix the DCOM configuration by:
    43165 10:54:18 (0) **    - Executing the 'DCOMCNFG.EXE' command.
    43166 10:54:18 (0) **    - Expanding 'Component Services' and 'Computers' nodes.
    43167 10:54:18 (0) **    - Editing properties of 'My Computer' node.
    43168 10:54:18 (0) **    - Editing the 'Default properties' tab.
    43169 10:54:18 (0) **    - Set the 'Default Impersonation level' listbox to 'Identify'.
    43170 10:54:18 (0) **    From the command line, the DCOM configuration can be corrected with the following command:
    43171 10:54:18 (0) **    i.e. 'REG.EXE Add HKLM\SOFTWARE\Microsoft\Ole /v LegacyImpersonationLevel /t REG_DWORD /d 2 /f'
    43172 10:54:18 (0) ** 
    43173 10:54:18 (0) ** WMI registry setup: ................................................................................................. OK.
    43174 10:54:18 (0) ** INFO: WMI service has dependents: ................................................................................... 1 SERVICE(S)!
    43175 10:54:18 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
    43176 10:54:18 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
    43177 10:54:18 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
    43178 10:54:18 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
    43179 10:54:18 (0) **          this can prevent the service/application to work as expected.
    43180 10:54:18 (0) ** 
    43181 10:54:18 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
    43182 10:54:18 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
    43183 10:54:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    43184 10:54:18 (0) ** WMI service DCOM setup: ............................................................................................. OK.
    43185 10:54:18 (0) ** WMI components DCOM registrations: .................................................................................. OK.
    43186 10:54:18 (0) ** WMI ProgID registrations: ........................................................................................... OK.
    43187 10:54:18 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
    43188 10:54:18 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
    43189 10:54:18 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
    43190 10:54:18 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
    43191 10:54:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    43192 10:54:18 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
    43193 10:54:18 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
    43194 10:54:18 (0) **    i.e. You can start your scripts or WMIC commands from an elevated command
    43195 10:54:18 (0) **         prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
    43196 10:54:18 (0) **         selecting 'Run as Administrator'.
    43197 10:54:18 (0) **    i.e. You can also execute the WMI scripts or WMIC commands as a task
    43198 10:54:18 (0) **         in the Task Scheduler within the right security context.
    43199 10:54:18 (0) ** 
    43200 10:54:18 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
    43201 10:54:18 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
    43202 10:54:18 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
    43203 10:54:18 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
    43204 10:54:18 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
    43205 10:54:18 (0) ** 
    43206 10:54:18 (0) ** Overall DCOM security status: ....................................................................................... OK.
    43207 10:54:18 (0) ** Overall WMI security status: ........................................................................................ OK.
    43208 10:54:18 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
    43209 10:54:18 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 1.
    43210 10:54:18 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
    43211 10:54:18 (0) **   'select * from MSFT_SCMEventLogEvent'
    43212 10:54:18 (0) ** 
    43213 10:54:18 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
    43214 10:54:18 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 4 NAMESPACE(S)!
    43215 10:54:18 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
    43216 10:54:18 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
    43217 10:54:18 (0) ** - ROOT/MICROSOFTIISV2.
    43218 10:54:18 (0) ** - ROOT/SERVICEMODEL.
    43219 10:54:18 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
    43220 10:54:18 (0) **    use an encrypted connection by specifying the PACKET PRIVACY authentication level.
    43221 10:54:18 (0) **    (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
    43222 10:54:18 (0) **    i.e. 'WMIC.EXE /NODE:"MAIL" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
    43223 10:54:18 (0) ** 
    43224 10:54:18 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
    43225 10:54:18 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
    43226 10:54:18 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 3 ERROR(S)!
    43227 10:54:18 (0) ** - Root/CIMv2, Win32_Process.Handle=36632, 0x80080005 - Server execution failed.
    43228 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43229 10:54:18 (0) ** - Root/CIMv2, Win32_Process.Handle=36632, 0x80080005 - Server execution failed.
    43230 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43231 10:54:18 (0) ** - Root/CIMv2, Win32_Process.Handle=1640, 0x80080005 - Server execution failed.
    43232 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43233 10:54:18 (0) ** 
    43234 10:54:18 (0) ** WMI MOF representations: ............................................................................................ OK.
    43235 10:54:18 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
    43236 10:54:18 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 32 ERROR(S)!
    43237 10:54:18 (0) ** - ROOT/CIMV2, InstancesOfAsync, 'CIM_USBDevice', 0x80080005 - .
    43238 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43239 10:54:18 (0) ** - ROOT/CIMV2, InstancesOfAsync, 'CIM_USBHub', 0x80080005 - .
    43240 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43241 10:54:18 (0) ** - ROOT/CIMV2, InstancesOfAsync, 'CIM_StorageVolume', 0x80080005 - .
    43242 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43243 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_IKEProposal', 0x80080005 - .
    43244 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43245 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'MSFT_NetIKEAuthProposal', 0x80080005 - .
    43246 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43247 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'MSFT_NetIKECryptoProposal', 0x80080005 - .
    43248 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43249 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_IPAssignmentSettingData', 0x80080005 - .
    43250 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43251 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_DNSGeneralSettingData', 0x80080005 - .
    43252 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43253 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'MSFT_NetAdapterSettingData', 0x80080005 - .
    43254 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43255 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_LogicalPort', 0x80080005 - .
    43256 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43257 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_NetworkPort', 0x80080005 - .
    43258 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43259 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_ProtocolEndpoint', 0x80080005 - .
    43260 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43261 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_LANEndpoint', 0x80080005 - .
    43262 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43263 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_DNSProtocolEndpoint', 0x80080005 - .
    43264 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43265 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_SecurityAssociationEndpoint', 0x80080005 - .
    43266 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43267 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_IKESAEndpoint', 0x80080005 - .
    43268 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43269 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_IPsecSAEndpoint', 0x80080005 - .
    43270 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43271 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_IPProtocolEndpoint', 0x80080005 - .
    43272 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43273 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_RemoteServiceAccessPoint', 0x80080005 - .
    43274 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43275 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_NetworkPipe', 0x80080005 - .
    43276 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43277 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_NextHopRoute', 0x80080005 - .
    43278 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43279 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_IKEAction', 0x80080005 - .
    43280 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43281 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'MSFT_NetIKEAuthSet', 0x80080005 - .
    43282 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43283 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'MSFT_NetIKECryptoSet', 0x80080005 - .
    43284 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43285 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_PolicyRule', 0x80080005 - .
    43286 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43287 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'CIM_SARule', 0x80080005 - .
    43288 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43289 10:54:18 (0) ** - ROOT/STANDARDCIMV2, InstancesOfAsync, 'MSFT_NetSARule', 0x80080005 - .
    43290 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43291 10:54:18 (0) ** - Root/CIMV2, InstancesOf, 'Win32_ComputerSystem', 0x80080005 - Server execution failed.
    43292 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43293 10:54:18 (0) ** - Root/CIMV2, InstancesOf, 'Win32_Service', 0x80080005 - Server execution failed.
    43294 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43295 10:54:18 (0) ** - Root/CIMV2, InstancesOf, 'Win32_Process', 0x80080005 - Server execution failed.
    43296 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43297 10:54:18 (0) ** - Root/CIMV2, InstancesOf, 'Win32_OperatingSystem', 0x80080005 - Server execution failed.
    43298 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43299 10:54:18 (0) ** - Root/CIMV2, InstancesOf, 'Win32_BIOS', 0x80080005 - Server execution failed.
    43300 10:54:18 (0) **   MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)'
    43301 10:54:18 (0) ** 
    43302 10:54:18 (1) !! ERROR: WMI EXECQUERY operation errors reported: ..................................................................... 17 ERROR(S)!
    43303 10:54:18 (0) ** - Root/CIMV2, Select * From Win32_LogicalDisk WHERE FreeSpace > 10000000 AND DriveType = 3, 0x80080005 - Server execution failed.
    43304 10:54:18 (0) ** - Root/CIMV2, Select DriveType From Win32_LogicalDisk WHERE Name='C:', 0x80080005 - Server execution failed.
    43305 10:54:18 (0) ** - Root/CIMV2, Select * From Win32_Service, 0x80080005 - Server execution failed.
    43306 10:54:18 (0) ** - Root/CIMV2, Select * From Win32_PageFileUsage, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    43307 10:54:18 (0) ** - Root/CIMV2, Select * From Win32_BIOS WHERE Version IS NOT NULL, 0x80080005 - Server execution failed.
    43308 10:54:18 (0) ** - Root/CIMV2, Select * From Win32_NetworkAdapter WHERE AdapterType IS NOT NULL AND AdapterType != "Wide Area Network (WAN)" AND Description != "Packet Scheduler Miniport", 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    43309 10:54:18 (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.
    43310 10:54:18 (0) ** - Root/CIMV2, Select * From Win32_DiskDrive, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    43311 10:54:18 (0) ** - Root/CIMV2, Select * From Win32_ComputerSystem, 0x80080005 - Server execution failed.
    43312 10:54:18 (0) ** - Root/CIMV2, Select * From Win32_DiskPartition, 0x80080005 - Server execution failed.
    43313 10:54:18 (0) ** - Root/CIMV2, Select * From Win32_LogicalDisk WHERE Description != "Network Connection", 0x80080005 - Server execution failed.
    43314 10:54:18 (0) ** - Root/CIMV2, Select * From Win32_VideoController, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    43315 10:54:18 (0) ** - Root/CIMV2, Select * From Win32_USBController, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    43316 10:54:18 (0) ** - Root/CIMV2, Select * From Win32_DesktopMonitor, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    43317 10:54:18 (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.
    43318 10:54:18 (0) ** - Root/CIMV2, Select * From Win32_Keyboard, 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    43319 10:54:18 (0) ** - Root/CIMV2, Select * From Win32_SystemDriver WHERE StartMode != "Disabled", 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema.
    43320 10:54:18 (0) ** 
    43321 10:54:18 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
    43322 10:54:18 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    43323 10:54:18 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    43324 10:54:18 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    43325 10:54:18 (0) ** WMI static instances retrieved: ..................................................................................... 2089.
    43326 10:54:18 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    43327 10:54:18 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
    43328 10:54:18 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    43329 10:54:18 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
    43330 10:54:18 (0) **   DCOM: ............................................................................................................. ERROR!
    43331 10:54:18 (0) **   WINMGMT: .......................................................................................................... ERROR!
    43332 10:54:18 (0) **   WMIADAPTER: ....................................................................................................... ERROR!
    43333 10:54:18 (0) ** 
    43334 10:54:18 (0) ** # of additional Event Log events AFTER WMIDiag execution:
    43335 10:54:18 (0) **   DCOM: ............................................................................................................. ERROR!
    43336 10:54:18 (0) **   WINMGMT: .......................................................................................................... ERROR!
    43337 10:54:18 (0) **   WMIADAPTER: ....................................................................................................... ERROR!
    43338 10:54:18 (0) ** 
    43339 10:54:18 (0) ** 42 error(s) 0x80080005 - (WBEM_UNKNOWN) This error code is external to WMI.
    43340 10:54:18 (0) ** 
    43341 10:54:18 (0) ** 10 error(s) 0x80041013 - (WBEM_E_PROVIDER_LOAD_FAILURE) COM cannot locate a provider referenced in the schema
    43342 10:54:18 (0) ** 


    Maurice

    Wednesday, October 19, 2016 1:38 PM
  • Hi,

    Thanks for your reply.

    I think you could set to identify to have a test since it is mentioned in the wmidiag report.

    "Default Impersonation Level: Select the system-wide default level of authority that a COM client on this computer can grant to a server application to perform processing tasks on its behalf. Levels are listed in order of increasing authority."

    Best Regards,

    Alvin Wang


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

    Friday, October 21, 2016 8:28 AM
    Moderator