Why WMI monitor switches to Down state soon after being started?
Q: WMI monitor starts, but soon switches to ‘Down’ state. How to fix that?
A: If you are sure all the parameters of your WMI monitor (credentials, query etc.) are correct, try to start it and pay attention to Log pane.
You will most probably find error message and error code in the end of string starting with “Poll failed”. Example: “The RPC server is unavailable. (0x800706ba)”
Extensive list of steps to handle WMI problems is available in MSDN article WMI troubleshooting. For a quick start, make sure the following has been checked:
- Remote Procedure Call service is running on remote host
- Firewall doesn’t block RPC calls from source computer
- Proper WMI credentials are used
Follow the above link to make sure you have set up WMI access correctly.
Related Topics:
How can I monitor disk I/O speed?
How to monitor a Windows process and restart it when it goes down?
Check out our Knowledge Base where we answer questions regarding various topics. Check the Log pane after starting the monitor and look for the Poll failed message, error text, and error code. It usually points to a remote WMI access problem, such as the Remote Procedure Call service not running, firewall blocks, or incorrect WMI credentials. Verify that RPC is running on the remote host, firewall rules allow RPC calls from the polling computer, and the monitor uses valid WMI credentials.
Frequently Asked Questions
What should I check first when a WMI monitor quickly goes Down?
What does RPC server unavailable usually point to?
Which basic prerequisites should be verified for WMI polling?