What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

80070005: Access is denied

Votes:

0

Your Vote:

Up

Down

We are getting the above error with some sensors (not all) on some servers (not all) WMI is working correctly and if I use a local machine account (as opposed to the domain account we normally use) it works fine. It mainly affects only CPU and Disk usage sensors, others work normally. Any ideas ? PS: Have rebooted servers and reset WMI.

error prtg wmi

Created on Mar 13, 2015 10:40:50 AM by  tfountain (40) 1



5 Replies

Votes:

1

Your Vote:

Up

Down

Did you check if the domain account is a member of the local administrators group on those servers?

Created on Mar 13, 2015 3:15:57 PM by  PRTG Tools Family [prtgtoolsfamily.com] (13,273) 3 4



Votes:

0

Your Vote:

Up

Down

Dear TFountain

Do you have sporadic issues, or did those sensors never work to begin with?

Many WMI connection issues can be circumvented with a PRTG remote probe. If you move the WMI sensors to that probe, the WMI query is done locally.

The other option is to use SNMP instead of WMI. A commonly used agent is "SNMP Informant" which offers to monitor a range of performance metrics via SNMP. The PRTG "SNMP Library" sensor comes with a library for the free SNMP Informant version.

Created on Mar 16, 2015 10:22:56 AM by  Arne Seifert [Paessler Support]

Last change on Mar 16, 2015 10:23:57 AM by  Arne Seifert [Paessler Support]



Votes:

4

Your Vote:

Up

Down

Just for information and to help others suffering similar issues, the fix is.....

Remove KB3002567 hot fix from DC's (this is a netlogon hotfix), all starting working again.

Created on Mar 17, 2015 4:34:03 PM by  tfountain (40) 1



Votes:

0

Your Vote:

Up

Down

i found that by switching to the local admin account on the server over the domain account we use for other services this problem went away. Cudoes to the first response with that idea. We did check our domain controllers for the KB referenced in the others and that did not remedy the problem.

Created on Jan 8, 2018 6:01:07 PM by  lheruska (0)



Votes:

0

Your Vote:

Up

Down

Dear lheruska,

thank you for your input.

Created on Jan 9, 2018 4:32:28 PM by  Arne Seifert [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.