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

All sensors turns gray spontaneously after last upgrade in july 2018

Votes:

0

After the upgrade in July 2018 we encounter spontaneously a problem with the sensors. Most of them turned gray and in the eventvwr we see this error occure for every sensor: Log Name: System Source: Service Control Manager Date: 3-8-2018 6:31:48 Event ID: 7011 Task Category: None Level: Error Keywords: Classic User: N/A Computer: V31000350.D40.tes.local Description: A timeout (30000 milliseconds) was reached while waiting for a transaction response from the PRTGProbeService service. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" /> <EventID Qualifiers="49152">7011</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8080000000000000</Keywords> <TimeCreated SystemTime="2018-08-03T04:31:48.881964400Z" /> <EventRecordID>139857</EventRecordID> <Correlation /> <Execution ProcessID="612" ThreadID="4052" /> <Channel>System</Channel> <Computer>V31000350.D40.tes.local</Computer> <Security /> </System> <EventData> <Data Name="param1">30000</Data> <Data Name="param2">PRTGProbeService</Data> </EventData> </Event> -------------------- After the restart of the prtgprobeservice everthing sensor responses and turn green...

7011 error prtgprobeservice

Created on Aug 3, 2018 5:46:59 AM



4 Replies

Votes:

0

Hello Marinus,

Are you referring to updating PRTG or did you install latest Windows updates (also)? In any case, please send us logs using "Setup | Contact Support" and mention this knowledgebase thread in the ticket text as well.

Kind regards,

Erhard

Created on Aug 3, 2018 10:10:36 AM by Erhard Mikulik [Paessler Support]



Votes:

0

Windows update were installed on the 24st of July and the first problems occurred 26 July 18:43u. A stop/start of the service resolves the problem, but most of the time within 24 hours it happens again. I just made the "ticket" by Contact Support option.

Created on Aug 3, 2018 11:38:34 AM



Votes:

0

Cause is a lack of Memory, because of the Dynamic memory setting in HyperV.

Created on Aug 8, 2018 7:32:12 AM



Votes:

0

Hello Marinus,

Right, memory should be fixed instead on dynamically allocated. I think you also have support case open with a colleague of mine, right?

Kind regards,

Erhard

Created on Aug 8, 2018 7:44:21 AM by Erhard Mikulik [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.