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


What does error code PE1114 mean?

Votes:

0

Your Vote:

Up

Down

When using PRTG’s webserver, a popup appears which displays “Lost connection to PRTG server!” and I cannot continue. This error has the code PE1114: URL: /api/public/testlogin.htm failed twice (PE1114, error. )

What does this error mean?

connection core-server disconnected error error-code error-messages pe1114 prtg web-interface

Created on Oct 25, 2013 1:55:26 PM by  Gerald Schoch [Paessler Support]



3 Replies

Accepted Answer

Votes:

0

Your Vote:

Up

Down

This article applies to PRTG Network Monitor 13 or later

Connection Problems: Error Code PE1114

The error code PE1114 indicates a connection timeout error. PE1114 appears when you are connected to PRTG’s web interface but it cannot reach PRTG’s core server anymore. This can be the case, for example, if the core server start is pending at the moment.

Usually the web interface will work again after a short time when the restart is finished. Wait a moment and click on Try Again.

Error PE1114
The Error Message in PRTG's Web Interface


Starting Core Server by Hand

However, if the PRTG core server is currently stopped, for example, after a server reboot and will not come back automatically, start the core server manually in the PRTG Administration Tool:

  • Open the tab Service Start/Stop.
  • If you see the message Service Status: Stopped, restart the core server.
  • Click the button Start Core Server.
  • Wait until Service Status: Running appears.
  • Go back to the PRTG web interface and click on Try Again in the error message.

Created on Oct 25, 2013 2:03:09 PM by  Gerald Schoch [Paessler Support]

Last change on May 7, 2015 2:55:37 PM by  Gerald Schoch [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I had the same error in this moment. But the log of the PRTG server only show the following irregular events:

07.10.2015 12:32:33 Probe Device Probe Health PROBE-Health Warning 165 Items (Open Requests) is above the warning limit of 100 Items

07.10.2015 12:40:31 PROBE-Health Unknown No data since 07.10.2015 12:35:21

07.10.2015 12:41:31 PROBE-Health Down 113 % Delay (Interval Delay WMI) is above the error limit of 100 % Delay. WMI Sensors of this probe can not be scanned in their specified intervals. Try longer intervals or distribute load over probes.

I'm not sure what mean the first entry of log (about Open Requests) because we didn't have any user manipulating the server in that moment.

Created on Oct 7, 2015 6:05:00 PM by  prtgmf (0)



Votes:

0

Your Vote:

Up

Down

Open Requests is not HTTP requests or similar to a server. It is a metric for PRTG itself, about how many sensor requests (to the target devices that you monitor with PRTG) are still open (so the devices have not responded). If you see warnings and errors often about Open Requests, it is a sign that the scanning intervals are too short for your target devices. Please then consider using longer intervals.

Created on Oct 9, 2015 11:20:34 AM by  Torsten Lindner [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.