• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4046
  • Last Modified:

Backup Exec 2010 error e00084af during System State backup

We have recently updated our own Backup Exec installation to 2010.  The update process was to uninstall v10D and then install Backup Exec 2010 afresh.  The same user credentials are being used for the backup jobs and all but the System State is being backed up successfully.

When backing up the System State the job always gets an error: "e00084af - The directory or file was not found, or could not be accessed."

All three possibilities in http://seer.entsupport.symantec.com/docs/326836.htm have been ruled out.  The System State obviously exists on the server & is not a "missing directory."  The credentials in use are correct (they're being used for the rest of the backup & working) and the system state backup does not work if the user credentials are removed either.  TCP Port 10,000 is definitely being listened to by beremote.exe (confirmed via "netstat -ano" and task manager with PID column).
0
Barthax
Asked:
Barthax
  • 8
  • 3
1 Solution
 
ConchCrawlCommented:
I do have a question are you using sbs 2008 or sbs 2003?
Are tyring to backup the server that BE is installed on or to a remote computer with an agent? or some other scenario?
Please elaborate.
0
 
BarthaxAuthor Commented:
The install of Backup Exec 2010 is directly on the SBS 2003 server and it is the System State of that server which is failing to be backed up.
0
 
dovidmichelCommented:
Check Event Viewer System and Application logs.
Enable debug and recreate the problem.
http://seer.entsupport.symantec.com/docs/254212.htm
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
BarthaxAuthor Commented:
Simple enough with & without debug.  A single error occurs (server name changed):

Event Type:      Error
Event Source:      Backup Exec
Event Category:      None
Event ID:      34113
Date:            25/03/2010
Time:            15:49:58
User:            N/A
Computer:      <the sever>
Description:
Backup Exec Alert: Job Failed
(Server: "<the sever>") (Job: "Backup To Disc test") Backup To Disc test -- The job failed with the following error: Failed to log on to Microsoft Windows.

Ensure that your logon credentials are correctly entered and that they meet the following minimum requirements to log on to a Windows computer:

   - The credentials used are a member of the Backup Operators group.
   - For Windows Vista/2008 and later, the credentials have the Log on as a batch job privilege.

Additional privileges may be required to access resources on the Windows computer.
 

 For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
0
 
BarthaxAuthor Commented:
Finally got this working with an account which is used to interactively log into the server.  The primary difference seems to be the interactive log on & membership of the Server Operators group.  Gonna try to whittle this one off my list today.
0
 
BarthaxAuthor Commented:
Definitely not group based, so am resorting to comparing these two accounts via RSOP.
0
 
BarthaxAuthor Commented:
I can't explain it.  Both accounts seem to be inheriting the same set of options regarding logging in locally via the local Administrators group and Backup Operators.  I'll just backup the System State as the other user, job done.
0
 
ConchCrawlCommented:
By default when you install BE it should create the BE admin to login interactively, if this is just a small network I would just use the regular admin account you use for the domain and be done with it.
0
 
BarthaxAuthor Commented:
ConchCrawl: hehe, that's what I mentioned doing in the previous comment (though it isn't clear, I grant you). :)
0
 
ConchCrawlCommented:
ok, I see what you mean now, but I was trying to make sure of what you were doing and clarify what I would do :-). Never did like using separate accounts with BE always was problematic for me.
One other thing, when you run the connectivity test in BE after supplying the credentials for the backup job what is the result?
Hope this helps
0
 
BarthaxAuthor Commented:
The connectivity tests always come back with successful - then the job result may be different. :(
0
 
BarthaxAuthor Commented:
On three occasions I have accepted my own answer.  On three occasions the question has not been closed.  Could you force acceptance of answer ID:28978260 please.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 8
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now