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

PRTG Probe service won't start

Votes:

0

I've got PRTG running on Server 2016.

Both core and probe service run on this box. Core is running fine and the web interfaces launches etc.

On the 15th the core and probe service restarted (for no obvious reason? This is something that happens occasionally, I don't think it was an update and the server itself didn't restart).

Anyway, after the core service successfully started I just get the following from the Probe service:

Error		15/05/2018 12:13:12	PRTGProbeService	0	None  
                Service failed on start: Access violation at address 00B6878C in module 'PRTG Probe.exe'. Read of address 00000074
Error		15/05/2018 12:13:12	PRTGProbeService	0	None
                Can not start probe: Could not load SSL library.

This continues after rebooting the server itself.

Looking into it a bit further the restart on the 15th indicated 5 days uptime. The last Windows update was installed on the 10th so I'm guessing something there has caused me problems, however the patch notes don't offer anything obvious that might be causing the problem.

Any thoughts on how best to proceed?

probe prtg service

Created on May 16, 2018 9:21:42 AM

Last change on May 16, 2018 11:43:00 AM by Dariusz Gorka [Paessler Support]



6 Replies

Votes:

0

Hi there,

The PRTG service might got updated. To avoid any issues with third party tools or antivirus systems please install the latest update from PRTG manually again. To manually update your core server, download the installer from the following URL and install it on top of your currently installed version:

Please note that monitoring will be disrupted for a few minutes during the update, remote probes (if any) will automatically be updated after the core server is updated.

Does the issue persist afterwards?

Best regards.

Created on May 16, 2018 11:45:06 AM by Dariusz Gorka [Paessler Support]



Votes:

0

Great, thank you thats working again. I was hoping to avoid a re-install but if i'd realised it was that straight forward I'd have just got on with it!

Thanks for your help.

Created on May 16, 2018 12:11:56 PM



Votes:

1

Since last reboot I get this error message:

Ticket #173: Caution! Your monitoring is interrupted because the core server cannot accept incoming probe connections

Opened by PRTG System Administrator Latest Comments: Your monitoring is interrupted until this issue is resolved: Could not load key, check password. error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch

Tried to reinstall, no success.

Created on Jul 9, 2018 2:50:55 PM



Votes:

0

Hi there,

Do you use any custom certificates for PRTG? Please check that all files are available in the "C:\Program Files (x86)\PRTG Network Monitor\cert\"-folder:

  • dh.pem
  • openssl.cnf
  • prtg.crt
  • prtg.key
  • root.pem

    Best regards.

Created on Jul 10, 2018 8:04:39 AM by Dariusz Gorka [Paessler Support]



Votes:

0

I'm also suddenly getting this one: Caution! Your monitoring is interrupted because the core server cannot accept incoming probe connections

Created on Feb 18, 2019 4:11:18 AM



Votes:

0

Hi there,

Please check the settings under "Setup > System Administration > Core & Probes" to make sure that PRTG allows Probe Connections.

Best regards

Created on Feb 18, 2019 8:52:01 AM by Dariusz Gorka [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.