A
a3pl
Last month we bought new servers and we made a small 2 node cluster of 2 Windows 2016 with Hyper-V.
Everything is fine, but after 2 or 3 days, servers (hosts) are starting to have problems with WMI.
For example:
- in wbemtest i can not get any informations (Error numer: 0x80004005 when enumerating classes),
- wmic isnt working (I get ERROR: Description = Invalid query for every command),
- simple get-wmiobject -list in PS is not working ending with error:
Get-WmiObject :
At line:1 char:1
+ Get-WmiObject -list
+ ~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified:
) [Get-WmiObject], COMException
+ FullyQualifiedErrorId : System.Runtime.InteropServices.COMException,Microsoft.PowerShell.Commands.GetWmiObjectCo
mmand
After reboot of server, WMI is working fine again for another 2 or 3 days.
I can not reboot host servers in Hyper-V cluster every 2 days.
Any ideas how to solve that problem ?
Continue reading...
Everything is fine, but after 2 or 3 days, servers (hosts) are starting to have problems with WMI.
For example:
- in wbemtest i can not get any informations (Error numer: 0x80004005 when enumerating classes),
- wmic isnt working (I get ERROR: Description = Invalid query for every command),
- simple get-wmiobject -list in PS is not working ending with error:
Get-WmiObject :
At line:1 char:1
+ Get-WmiObject -list
+ ~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified:
) [Get-WmiObject], COMException+ FullyQualifiedErrorId : System.Runtime.InteropServices.COMException,Microsoft.PowerShell.Commands.GetWmiObjectCo
mmand
After reboot of server, WMI is working fine again for another 2 or 3 days.
I can not reboot host servers in Hyper-V cluster every 2 days.
Any ideas how to solve that problem ?
Continue reading...