New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Templates stopped working after an update

Votes:

0

Your Vote:

Up

Down

Hello everyone,

So, We've updated our PRTG to verison 20.1.57.1745+, everything was working until we've added new server using template and the one thing it is adding is ping, we have created a new template, same thing. We've tried pre-made ones and still was getting just ping. Checked the autodiscover logs and this is what they were saying.

INFO TId 628 CoreAutoDiscovery> Device ID: 4868 Name: <server> Host: <server> INFO TId 628 CoreAutoDiscovery> Device Templates; Device ID: 4868; Selected: 1 INFO TId 628 CoreAutoDiscovery> Template Loaded; Device ID: 4868; Name: <Template> INFO TId 628 CoreAutoDiscovery> Template Check; Device ID: 4868; Check ID: ping; FOUND INFO TId 628 CoreAutoDiscovery> Template Assigned; Device ID: 4868; Name: CCSO Template INFO TId 628 CoreAutoDiscovery> Sensor Created; Device ID: 4868; Create ID: {E6F31B41-AC40-40C8-A968-0DF41B65F684}; Sensor ID: 4869; Name: Ping INFO TId 628 CoreAutoDiscovery> Template Check; Device ID: 4868; Check ID: wmi; ERROR: 106ErrorMessage: #O69 INFO TId 628 CoreAutoDiscovery> Autodiscovery Finished: Device ID: 4868; Sensor(s): 1; Templates: <template>

Any ideas?

Sincerely, flyingjet

autodiscovery prtg template wmi

Created on Apr 13, 2020 1:09:52 PM by  ccsoflyingjet (0) 1



5 Replies

Accepted Answer

Votes:

1

Your Vote:

Up

Down

Hello there,

Thank you for your post.

This is probably caused by a bug in the PRTG version you are running. This is fixed in the newest PRTG version 20.1.57.1786. Please update and try the auto discovery again.


Kind regards,
Sasa Ignjatovic, Tech Support Team

Created on Apr 13, 2020 3:26:10 PM by  Sasa Ignjatovic [Paessler Support]



Votes:

0

Your Vote:

Up

Down

Hello Sasa,

When we upgraded we thought it was the newest version, I guess not. When I checked for the update from SETUP menu i did pop up to install it and after that all works good.

Thanks!

Created on Apr 13, 2020 4:25:13 PM by  ccsoflyingjet (0) 1



Votes:

0

Your Vote:

Up

Down

Problems not resolved until the latest version(20.2.58.1629). Downgrade version 20.1.55.1775. On this version, everything works correctly.

Created on Apr 22, 2020 6:30:59 PM by  slamich (1) 1



Votes:

0

Your Vote:

Up

Down

I suspect that the fix Wmi sensors WMI sensors now show an according error message (PE069) if they do not find any items to monitor on the target device during the meta-scan on sensor creation. in version 20.1.57.1745 caused such a failure. Something does not work correctly in the module for checking WMI objects.

Created on Apr 22, 2020 6:36:08 PM by  slamich (1) 1



Votes:

0

Your Vote:

Up

Down

Hello,

Adding WMI sensors using the Auto-Discovery should work again in the latest version. Are you able to add the sensors manually? If so please send us a support bundle containing the log files from PRTG for further troubleshooting. For this, please open the support dialog "Contact Support" in the lower right corner of the WebUI. Please refer to this KB-topic.

Created on Apr 23, 2020 10:14:27 AM by  Timo Dambach [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.