Connection could not be established (code: PE015)
Modified on 2025-06-10 16:30:43 +0200
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.
Important: We no longer maintain this article. The information might be out of date.
We have a server with multiple sensors and all work with the exception of WMI Free Disk Space (Multi Disk)
i have removed and re-added and even removed the whole server and re added and let it detect sensors - all which it detects work flawlessly - as soon as i add WMI Free Disk Space (Multi Disk) it doe snot work and says its down.
Using the Paessler WMI test tool i run all the WMI tests to the server and they pass including SELECT * FROM Win32_logicaldisk which shows free disk space normally.
Credentials are inherited from the parent and other sensors like CPU, PING and RDP show up fine.
any further hints?
Article Comments
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.
Hi there,
Thank you very much for the contact.
Please review the following article and its problem solving approaches to solve this issue:
Why do I receive the sensor error message 'Connection could not be established (code: PE015)'?
Best regards,
Sebastian
Mar, 2019 - Permalink