What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

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

Connection could not be established (80070005: Access is denied) (code: PE015)

Votes:

3

Good afternoon, for the past three days I have been receiving error messages reporting Connection could not be established (80070005: Access is denied) (code: PE015) I am running 22.2.76.1705+, I believe that some recent Windows Server updates have impacted how PRTG is querying servers but I am not sure how to resolve the issue.

I am not sure what more credentials it needs. the service account is active and have not changed

prtg windows wmi

Created on Jun 17, 2022 4:17:47 PM

Last change on Jun 21, 2022 5:42:24 AM by  Timo Dambach [Paessler Support]



13 Replies

Votes:

1

After update KB5014738 or KB5014702, from 06 2022 all WMI sensors are dead with error 80070005.

Created on Jun 17, 2022 9:12:50 PM



Votes:

0

Any news on this subject? We are also experiencing these issues.

Created on Jun 20, 2022 8:42:30 AM



Votes:

0

thanks for the info, so is there a workaround available at the moment? or are we waiting on Paessler to release a update?

thank you

Created on Jun 20, 2022 1:18:36 PM

Last change on Jun 21, 2022 5:43:11 AM by  Timo Dambach [Paessler Support]



Votes:

1

If you recently installed Windows Updates KB5014692; KB5014754; KB5014699 & KB50004442 you might be affected by hardening changes. Microsoft recently rolled out a patch which hardens the DCOM authentication, which can cause authentication login attempts to fail. You can try to roll back the update or remove the registry entry as described here

As workaround you can also use this article to disable the hardening again.

Installing the updates on the PRTG server and rebooting PRTG afterwards might solve the issue as well. Ensure the same patches are installed on target device and PRTG server.

Created on Jun 21, 2022 5:51:39 AM by  Timo Dambach [Paessler Support]

Last change on Jul 12, 2022 12:12:18 PM by  Timo Dambach [Paessler Support]



Votes:

0

Unfortunately the trick to update the PRTG Server to the corresponding june patch didn't work either so right now we're also stuck with defunct WMI sensors. Due to policy reasons we are unable to uninstall the KBs or revert the hardening via registry. What to do?

Created on Jun 21, 2022 12:39:31 PM



Votes:

0

Unfortunately there's no other known workaround currently.

Created on Jun 22, 2022 7:18:57 AM by  Timo Dambach [Paessler Support]



Votes:

0

Experiencing this error as well...would it be possible to change wmi sensors to snmp? or will there be the same issue?

Created on Jun 28, 2022 2:34:45 PM



Votes:

0

In our experience the issue should be fixed if all updates are installed on PRTG server and target device. If you are still facing this issue even though all servers are on the same patch level, feel free to reach out to us directly via mail at [email protected] so we can take a closer look.

Only WMI is affected. Replacing WMI sensors with the SNMP based alternatives should work without issues. You'll find all available SNMP sensors here. And here is how to enable SNMP on Windows.

Created on Jun 29, 2022 6:38:10 AM by  Timo Dambach [Paessler Support]



Votes:

0

If the server is Windows 7, is there a solution other than RequireIntegrityActivationAuthenticationLevel=0?

Created on Jul 11, 2022 7:09:51 PM



Votes:

0

Same applies to Windows 7: If you are still facing this issue even though all servers are on the same patch level, feel free to reach out to us directly via mail at [email protected] so we can take a closer look.

Created on Jul 14, 2022 7:57:49 AM by  Timo Dambach [Paessler Support]



Votes:

0

In our case, security update KB5015808 on monitored server stopped communication with WMI sensors. Solution was to apply same KB on probe server.

Created on Jul 15, 2022 9:46:00 AM



Votes:

0

hey guys, i am also stuck with this issue since May-June.

This has been really frustrating and PRTG has been not helpful at all.

Created on Dec 24, 2022 5:32:24 AM



Votes:

0

Hello Saadahmed,

Can you confirm that the same windows updates and patch level is installed on both the PRTG Probe server as well as on the target device you are looking to monitor?

Created on Dec 26, 2022 2:42:27 PM by  Timo Dambach [Paessler Support]




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.