"Could not start the Backup Exec Remote Agent for Windows Servers service on local Computer. Error 1069: The service did not start due to a login failure."
Posted on 2008-06-11
"Could not start the Backup Exec Remote Agent for Windows Servers service on local Computer. Error 1069: The service did not start due to a login failure." Infact all of the Backup Exec services gave the error above except with their corresponding service name.
Here is a run down of what happened:
Our main fiber switch went down. We switched it out and the netwrok came back up. However, now Backup Exec won't start. When you execute the application it asks for the admin password. When the admin password is entered it rejects the password. I couldn't start the Backup Exec services any way that I tried. A server reboot didn't solve the problem either. The only way around it was to change the Backup Exec credentials by changing (really reentering) the admin username, password, and domain name. After doing this I was able to force most of the Backup Exec services to start. The ones that did not start and will not start are the above mentioned Remote Agent and the Backup Exec Job Engine. Now after changing the credentials I am able to execute/open the Backup Exec app. The job history shows past jobs and the scheduled job still has the correct name. Even the email addresses to alert of a failed job are present and correct. It seems that our "company info" is still present except the actual job selections are not there any more under our daily backup job. Infact I can't seem to even create a new job and select the files/folders I need to backup. So our daily backup job seems to have been deleted but as I mentioned the other "company info" is still there. How can I start the needed services? How can I get that old job and its selections back? What could have caused this? How can I create a new job with the old selections?