cancel
Showing results for 
Search instead for 
Did you mean: 

Backup exec 10d error 0xe000fe29

andrew_charles
Level 4
Hi Guys,

We are running 2 servers with backupexec 10d on them. they both use the same servie account. The server which backs up our database is running fine. The server which does our system states has all of a sudden started failing with the bellow error. Now the service account is a domain and enterprise admin. It is not locked and the password has not been changed. I was wondering if anyone has seen this error before?

Final error: 0xe000fe29 - Authentication failed on connection to the server. Make sure that the user account has the appropriate permissions and that the password was typed correctly. Final error category: Security Errors

Thanks in Advance.

Charlie
1 ACCEPTED SOLUTION

Accepted Solutions

Hemant_Jain
Level 6
Employee Accredited Certified
It is not the service account, but the logon account whose credentials you need to verify. You can check logon accounts, by going to Network-> Logon accounts on Backup Exec console. Make sure they are same on both the servers. Also, verify the logon account used in "resource credentials" tab in the backup job properties. This logon account must be granted privileges on the target server being backed up. Change password on the logon account, to make sure you are using correct password. Also, ensure that system logon account is present in the logon accounts.

Please mark it a solution, if this is useful.
Thanks

View solution in original post

1 REPLY 1

Hemant_Jain
Level 6
Employee Accredited Certified
It is not the service account, but the logon account whose credentials you need to verify. You can check logon accounts, by going to Network-> Logon accounts on Backup Exec console. Make sure they are same on both the servers. Also, verify the logon account used in "resource credentials" tab in the backup job properties. This logon account must be granted privileges on the target server being backed up. Change password on the logon account, to make sure you are using correct password. Also, ensure that system logon account is present in the logon accounts.

Please mark it a solution, if this is useful.
Thanks