Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 7039 Source: ServiceControlManager

Level
Description
A service process other than the one launched by the Service Control Manager connected when starting the <service> service. The Service Control Manager launched process <PID 1> and process <PID 2> connected instead.

Note that if this service is configured to start under a debugger, this behavior is expected.
Comments
 
As per Symantec: "The Windows Event ID 7039 reports, "A service process other than the one launched by the Service Control Manager connected when starting the VERITAS Private Branch Exchange service. The Service Control Manager launched process 4068 and process 512 connected instead. Note that if this service is configured to start under a debugger, this behavior is expected."
This behavior is expected and can be safely ignored. The message is generated as a result of the way the PBX service was implemented. The PBX binary is not written as a pure Windows service. Instead, when the Service Control Manager starts the service, it launches a batch file that in turn starts the processes". See the link to "Symantec Support Document ID: 286761" for details.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.

Read more...

 

Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.

Read more...