Hi,

I recently migrated my PRTG Server installation from Amazon to Azure, and whilst it might be unrelated, I'm using full disclosure.

When I try to add a new WMI sensor - on any of my servers it comes back with the following error: Could not create the sensor WMI Service on device <DEVICENAME> (127.0.0.1).

Could not validate sensor preconditions

I have other WMI sensors that are working fine, and even when I try to add them again I get this error.

I also get this error when trying to add wmi sensors on any of my other servers.

PRTG Info: PRTG Version PRTG Network Monitor 15.3.17.2996 Auto-Update Status [12/07/2015 11:40:11 AM] Downloaded version (15.3.17.2996) is not newer than your current version (15.3.17.2996). Operating System Windows Server 2012 (6.2.2 Build 9200 ), 1 CPUs (Single x64 Model 45 Step 7), code page "Windows-1252", on HyperV Server Time 14.07.2015 07:58:19 (UTC+10:00)

Article Comments

Hi Slaziar,

Please try to enter the Windows Credentials directly in the device settings of the Remote Probe itself. Afterwards, you should be able to add the WMI Sensors to the probe device.

Best regards


Jul, 2015 - Permalink

Hi,

I thought I wrote a reply yesterday, but I attempted this with the domain administrator credentials with no success.

Considering that this remote probe has other WMI sensors, and I am having the issue on ALL my remote probe servers, most of which have WMI sensors, this sounds more like a server sided issue.

Regards,

Scott


Jul, 2015 - Permalink

Hi,

You mentioned that some WMI sensors are working, which exact sensor type does not work? Please do also try to add a new device with the private IP address of the PRTG Server or Remote Probe and see if the sensor works afterwards.

Best regards


Jul, 2015 - Permalink

It's strange, I put the windows credentials into the core probe service (on the remote computer mistakenly). When putting it onto the prtg server in Windows Credentials it works.

The question is, why have I been able to have wmi sensors (like WMI service, that I just had problems with) on the core probe before without having to enter Windows credentials, but I have to now?

Thanks,

Scott


Jul, 2015 - Permalink

Hi Slaziar,

This is a known bug in the current Stable version of PRTG which is already fixed in the recent Preview version. It's just affecting the meta scan of those sensors, this will be most likely the reason why some other WMI sensors worked properly. Please excuse the inconvenience.

Best regards


Jul, 2015 - Permalink