Backup Exec 12.5 "Directory was not found or cannot be accessed"

I have a customer running SBS 2008 and Backup Exec 12.5. Backups have been working fine until recently, when they have been randomly failing with error code E00084AF.

When I look at the error log for the job, I see something like:-

Directory Users\FolderRedirections\janet\Desktop\ADCD\COMMON\ was not found, or could not be accessed.

None of the files or subdirectories contained within will be backed up.

Then all folders after janet in Users\FolderRedirections also fail with the same error.

It's not always the same folder that fails first, and it's not always in Users\FolderRedirections either.

The only thing that has taken place on the server are the regular Windows updates and AV definitions.

There is a batch file which stops the AV scan prior to the backup starting, and another batch file the restarts the AV after the backup has finished.

The corresponding event log error is:-

Log Name:      Application
Source:        Backup Exec
Date:          05/09/2013 01:12:41
Event ID:      34113
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      FTSRV05.ft.local
Backup Exec Alert: Job Failed
(Server: "FTSRV05") (Job: "Backup 00001") Backup 00001 -- The job failed with the following error: The directory or file was not found, or could not be accessed.

 For more information, click the following link:
Event Xml:
<Event xmlns="">
    <Provider Name="Backup Exec" />
    <EventID Qualifiers="8192">34113</EventID>
    <TimeCreated SystemTime="2013-09-05T00:12:41.000Z" />
    <Security />
    <Data>Backup Exec Alert: Job Failed
(Server: "FTSRV05") (Job: "Backup 00001") Backup 00001 -- The job failed with the following error: The directory or file was not found, or could not be accessed.
LVL 17
Chris MillardAsked:
Who is Participating?
Chris MillardConnect With a Mentor Author Commented:
OK - I've managed to resolve this by simply creating a new backup job!
Pradeep DubeyConsultantCommented:
Gary ColtharpSr. Systems EngineerCommented:
I am going to assume you have checked the paths and that they are valid so it should not have failed for this reason. If this assumption is incorrect, please do so.

Is the failure always on the same user? You said different folders but did not indicate if it was jumping around the user base.

Have you checked permsissions to make sure they are correct? (compare to a non failing user)

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Chris MillardAuthor Commented:
The paths are indeed valid, and so far, it's always been a different user that it fails on, and of course once it has failed on one user, it automatically fails on the remaining users.
Chris MillardAuthor Commented:
Any more ideas on this? The backups are still failing every day due to this issue, and there is no one particular folder that is causing the issue.
Chris MillardAuthor Commented:
I managed to resolve my own issue by deleting the existing job and creating a new one from scratch.
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.