Solved

"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
5
6,942 Views
Last Modified: 2013-12-01
"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?

Thanks.
0
Comment
Question by:level9tech
  • 2
5 Comments
 
LVL 6

Accepted Solution

by:
raptorjb007 earned 500 total points
ID: 21765603
It sounds like the password for the account the BackupExec services were using changed, when you rebooted the services could not restart because they are trying to authenticate with an old password. You will not be able to log into the interface unless the services are started.

Typically, the BackupExec services can all run as local system, including the remote agent. However you have to be sure that you have the proper credentials set for the admin account in the BackupExec interface under Network->Logon Accounts. If the logon accounts are not configured with valid credentials you will find your jobs will all fail to complete.

So, you should update any BackupExec services running with a domain account with valid credentials and ensure that the logon accounts in BackupExec are updated as well.
0
 
LVL 6

Expert Comment

by:raptorjb007
ID: 21828253
Any luck?
0
 

Expert Comment

by:dcgagne
ID: 22732586
I had the same issue as the author and this advice fixed it. The problem ended up being the domain administrative password had been changed and none of the services would start. Simply typing in the new name at the prompt would not work because none of the services were on. We had to change the credentials, restart BackupExec, and then start the services.

Everything is working properly now.
0
 

Expert Comment

by:saty25
ID: 33868181
I tried by being on backup exec services through services.msc on server where the backup exec is installed. then click on the properties of the backup exec services -> select Logon tab and change the password for related account. this way it worked for me and i can run my backup exec as normal.
0

Featured Post

Google Storage: Standard vs. Nearline vs. Coldline

Google Cloud Storage has a number of classes to choose from. Although there are a lot in common, they vary in price and usage terms. This post explains Google Cloud Storage classes and helps to understand which  one to choose.

Join & Write a Comment

Suggested Solutions

VM backup deduplication is a method of reducing the amount of storage space needed to save VM backups. In most organizations, VMs contain many duplicate copies of data, such as VMs deployed from the same template, VMs with the same OS, or VMs that h…
Microservice architecture adoption brings many advantages, but can add intricacy. Selecting the right orchestration tool is most important for business specific needs.
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

706 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now