Auto-discovery error 106

8/10/2016 1:44:13 PM: Autodiscovery Started; Device ID: 15398
8/10/2016 1:44:13 PM: Device Templates; Device ID: 15398; Selected: 3
8/10/2016 1:44:13 PM: Template Loaded; Device ID: 15398; Name: Windows (via Remote Powershell)
8/10/2016 1:44:15 PM: Template Check; Device ID: 15398; Check ID: ping; FOUND
8/10/2016 1:44:15 PM: Template Assigned; Device ID: 15398; Name: Windows (via Remote Powershell)
8/10/2016 1:44:30 PM: Template Check; Device ID: 15398; Check ID: updatecheck; FOUND
8/10/2016 1:44:30 PM: Template Loaded; Device ID: 15398; Name: Hyper V Host Server
8/10/2016 1:44:35 PM: Template Check; Device ID: 15398; Check ID: wmi; ERROR: 106
8/10/2016 1:44:35 PM: Template Loaded; Device ID: 15398; Name: Windows (Detailed via WMI)

Hello,

Are you able to add any WMI sensors manually to this device (ID 15398)?

Please also check if this device has necessary Windows credentials (you can check this in the device settings, as well as in the settings of the parent device group and the probe if the settings are inherited).

Aug, 2016 - Permalink

Yes I can add them manually. I just verified I can add "WMI Free Disk Space (Multi Drive)" manually.

Aug, 2016 - Permalink

Hello,

We will need some more information and log files from your PRTG. Please open a support ticket so we will continue troubleshooting there. Please refer to this KB article in the ticket.

Thank you

Aug, 2016 - Permalink

Hi, did you solve this problem?

I think, I have a same issue.

WMI Service Sensor works fine on the Device, but Auto-Discover and System Information doesnt work. (Error 106)

from the Auto Discovery Debug Log.log :

30.01.2018 01:08:31: Template Loaded; Device ID: 7062; Name: Windows (via WMI)

30.01.2018 01:08:32: Template Check; Device ID: 7062; Check ID: wmi; ERROR: 106

Jan, 2018 - Permalink

Hi Dieter,

When this happens, this is usually an indication that the device in question responds slowly to WMI queries. When adding sensors manually and during sensor operation itself there are longer timeouts in place, while during auto-discovery, the preliminary check whether or not WMI is available is more "aggressive", not waiting that long for a response.

You can disable this "WMI check" directly in the template file:

• Templates are located in PRTG's installation path in subfolder devicetemplates.
• Open the template in question with a text editor (please don't open it with Word or something like that).
• For every WMI sensor you will find a line that looks like this: <create displayname="CPU Load" id="wmiprocessorsensor" kind="wmiprocessor" requires="wmi">
• Change requires="wmi" to requires="ping" in each of those lines, this will effectively disable the WMI preliminary check for those sensors.

It makes sense to do this with templates that you've created yourself. Otherwise chances are that the changes will be reverted with a PRTG update when being performed on the default templates that come with PRTG.

Kind regards,

Erhard

Jan, 2018 - Permalink