HI,

I'm having weird issue with a two different Windows 2016 std servers. If for some reasons windows lock up then i reboot system but after the reboot all wmi sensors are in error PE015. I tried several reboot with no luck. No problems occurs with WMITester. The only way i solve this is by removing completly the VM from PRTG then create it with the exact sensors.

I did not found any KB about this on the web so is there anyone that solved this king of recurring issue?

Regards Chris

Article Comments

Hello,

Thank you for your post.

Did you try restarting the probe that runs the WMI sensors?

Kind regards,
Sasa Ignjatovic, Tech Support Team


Sep, 2020 - Permalink

Hi, I did not tried this because the probe server is part of a bigger organisation that i dont have control on so i cannot do this. I dont see how this could solve the issue the probe is monotoring over 300 other devices without issue.

Regards


Sep, 2020 - Permalink

We have the same problem, i think this is some how related to Windows Server updates. After the last update installation and reboot, all our server WMI sensors turned down and we got the same error code PE015.

BR.

Juha


Sep, 2020 - Permalink

Hello,

You could try restarting the "PRTG Probe" service. If you do not have access to the system running the probe, you can restart all of your probes thru the PRTG web interface. For this go to Setup>System Administration>Administrative Tools and click on Go! under "Restart All Probes". The restart of the probe will also reset the WMI connection which may solve the issue.


Sep, 2020 - Permalink

Hello,

probe restart done the right way fixed the problem. I just restarted sensors earlier and it didnt help :)

Thank you!


Sep, 2020 - Permalink

Hi,

Thanks for your replies. I do not have acces to reboot from the console. What i'm stunned is that this problem occurs every month for only two of tousands of VMs. How come we have to reboot the whole PRTG probe for this? Its obvious that the PRTG Probe should detect such thing and act so we dont have to reboot the system. I'm a missing something here? :)


Sep, 2020 - Permalink