Connection could not be established (code: PE015)

Modified on 2025-06-10 12:14:41 +0200

There are some problems with sensors on several servers, "Connection could not be established (code: PE015)" error periodically appears. I checked the WMI and RPC services (restarted them), launched the tester, scrolled the logs, even updated the PRTG version to 18.4.46.1754+ but still did not find the cause. The user who is registered in the server settings is the admin on all servers (not the admin domain).

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hi Elmira,

Please follow this guide and forward the logs of the probe where the WMI errors occur to support@paessler.com. I'll then be able to check what's reported back by these devices.

Kind regards,
Felix Saure, Tech Support Team

Feb, 2019 - Permalink

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.

Connection could not be established (code: PE015)

Article CommentsAttention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Search

Attention

Related Articles

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.