If you run PRTG Traffic Grapher as a service on your computer you may see Windows Event ID 7039 in your System Event log.
The message is:
A service process other than the one launched by the Service Control Manager connected when starting the PRTG Service service. The Service Control Manager launched process xxx and process yyy connected instead. Note that if this service is configured to start under a debugger, this behavior is expected.
The reason for this message is the license control and code tampering protection mechanism that we use in PRTG Traffic Grapher. Similar to a debugger it uses a second process to monitors the main process. This is the reason why Windows sees a different process ID when PRTG Traffic Grapher is started as a service. So you can ignore Event ID 7039 for PRTG Traffic Grapher, it is expected behaviour.

Neuste Blog-Beiträge von Dirk Paessler

2014-Apr- 8: OpenSSL Heartbleed Bug Vulnerability

2014-Mar- 5: The Future is Mobile: Are You Ready?

2014-Feb-27: Die Zukunft der Netzwerküberwachung ist mobil und virtuell

2014-Feb-25: Critical Security Update Available for PRTG Network Monitor

2013-Jul-16: Introducing Our New Passive Application Performance Sensor

2013-Apr-23: Paessler at VMware Forum 2013

2012-Nov- 7: New Version of PRTG Introduces 64bit Core Server and Other New Features

2012-Jul-13: The WMI Performance Test (2012 Edition)

2012-Jul-10: The Paessler Roadmap

2012-Jul- 3: How We Rate Your Feature Requests

Copyright © 1998 - 2014 Paessler AG