New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.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


Error: Metascan Timeout

Votes:

0

Your Vote:

Up

Down

Hi, With new version 16.2.24.3686 I have an error message "Error: Metascan Timeout" when i try to display system information hardware - users - services (not system) Bug or bad settings ? Regard

information prtg system

Created on May 12, 2016 1:42:42 PM by  Yohann Boucher (0) 1



5 Replies

Votes:

0

Your Vote:

Up

Down

Hello,

This is a WMI timeout and occurs if the WMI connection cannot be established for several minutes. Please check your WMI configuration and especially consider the WMI settings on the target computer.

Created on May 13, 2016 12:16:22 PM by  Jochen Greger [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I'd like to add that I started receiving this error when trying to add sensors to an yof my devices. The issue was with the PRTG Core probe and after restarting that server the issue went away.

Created on Jul 12, 2016 1:40:21 AM by  jcrookslakemac (0) 1



Votes:

0

Your Vote:

Up

Down

Hello

This issue has to do something with the new PRTG Release.

Created on Aug 12, 2016 8:05:39 AM by  Tibor Cetl (0) 1



Votes:

0

Your Vote:

Up

Down

Hello Tibor,

Unfortunately we can not confirm that this error message occurs because of a bug in the latest PRTG version. Does restarting the PRTG probe service help to resolve the issue?

Created on Aug 15, 2016 12:10:15 PM by  Jochen Greger [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I've found that if you add a WMI based sensor like Memory or CPU that it can get WMI working again. It's most likely something that gets gummed up with WMI that gets resolved by polling for another metric. Try adding a CPU sensor then delete it. See if that gets the information working.

Created on Sep 9, 2016 4:39:47 PM by  Benjamin Day [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.