UNKNOWN - The WMI query had problems
Posted: Fri Nov 05, 2021 12:54 am
Hi Team,
I am getting the below error for CPU usage monitor for some windows servers which are added in Nagios via WMI. I am seeing this error only for CPU usage monitor. Other services like memory, disk all are working as expected. I checked the WMI user and it has admin privilege. What is the reason for this issue and how this can be fixed ?
UNKNOWN - The WMI query had problems. The plugin is having trouble finding the required WMI Classes on the target host (<IP address>). There can be multiple reasons for this (please go through them and check) including permissions problems (try using an admin login) or software that creates the class is not installed (eg if you are trying to checkiis but IIS is not installed). It can also happen if your version of Windows does not support this check (this might be because the WMI fields are named differently in different Windows versions or your version of Windows does not even have the required WMI class). Sometimes, some systems 'lose' WMI Classes and you might need to rebuild your WMI repository. Sometimes the WMI service is not running, other times a reboot can fix it. Other causes include mistyping the WMI namesspace/class/fieldnames. There may be other causes as well. You can use wmic from the command line to troubleshoot. Wmic error text on the next line.
Regards,
Preethu
I am getting the below error for CPU usage monitor for some windows servers which are added in Nagios via WMI. I am seeing this error only for CPU usage monitor. Other services like memory, disk all are working as expected. I checked the WMI user and it has admin privilege. What is the reason for this issue and how this can be fixed ?
UNKNOWN - The WMI query had problems. The plugin is having trouble finding the required WMI Classes on the target host (<IP address>). There can be multiple reasons for this (please go through them and check) including permissions problems (try using an admin login) or software that creates the class is not installed (eg if you are trying to checkiis but IIS is not installed). It can also happen if your version of Windows does not support this check (this might be because the WMI fields are named differently in different Windows versions or your version of Windows does not even have the required WMI class). Sometimes, some systems 'lose' WMI Classes and you might need to rebuild your WMI repository. Sometimes the WMI service is not running, other times a reboot can fix it. Other causes include mistyping the WMI namesspace/class/fieldnames. There may be other causes as well. You can use wmic from the command line to troubleshoot. Wmic error text on the next line.
Regards,
Preethu