What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Sensors problems after update 16.1.21.1692

Votes:

0

Hello,

We have same problems with multiples sensors after update in 16.1.21.1692 version:

- 80041017: The query was not syntactically valid.

- WMI: 80041017: The query was not syntactically valid.- Remarque : la version du système d'exploitation de l'ordinateur n'a pas pu être identifiée, il se peut que WMI ne fonctionne pas correctement. -- PerfCounter: The specified counter path could not be interpreted. (erreur de compteur de performance 0xC0000BC4)

- 80041032: An asynchronous process has been canceled internally or by the user. Note that due to the timing and nature of the asynchronous operation the operation may not have been truly canceled.- Remarque : la version du système d'exploitation de l'ordinateur n'a pas pu être identifiée, il se peut que WMI ne fonctionne pas correctement.

- 8004106C: Windows XP: WMI is taking up too much memory. This could be caused either by low memory availability or excessive memory consumption by WMI.- Remarque : la version du système d'exploitation de l'ordinateur n'a pas pu être identifiée, il se peut que WMI ne fonctionne pas correctement.

We have updated only PRTG, nothing other applications has changed.

We've made already restarted the PRTG server.

An idea?

Thanks

sensor update wmi

Created on Feb 17, 2016 9:11:30 AM



7 Replies

Votes:

0

Hi,
could you please update to the most recent version and see if the issue persists?
Best regards

Created on Feb 19, 2016 2:47:08 PM by Konstantin Wolff [Paessler Support]



Votes:

0

Hi,

I have updated to 16.1.22.2012 version, but this problem is more present :(

An other idea?

Thanks

Created on Feb 22, 2016 9:07:30 AM



Votes:

0

Which specific sensors have these problems?

Created on Feb 22, 2016 11:53:23 AM by Stephan Linke [Paessler Support]



Votes:

0

With WMI sensors

On a same server:

- Sensor HDD Free space - Sensor monitoring service

On a other server:

- Sensor HDD Free space - Sensor monitoring service - Sensor Sql server - Sensor free Memory

Other server:

- Sensor CPU monitoring - Sensor monitoring service

Thanks

Created on Feb 22, 2016 12:04:40 PM



Votes:

0

Would it be possible to migrate those sensors to their SNMP equivalents? Doesn't seem like much work, considering the amount of sensors :)

Created on Feb 23, 2016 9:47:39 AM by Stephan Linke [Paessler Support]



Votes:

0

Hi,

We have wmi sensors Service Windows, Doesn't exist in SNMP.

We have upgrade this PRTG Server to Windows 2012R2 => this problem is still present :(

Other idea?

Thanks

Created on Feb 29, 2016 12:57:51 PM



Votes:

0

Windows services can also be monitored via SNMP using the SNMP Windows Service Sensor. The only caveat is that it doesn't restart the service once it's down. But this can also be configured in the service properties itself more granular (PRTG only tries to restart the service once).

Created on Mar 1, 2016 6:34:02 AM by Stephan Linke [Paessler Support]

Last change on Sep 4, 2019 10:44:20 AM by Felix Saure [Paessler Support]




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.