New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

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

 

Top Tags


View all Tags


Unable to create Active Directory Replication Errors sensor

Votes:

0

Your Vote:

Up

Down

When I try creating an Active Directory Replication Errors sensor on my domain controllers I get the dreaded Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) error.

So I figured it's some issue with WMI permissions or something. However, other WMI sensor types like Windows Uptime are working without a hitch on this system. The probe is joined in the domain I'm adding the sensor in, it has .NET 3.5 and 4.6 enabled through Server Manager, has credentials in the domain, and is a Windows Server 2016 OS. The target system is also a Windows Server 2016.

We are however stuck on 16.2.23.3270 and not able to upgrade.

What are some things that I can verify/rectify to get this sensor type working?

active-directory-replication prtg wmi wmi-error wmi-sensors

Created on Nov 9, 2018 8:39:35 AM by  Fraeco (0) 1



3 Replies

Votes:

0

Your Vote:

Up

Down

Hi there,

Could you try to use the sensor together with a full Domain Administrator instead of a limited user? Does the sensor work afterwards?

Best regards.

Created on Nov 9, 2018 12:32:36 PM by  Dariusz Gorka [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hi Dariusz, thanks for getting back to me.

The service user being used was already a member of the Domain Admins groups. However, upon you request I entered the credentials of another priviliged user directly on the server and this worked.

Upon further investigation I turns out the user was incorrectly defined. It was configured like this domain: <null> username:domain\srv-account instead of domain: domain username: srv-account.

I rectified this and was able to add the sensor without any problems now.

Created on Nov 9, 2018 2:42:18 PM by  Fraeco (0) 1



Votes:

0

Your Vote:

Up

Down

Hi there,

Great to hear that it was that easy to fix it. :)

Best regards.

Created on Nov 9, 2018 3:01:45 PM by  Dariusz Gorka [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.