Backup Exec 11d 0xe000fe29 - Some jobs fail, not all

We are running a Backup Exec 11d on a Server 2003 box which backs up around 40 servers via remote agents.  We have several different Policies for different devices on our network.  Recently a few servers started failing with the "e000fe29 - Authentication failed on connection to the server. Make sure that the user account has the appropriate permissions and that the password was typed correctly" error.  The strange thing is that I can run the backup job manually and it runs just fine.

I searched for days on this and found some useful articles, none of which worked for me.  

I have verified that the BE service is running under Local System on the remote servers.
The BE Network Account is the same for every device.
The BE Network Account is not disabled

This morning I ran a test run on the jobs that consistently fail, they all succeeded.

Is there a difference between the job running on a schedule as opposed to an admin manually starting it?
LVL 3
thecureisAsked:
Who is Participating?
 
demaitConnect With a Mentor Commented:
For grins, have you tried creating a completely new account in Active Diretory, then going into BE and settting that new account as the Default System Logon account?

0
 
demaitCommented:
Have you tried an uninstall/reinstall of the remote agent on any of the failing servers?
0
 
thecureisAuthor Commented:
Since I can run the backup manually and it runs fine, I do not believe it is the agent that is causing the issue.
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
demaitCommented:
We currently use 12.5. However, in the past when we had 11d, we experienced a similar problem that caused an update to corrupt the agent. The agent would run fine when run manually, but not through the automated process.
0
 
thecureisAuthor Commented:
Hmm, I will try re-installing the agent on a server and see what happens tomorrow.  Sometimes the servers will backup fine and sometimes they get the authentication error.  Is that what happened with you? or did your servers fail everytime when running on a schedule.
0
 
demaitCommented:
We had the same problem. It would work sometimes, but not always. After upgrading to 12.0 the problem went away completley. However, there was a newer version of the Agent that we had installed and it helped in the interim.

One more question for you.. Are these servers running Oracle on them? Oracle can cause some issues for you with the remote agents also.
0
 
thecureisAuthor Commented:
Interesting.  I will re-install the agents on a few today and see if it resolves the issue.  We are not running oracle.
0
 
demaitCommented:
Did you verify the user account is in the services of each of the servers? I do remember an update causing one of the services to return to a default value on the "local services" of the server. After changing it to the preferred user account, that particular problem went away also.
All of the services for Backup Exec should be set to "<domain>\<username>
0
 
thecureisAuthor Commented:
The "Backup Exec Remote Agent..." Service was set to "Local System Account"  All others on the backup server were set to our backup domain user.  
0
 
demaitCommented:
That should be fine.
0
 
thecureisAuthor Commented:
I also read on Symantec's site that the service accounts on the remote computers should be set to Local System.  This is the way all of our servers are set up.  Is this wrong?  The reason for this is so that we do not have to touch each server if/when we change our backup service account password.
0
 
demaitCommented:
No, that's not wrong. Ours are set to the Local System Account also.
0
 
thecureisAuthor Commented:
OK, I will post what happens tomorrow morning.  Thanks.
0
 
thecureisAuthor Commented:
I re-installed the agent on 2 servers and the backups still failed with the same error.
0
 
demaitCommented:
Has there been any type of update to the Network, ie. AD/DNS? Any updates that may have been done recently to the servers with problems? Or have all the servers received the same updates?
0
 
thecureisAuthor Commented:
They all receive the same updates on the same day.  They are all rebooted once a month and are on the same physical network backing up to the same tape library.  I don't see what the difference would be having the backup exec run the job at a certain time as opposed to myself right clicking and selecting to run now.
0
 
demaitCommented:
There should be no difference in the job running manually as compared to running it through automation. Unless someone else has a suggestion, you may have to open a ticket with Symantec (good luck) to determine what can be done.
Sorry I couldn't help any more on this.
0
 
thecureisAuthor Commented:
demait - thanks for the ideas and the help.

After combing through hundreds of backup logs, I have found that on occasion every server fails with that error.  It just seems that the same 10 servers fail more often than the others. I looked through the detailed logs of the 10 servers that fail most often, and they do backup some random nights.

Can anyone shed some light on a possible solution?  It appears that the error is occuring during the initial connection to the servers.  If it was an account issue, I would think that it would happen to every server or at least every time.
0
 
demaitCommented:
thecureis - have you tried deleting and then re-creating the System Logon Account in BE?
http://seer.entsupport.symantec.com/docs/274012.htm
0
 
thecureisAuthor Commented:
Yes I have
0
 
thecureisAuthor Commented:
I will do that and let them run tonight again
0
 
demaitCommented:
Remember to restart the BE services after you set the new System Logon Account in BE.
0
 
thecureisAuthor Commented:
Done, thanks for the reminder.  hopefully this resolves the issue.
0
 
thecureisAuthor Commented:
After creating a new service account (Copied the old on in AD) the backups are running.  After doing a little more digging, I found that our main backup service account keeps getting locked out.  We are using that account for our Backup Exec System Recovery services as well.  Apparently one of the other admins mistyped the password on one of the servers.

Thanks for the help.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.