The problem is probably with the login account which is set to run the backup exec services. You need to ensure that the login details are correct (have you changed the password for the user that you use to run the services) so you can start the services. Once the services have started you'll be able to login to the front end again.

Hello Don,


Please let us knbow if you have tried the earlier provided suggestions? Were these helpful.


============

There is my problem, as I stated I log in and get the services aren't running errors, When I start the services the I get the logon errors, A perfect catch 22!!!

Can I wipe out or reset the passwords or wipe out and reset the Users?

Thanks for your imput

Yes... sorry but that's the whole point! If the services aren't running then you have nothing there to login to, so of course it will fail. When you login to the front end of Backup Exec it has nothing to do really with the services login, what you're logging into is the Backup Exec service, which in your case isn't running. It's certainly not a catch 22 at all, the Windows services couldn't care less about the login details you use to connect to Backup Exec.

Forget about the Backup Exec login, and concentrate on the services, you need to get them to work otherwise nothing else will. In Services what user are the Backup Exec services configured to run as? Eg, go to Administrative Tools, Services, select a Backup Exec service, right click it and select Properties, go into the Log On tab and confirm the login details listed there are correct. Make sure the login details you have configured for each of the services is correct by resetting the password to the one you know if correct for that users account, and if necessary consider resetting the domain login itself in AD if it's not used for anything else, eg it's a backup specific account.

Thanks Keith your first part makes sence. I have 5 BE services available in Services:
Agent Browser, Device & Media, DLO Admin, Remote Agent, Server

I changed all the logons to Local System Account w/desktop interation
(by the way I am not sure what the Desktop interaction means)

Everything is up and running. Thanks so that leaves me with two questions:
1. What is the Desktop Interaction provide me
2. What is the best practice for setting up users

If memory serves Desktop Interaction relates to the permissions required for a service to interact with the desktop, eg popup errors messages, load windows etc, which obviously for something like this is required.

Generally the best rule of thumb is the least amount of privaledges to do what is required, though because of what you're trying to do you'll generally end up using an administrator level user. For some reason I believe that while the Backup Operators group is fine for backups, it doesn't have enough permissions to completely restore of a system. Personally I create a new domain admin user and run the services using that user, it's essentially the same as using the domain administrator, but at least it provides a level of separation, and makes things easier if one or other password needs to be reset.