Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

A service process other than the one launched by the Service Control Manager connected when starting the Backup Exec Remote Agent for Windows service

Created: 23 Apr 2013 • Updated: 30 Apr 2013 | 6 comments
This issue has been solved. See solution.

We have just started having this problem on a number of servers when they are rebooted. The Backup exec service fails to start and the only error message in the server logs is:)`

"Event Type:    Warning
Event Source:    Service Control Manager
Event Category:    None
Event ID:    7039
Date:        24/04/2013
Time:        7:58:13 AM
User:        N/A
Computer:    X.Y.local
Description:
A service process other than the one launched by the Service Control Manager connected when starting the Backup Exec Remote Agent for Windows service.  The Service Control Manager launched process 1456 and process 1420 connected instead.

  Note that if this service is configured to start under a debugger, this behavior is expected.

The only event which could have any bearing on this is that all the Patch Tuesday patches for April were installed. I have also installed the  replacement patch for KB2840149. However installing this did not solve the problem.

Has anyone else come across this problem?

 

regards

G:)

Operating Systems:

Comments 6 CommentsJump to latest comment

VJware's picture

Which processes were corresponding to PIDs 1456 & 1420 ?

And if you attempt to start each service manually, which service fails to start ?

woofphil's picture

I will get back to you tomorrow re processes, but the only automatic service which did not start automatically at boot up was the BE agent service and despite the warning message in event logs, it started OK manually.

regards,

G :)

woofphil's picture

I replied to this, but it appears to have got lost in the ether.

On checking the relevant processes running neither of the ones which are mentioned in the logs after bootup of affected servers are running.

The Backup exec agent which fails to start at bootup, starts manually. It must however be started manually at each successive boot.

 

regards

G:)

VJware's picture

Set the Remote Agent service (and maybe the Device & Media service as well) to Delayed Start.

SOLUTION
woofphil's picture

Thanks VJWare :)
I will try that and see how it goes. It is a mystery though as to why it suddenly started happening and only happens with a few servers. Nothing different has changed on these servers, compared to the rest of our servers.
Stay tuned for the next exciting update *grin*
regards
G:)

woofphil's picture

Thanks VJWare, that did the trick:)

Why it has happened will just have to remain one of those untold mysteries *grin*

regards

G:)