After an autodiscovery of a windows server, a handful of sensors are reporting "wmi - class not specified".

What is this error?

Article Comments

Could you please elucidate? What precise WMI sensors are returning this message? What Windows are you running on the PRTG server and what Windows is running on the target machine(s)? Are there any relevant entries in the auto-discovery log file?


Jan, 2013 - Permalink

I can elucidate on my problem. I created a new auto discovery group to implement template based devices, while still keeping the older groups active/not paused or deleted. Basically both groups/devices have the same type of WMI sensors but the new template based auto discovery group's WMI sensors are showing "Class not specified". While the same exact WMI sensor on the same device in the old group is still showing up. I did not want to delete the devices from the previous, non auto discovery group until I can get the WMI problem on the devices in the new group resolved.


Feb, 2013 - Permalink

Do the sensors in case have a "Write to disk" option within the sensor settings? If so, could you please turn that on and forward us the results to support@paessler.com, refering to this knowledge base thread?


Mar, 2013 - Permalink

Hello Patrick,

Looking under settings I do not see an option to write to disk. Could you tell me one that does have it and I will see if it has the same issue. If so I can collect the data for you. Thank you.

-Justin


Mar, 2013 - Permalink

Please forward us an email to support@paessler.com refering to this thread. Please let us know what precise WMI sensor types are showing this issue.


Mar, 2013 - Permalink

Hello Patrick,

I think I found the problem. The WMI sensors in the template were created with a previous version of PRTG, which version I am not quite sure. Once I removed them and added sensors from the current version the problem disappeared. One example sensor would be the "SMTP Server: Local Queue Length SMTP" (Exchange 2003) sensor. The template contained that sensor but it was labeled "SMTP Server/Local Queue Length SMTP". Notice the slash after SMTP Server. When that sensor was added manually it did not have a slash, it contains a colon in it's place. As I stated earlier both sensors are now working as expected. For reference the other sensor was MSExchangeIS\RPC Requests (Exchange 2003). As you can see it contains the slash, while the new sensor has a colon. Thank you.


Mar, 2013 - Permalink