BE services cannot be started after reboot

[123456]

After we installed BE10, we noticed that a lot of servers have the problem in restarting backup exec job engine service and backup exec server service after the servers reboot. The error logged in the event viewer is event ID 7001, 7009, and 7000. The error shows the service did not respond to the start or control request in a timely fashion. Any suggestion?

[Greg_Walker]

Try opening the properties of the "Backup Exec Server" service and change the logon account to the same account as it is already using.

For some reason this seems to help on one of my media servers.

[123456]

We are using the same account. Any other suggestion? Actucally, BE services can be manually started, which I think eliminate the right's issue. The problem is BE services cannot be restarted after the servers reboot and the error logged in the event view is that the service did not respond to the start or control request in a timely fashion. Only job engine service and server service cannot be started. The rest of the services have no problem to restart after the servers reboot.

[Michael_McKenne]

Did you try error checking and defragmentation. This has worked before for me correcting BE service issues.

[123456]

But the server is still a new server. We are not allowed to do error checking or defragment on the servers. Any other suggestions?

[Dave_Bunye]

What you are experiencing is just a fluke of an operating system trying to start to many processes or programs. As it states, after the services attempt to start, they time out before successfully starting. This is because other services are also starting at the same time. There is no "error" here to fix other than a timing issue.

Aside from hacking the registry for startup values, I would just manually start the services and not worry about it. You could compare servers that have the issue against those which do not and find out the pattern of what software, hardware, or utilities are on the systems with and without the problem.

[Michael_McKenne]

Increasing RAM and CPU would allow services to load faster and not hang.

[Sharvari_Deshmu]

Hello,

Backup Exec user account will have the required permissions to the installation directory.
1) Create a new user on the local machine (or on the remote machine, if the issue is with remote machine's backup). Make newly created user a member of Domain/local Admin group only.
2) Start Backup Exec; create a Logon account with same username and password as that of newly created user
You may refer to following:
-Start Backup Exec
-Select Tools > Wizards > Logon account wizard -Add new logon account, type in the credential for the new account.
-Make this account a common logon account.
-Complete the wizard.
3) Create new backup job by selecting the local (or remote machine) and select this newly created account from window.
If while selecting the local resource (or remote machine) it does not prompt for the credentials then after selecting the remote machine | select "resource credentials" | select existing logon account | click change and select the newly created logon account
You may like to refer to the following technote for more information:
Title : Backup Exec services fail to start and the Event Viewer System log displays Event ID's 7000 and 7001.
URL: http://seer.support.veritas.com/docs/242522.htm


Thanks,

NOTE : If we do not receive your reply within two business days, this post would be marked "assumed answered" and would be moved to "answered questions" pool.