Backup exec services will not start
Hi,
I have a windows server 2003 SP2 running Symantec Backup Exec 10d for Windows Server, with HP Storage Works library and tape tools version 4.1 and Veritas v 8.5.
When I go to open my Symantec backup exec 10d for windows I immediately get a pop "connect to media server". The local administrator credentials do not seem to work but I know they are right as im logged on the system with them. The backup exec services on (mysevername) stopped. I restart all services but receive a message "an error sarting the service backup exec job engine, the dependency service or group failed to start".
I ensured all the backup exec services, mssql$bkupexec and Sqlagent$bkupexec service were logged on with the local account. The services still will not restart. I also tried to create a new AD Account called nabackup and added it to my domain admin group, i then changed the service logon for backup exec and also within each service. This still did not allow me to restart the services.
This server used to be on a different domain but was moved over a few months back. Is it possible that only now I am seeing the issue from this change? Is this issue all revolved around permissions or could it be hardware?
I am not sure what I can try at this point, is my next step reinstalling? If so, do I reinstall backup exec 10d for windows and then also HP Storage works library and tape tools and veritas?
Any info is great,
Thank You
Jamie
Comments
Try this: When you get
Try this: When you get "connect to media server" prompt, click on services credentials and provide the correct domain name and user account with administrator privileges and its password. Once done, try restarting services. If this does not help, check event viewer for messages on "device and media service" or "backup exec server" service.
Please mark it a solution, if this is useful.
Thanks
Solution from Symantec Support
Hi,
Thanks for the reply. I was able to get support on the line. The final resolution was that the prefirstrun in registry wasnt pointing to outlook anymore, once we renamed prefirstrun entry to prefirstrun.old and restarted all the services everything came back up.
Thanks
Jamie
f
f
Would you like to reply?
Login or Register to post your comment.