08-27-2012 02:13 AM
We have a Windows Server 2003 Standard 64-bit Server. We deinstalled the old Backup Exec 8.5 version and installed Backup Exec 2010. Everything worked just fine. We then renamed the server (hostname) - still everything fine - jobs ran.
We ran LiveUpdate - funnily, BE 8.5 & 2010 were displayed. We selected just the 2010 and installed all 10 updates. After rebooting the server, the BE services no longer started. We deinstalled and reinstalled BE 2010. Everything fine - but as soon as we run a LiveUpdate and install the updates, BE services no longer start.
Any ideas what the problem could be?
Solved! Go to Solution.
08-27-2012 02:46 AM
...is that account locked out at all?
Otherwise, if you have domain admin rights on your account, use BEutility.exe to change the BESA to use your account as a test and see if it starts up.
The other thing to check is to ensure that any AV running on that server isn't perhaps blocking the BE services,a nd if so, put in exclusions for them.
Thanks!
08-27-2012 02:17 AM
Which BE service is not starting?
Check event viewer for any error related to services.
BE Services should be started in following sequence.
1) SQL server service
2) BE Device and Media service
3) BE Server service
4) BE Job Engine
5) Remote Agent
5) Agent Browser
08-27-2012 02:34 AM
The only BE services which start are "Backup Exec Error Recording Service" and "Backup Exec Remote Agent for Windows Servers". When trying to start any of the services, we get an error 1068 'dependency service or group failed to start'. Event viewer shows nothing.
08-27-2012 02:37 AM
Check the status of "SQL server BKUPEXEC" service and "Workstation" service.
08-27-2012 02:39 AM
All other services are running. The services starting as 'local system' start just fine. The services which start as the 'backup-user' fail - yes, we have tried re-entering the password and changing the login name to 'domain\username' and 'username@domain.local'.
08-27-2012 02:46 AM
...is that account locked out at all?
Otherwise, if you have domain admin rights on your account, use BEutility.exe to change the BESA to use your account as a test and see if it starts up.
The other thing to check is to ensure that any AV running on that server isn't perhaps blocking the BE services,a nd if so, put in exclusions for them.
Thanks!
08-27-2012 03:12 AM
Thanks CraigV. Using BEUtility.exe to change the BESA worked just fine.