Common WMI errors?

First, download free WMI tester from here

And few things to check….

– Check WMI is installed. Type "wbemtest" from DOS prompt from both PC. If "WMI tester" window is popped up, it meant WMI is present.

1. Error message "Port Error 135: RPC Server not accessible

If you see this precise error message, the port which all DCOM communication protocols are routed over is blocked. This very likely is the case because the RPC server on the monitored machine is:

    – Blocked by a local firewall
    – Blocked by domain policies
    – DCOM service is not running
    – Running on a different port than specified in PRTG’s setting for this computer

Solution>

DOS prompt from monitored PC, "netsh firewall set service RemoteAdmin"

 

2. Error message "Error: 80080005: Access is denied"

 – 80070005 means that the Domain Controller / local Windows could not verify the credentials for the target computer.

Solution>

DOS prompt from monitored PC, type ‘secpol.msc’ to open "Local Security Policy"
Expand the "Local Policies" node and select "Security Options". Now scroll down to the setting titled "Network access: Sharing and security model for local accounts".
If this is set to "Guest only", change it to "Classic" and restart your computer, if needed.

3. Error message "Error: 80041003: Access is denied"

– 80041003 means that the user has no sufficient rights to use WMI, so you might want to check your access rights or the respective policies.

 Solution>

DOS prompt from monitored PC, type ‘secpol.msc’ to open "Local Security Policy"
Expand the "Local Policies" node and select "Security Options". Now scroll down to the setting titled "Network access: Sharing and security model for local accounts".
If this is set to "Guest only", change it to "Classic" and restart your computer, if needed.