다음을 통해 공유


WMI Errors and SCVMM – If It’s Not Broken, Update It!

There are many errors that may appear, based on events in SCVMM, to be WMI related. An understandable response would be to troubleshoot WMI. On the other hand, many ‘Access Denied’ errors, while pointing to WMI in no way, are actually the result of WMI issues. Below are a number of error examples that in one way or another are related to WMI. The best way to deal with these errors is divide and conquer. First, determine if WMI itself is responding correctly. By this I mean that we test WMI functionality alone, not in combination with SCVMM which has its own detached namespace. Second, with no fundamental problems found with WMI due to NIC teaming or otherwise, there are three updates that may very well resolve your issue. These should be installed on all Windows 2008 servers that hold SCVMM components. The updates are at the bottom of this post. Good luck!

_____ERRORS_____

SCVMM Admin Console typical errors for Hosts
'Connection Status: Not responding'
'Virtualization service status: unknown"

WMI typical errors
Example #1
Log Name: Application
Source: Microsoft-Windows-WMI
Event ID: 10
Task Category: none
Description:
Event filter with query "select * from __instancemodificationevent within 30 where
targetinstance isa 'Win32_PerfFormattedData_PerfOS_Processor' and
targetinstance.PercentProcessorTime > 99 and targetinstance.Name != '_Total'" could
not be reactivated in namespace "//./root/CIMV2" because of error 0x80041010.
Events cannot be delivered through this filter until the problem is corrected.

Example #2
Log Name: Application
Source: Application Error
Event ID: 1000
Task Category: (100)
Description:
Faulting application wmiprvse.exe, version 6.0.6001.18000, time stamp 0x4791950f,
faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791adec, exception
code 0xc0000005, fault offset 0x000000000003e39c, process id 0x944, application
start time 0x01c95ba1faa603ce.

Jobs list errors in SCVMM Admin Console
Example #1

Error (2911)
Insufficient resources are available to complete this operation on the
server.contoso.com server.
(Not enough storage is available to complete this operation (0x8007000E))
Recommended Action
Ensure that the virtual machine host has sufficient memory and disk space to
perform this action. Try the operation again.

Example #2

Warning (10803)
Unable to refresh \\server.contoso.com\ISOS$\WinPE_X86_with_HyperV_ICs.iso because
the file is in use by another process.
Recommended Action
Wait for the next automatic library refresh, or manually refresh the library share
after the process completes.

Example #3
Error (2912)
An internal error has occurred trying to contact an agent on the server.contoso.com
server.
(No more threads can be created in the system (0x800700A4))
Recommended Action
Ensure the agent is installed and running. Ensure the WS-Management service is
installed and running, then restart the agent.

Example #4
Error (2912)
An internal error has occurred trying to contact an agent on the
ephypv01.constrution.enet server. (The paging file is too small for this operation
to complete (0x800705AF)
 

_____TEST_____  
Verify that various WMI namespaces can be connected to, then update WMI on all involved Windows 2008 machines

Using wbemtest
- Click the 'Start' button
- Start> Run> wbemtest
- Click 'Connect' and enter 'root\cimv2' then click 'Connect' again. This should not prompt with an error
- Click 'Connect' and enter 'root\default' then click 'Connect' again. This should not prompt with an error
On a Hyper-V server, this should also work
- Click 'Connect' and enter 'root\virtualization' then click 'Connect' again. This should not prompt with an error.

On an SCVMM Server (Host) this should also work
- Click 'Connect' and enter 'root\scvmm' then click 'Connect' again. This should not prompt with an error
- Close 'wbemtest'

Using command line
- From an elevated command prompt type 'wmic nic' and press Enter
- This should return information, not an error. If there is an error, and all other tests work, this is likely due to NIC TEAMING. Uninstall all NIC Teaming software, reboot and try again
- From an elevated command prompt type 'wmic diskdrive list brief' and press Enter
- This should return information, not an error

 

_____UPDATE_____

Install WMI Updates and Hotfixes
Each requires a reboot

954563 Memory corruption may occur with the Windows Management Instrumentation (WMI) service on a computer that is running Windows Server 2008 or Windows Vista Service Pack 1
https://support.microsoft.com/default.aspx?scid=kb;EN-US;954563

958124 A wmiprvse.exe process may leak memory when a WMI notification query is used heavily on a Windows Server 2008-based or Windows Vista-based computer
https://support.microsoft.com/default.aspx?scid=kb;EN-US;958124

 

955805 Certain applications become very slow on a Windows Server 2008-based or Windows Vista SP1-based computer when a certificate with SIA extension is installed

https://support.microsoft.com/kb/955805

Technorati Tags: microsoft,scvmm,hyper-v,virtual,virtualization,windows

Comments

  • Anonymous
    January 01, 2003
    thank you