We just for a license and upgraded to 23.2.84.1566+

I'm having issues getting the WMI Event Log sensor set up.

I continually get the error

"Could not create the WMI Event Log sensor on device <serverName>.

The meta-scan did not return any valid results. Check if the sensor supports the device. (code:PE069)"

I've followewd these pages without a change in results.

https://helpdesk.paessler.com/en/support/solutions/articles/76000062954-my-wmi-sensors-don-t-work-what-can-i-do https://helpdesk.paessler.com/en/support/solutions/articles/89832-wmi-event-log-sensor-does-not-show-all-logfiles#reply-317822 https://docs.datadoghq.com/integrations/faq/how-to-add-event-log-files-to-the-win32-ntlogevent-wmi-class/ https://girl-germs.com/?p=1538

I can connect to the remote WMI via Powershell using the same AD account.

I searched for the PE codes and see that PE069 is deprecated. https://https://helpdesk.paessler.com/en/support/solutions/articles/76000063696

Any advice would be appreciated.

Article Comments

Hello,

For testing purposes you can use WMI Tester on the PRTG Probe system and test the following query:

SELECT Name, LogFilename, Filename, NumberOfRecords FROM Win32_NTEventlogFile

Do you get any results here?


Jun, 2023 - Permalink

I get no results. WMI Tester and the Security event viewer show no errors.

The Microsoft > Windows > WMI-Activity > Operational log shows this entry

"MS_NT_EVENTLOG_PROVIDER provider started with result code 0x0. HostProcess = wmiprvse.exe; ProcessID = 5548; ProviderPath = %systemroot%\system32\wbem\ntevt.dll"


Jun, 2023 - Permalink

As long as we do not receive any results from the target device via WMI, it's not possible to monitor it and add the sensor in PRTG. The following article might help here: https://helpdesk.paessler.com/en/support/solutions/articles/3713


Jun, 2023 - Permalink