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

Service failed to start - access violation at ... PRTG Server.exe



The core server service does not start on one of our prtg installations.

The Core-Server Log looks like this: 18.10.2017 13:07:32 PRTG Network Monitor x64 Core Server starting on "SRV00300" 18.10.2017 13:07:33 Startup: OS: Microsoft Windows Server 2012 R2 Datacenter (6.3 Build 9600), 2 CPUs (Double x64 Model 63 Step 2), code page "Windows-1252", on VMware 18.10.2017 13:07:33 Startup: System Path: C:\Program Files (x86)\PRTG Network Monitor\ 18.10.2017 13:07:33 Startup: Data Path: C:\ProgramData\Paessler\PRTG Network Monitor\ 18.10.2017 13:07:33 Startup: Formatting: dd/MM/yyyy | dddd, d/ MMMM yyyy | hh:mm | hh:mm:ss 18.10.2017 13:07:33 Probe settings: IPs: - Port: 23560 - SSL: -1 18.10.2017 13:07:33 System time zone: (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna 18.10.2017 13:07:33 Memory Manager: NexusMM4 18.10.2017 13:07:33 libeay32.dll= 18.10.2017 13:07:33 ssleay32.dll=

The windows event log contains the following message: The description for Event ID 0 from source PRTGCoreService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Service failed on start: Access violation at address 00000000010285F8 in module 'PRTG Server.exe'. Read of address 0000000000000078

Replacing the configuration file with one from the AutoBackup directory didn't work.

core-server service start-failure

Created on Oct 18, 2017 11:39:56 AM

1 Reply



Did this happen after you tried to do an update?

If so, can you try installing the update again?

Created on Oct 18, 2017 2:17:04 PM by  Benjamin Day [Paessler Support] (1,441) 2 1

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.