asked on

Backup Exec fails with error E00084AF

Hello Gurus,

I have seen plenty of posts regarding this same error but cannot seem to see one that quite fits our environment. We do not have exchange on this server or sql server . I am trying to run a full backup on the server to LTO4 tapes. This error conditions persists whether I try running a full backup of the server or a drive or a few directories. I have removed and re-installed backup exec. I have removed all tape library drivers and tested it using A) symantec drivers and B) the manufacturer's drivers.....error condition persists.

We have a Windows Server 2003 R2 (64 Bit)
Symantec Backup Exec 12.5 is installed on the server.

Dell Md3000 disk array attached to the server
PowerVault TL4000 tape library (LTO4 and 48 slots)

All backups fail with error code E00084Af

Error category : Job ErrorsError : e00084af - The directory or file was not found, or could not be accessed.
For additional information regarding this error refer to link V-79-57344-33967

Rodney Barnhardt

You mentioned reinstalling. Have you been backing up your catalogs and databases or just re-createing your jobs? If you haven't been recreating, have you tried new jobs?

hockeyhalloffame

ASKER

Hello,

This is a new installation. Until this issue is resolved, I am creating new backup jobs on each on my tests.

Thank you

Rodney Barnhardt

Are you using an account with domain privileges? If you are using local system, then that could be the problem. Also, are the files you are backing up on the same server as BE, or are they on another server? If they are on another server, do you have the remote agent license installed?

hockeyhalloffame

ASKER

For my tests, I am using the administrator account. All files selected for th ebackup job are on the server as Be 12.5.

Rodney Barnhardt

Was there some change were the jobs were working, then stopped working?

hockeyhalloffame

ASKER

This is a new installation.

Rodney Barnhardt

Are you using the AOFO on your server? There are known issues with the AOFO creating snapshots so large that the drive temporarily fills up. Have you also checked your event viewer?

hockeyhalloffame

ASKER

I have performed test backup jobs with and without AOFO. Both fail with the same error code. The event viewer was something I did not think of looking into. Upon going through it, there are no backup exec related errors in there.

ASKER CERTIFIED SOLUTION

Rodney Barnhardt

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

hockeyhalloffame

ASKER

In my case, this is what appears to make it return the E00084AF error code.

Backup- C: Directory WINDOWS\assembly\GAC_MSIL\IEExecRemote\2.0.0.0__b03f5f7f11d50a3a\ was not found, or could not be accessed.

It appears to be the same directory for all of my test backup jobs whether I ran a full server backup or selective directories/files.

hockeyhalloffame

ASKER

That directory appears as the cause of the error whether it is pasrt of the backup selection or not. Any idea what it is?

SOLUTION

Rodney Barnhardt

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

hockeyhalloffame

ASKER

I have deleted the b03f5f7f11d50a3a key from the c:\windows\assembly directory and re-submitted a backup that previously failed. The backup completed normally.

I have now submitted a full backup of the server and the attached disk array. There is approx 8 Terabytes of data.
I will update this post once it completes one way or another.

hockeyhalloffame

ASKER

The full server backup completed moments ago. It completed successfully! All I did is delete the b03f5f7f11d50a3a key from the c:\windows\assembly directory .

Symantec support was not very helpful in providing and tangible explanation but I am happy backups are functionning normally. If anybody can shed some light to this mystery, please share.

Thank you

hockeyhalloffame

ASKER

I don't know why exactly it now works but it works.

Rodney Barnhardt

Glad it is working. Did you by chance check any permissions on the file or directory before you deleted it? If it was some type of encrypted key, that may have been the problem.

hockeyhalloffame

ASKER

Strangely, It did not allow me to view permissions on it although I was using the administrative log-in.

Rodney Barnhardt

Sounds like it was some type of permission problem on that file.

hockeyhalloffame

ASKER

It may have been but I was using the administrative account. If it was a permission issue, why did it allow me to delete the key but it did not allow BE to save it to tape. Both operations were using the same account.

Rodney Barnhardt

Not sure, but if it wouldn't let you view the permissions, that sounds like security. I guess you could have tried to take ownership of the file.

hockeyhalloffame

ASKER

True. Should have tried that too.

ratherby

The permission issue was likely due to the folder being a junction point instead of a normal directory. Opening a command prompt in the WINDOWS\assembly\GAC_MSIL\IEExecRemote and issuing the DIR command would reveal that 2.0.0.0__b03f5f7f11d50a3a was type JUNCTION instead of DIR.