goldylamont
asked on
Backup Exec Error 34113 - directory or file not found
I can't complete even a simple backup job with Veritas Backup Exec 10.0 rev 5484 on Small Business Server 2003 SP1. I have simplified the job to try to copy just one file folder (a few MB in size) from the C: drive. The error I get in the Event Log is:
Error 34113 : The job failed with the following error: The directory or file was not found, or could not be accessed.
Final error: 0xe00084af - The directory or file was not found, or could not be accessed.
I've turned on Veritas debug logging and these are the last few lines:
[5464] 05/17/07 05:04:02 SQL2_CleanUpSnapInfoList called.
[5464] 05/17/07 05:04:02 Status RPC_E_TOO_LATE (0x80010119) returned initializing COM when initializing shadow copy
[5464] 05/17/07 05:04:02 Calling IVssBackupComponents::Gath
[5464] 05/17/07 05:04:03 ...completed IVssBackupComponents::Gath
[5464] 05/17/07 05:04:03 brUtil::brUtil( img ) Constructor
[5464] 05/17/07 05:04:03 Attach to Shadow?Copy?Components
[5464] 05/17/07 05:04:03 Informational status CODE (0x00000002) returned calling FindFirstFile for C:\WINDOWS\system32\perf?0
[5464] 05/17/07 05:04:03 Status FS_NOT_FOUND (0xE00084AF) returned determining if Writer SqlServerWriter should be displayed when generating logical directory tree
[5464] 05/17/07 05:04:03 Warning status -536836945 calling FS_EnumSpecFiles for device Shadow?Copy?Components in LP_ENV::LoadEnumSpecFileEx
[5464] 05/17/07 05:04:03 Detach from Shadow?Copy?Components
[5464] 05/17/07 05:04:03 brUtil::brUtil Destructor
[5464] 05/17/07 05:04:03 Status 0xE00084AF calling LoadEnumSpecFileExcludes in LP_DoBackup
[5464] 05/17/07 05:04:03 LP_ENV::MsgError: error 0xe00084af processing object <Unknown>
[5464] 05/17/07 05:04:03 Job Stop(0) - Thu May 17 05:04:03 2007
[5464] 05/17/07 05:04:03 ERROR: ndmpdDataAbort: invalid state to process abort request.
any help would be appreciated
Error 34113 : The job failed with the following error: The directory or file was not found, or could not be accessed.
Final error: 0xe00084af - The directory or file was not found, or could not be accessed.
I've turned on Veritas debug logging and these are the last few lines:
[5464] 05/17/07 05:04:02 SQL2_CleanUpSnapInfoList called.
[5464] 05/17/07 05:04:02 Status RPC_E_TOO_LATE (0x80010119) returned initializing COM when initializing shadow copy
[5464] 05/17/07 05:04:02 Calling IVssBackupComponents::Gath
[5464] 05/17/07 05:04:03 ...completed IVssBackupComponents::Gath
[5464] 05/17/07 05:04:03 brUtil::brUtil( img ) Constructor
[5464] 05/17/07 05:04:03 Attach to Shadow?Copy?Components
[5464] 05/17/07 05:04:03 Informational status CODE (0x00000002) returned calling FindFirstFile for C:\WINDOWS\system32\perf?0
[5464] 05/17/07 05:04:03 Status FS_NOT_FOUND (0xE00084AF) returned determining if Writer SqlServerWriter should be displayed when generating logical directory tree
[5464] 05/17/07 05:04:03 Warning status -536836945 calling FS_EnumSpecFiles for device Shadow?Copy?Components in LP_ENV::LoadEnumSpecFileEx
[5464] 05/17/07 05:04:03 Detach from Shadow?Copy?Components
[5464] 05/17/07 05:04:03 brUtil::brUtil Destructor
[5464] 05/17/07 05:04:03 Status 0xE00084AF calling LoadEnumSpecFileExcludes in LP_DoBackup
[5464] 05/17/07 05:04:03 LP_ENV::MsgError: error 0xe00084af processing object <Unknown>
[5464] 05/17/07 05:04:03 Job Stop(0) - Thu May 17 05:04:03 2007
[5464] 05/17/07 05:04:03 ERROR: ndmpdDataAbort: invalid state to process abort request.
any help would be appreciated
Further info:
This could be a permissions issue.
In the Job Setup window, edit the job and then in the graphical view ensure that when you click on a drive that something appears in the right-hand window. Otherwise, you should get your permissions error there.
http://seer.support.veritas.com/docs/278705.htm
http://seer.support.veritas.com/docs/261831.htm
https://forums.symantec.com/syment/board/message?board.id=103&message.id=54411
or work through:
http://www.google.co.uk/search?hl=en&q=Backup+Exec+Error+0xe00084af&btnG=Search&meta=
This could be a permissions issue.
In the Job Setup window, edit the job and then in the graphical view ensure that when you click on a drive that something appears in the right-hand window. Otherwise, you should get your permissions error there.
http://seer.support.veritas.com/docs/278705.htm
http://seer.support.veritas.com/docs/261831.htm
https://forums.symantec.com/syment/board/message?board.id=103&message.id=54411
or work through:
http://www.google.co.uk/search?hl=en&q=Backup+Exec+Error+0xe00084af&btnG=Search&meta=
Do you have the Shadow Copy Components selected for backup as well.
The error seems to suggest a problems with the SQL Writer - part of VSS.
Do you see any problem when you run "vssadmin list writers" from the command line? All the writers should display a "Stable" state with "No error". Do you see an SQL writer in the output?
Not sure if you tried this already, but a reboot may help if it's a writers problem.
The error seems to suggest a problems with the SQL Writer - part of VSS.
Do you see any problem when you run "vssadmin list writers" from the command line? All the writers should display a "Stable" state with "No error". Do you see an SQL writer in the output?
Not sure if you tried this already, but a reboot may help if it's a writers problem.
ASKER
honmapog--no, sorry the sql errors are likely there because i have shut down one on the servers that is not being used. Yes i have run "vssadmin list writers" and there are no errors but a good suggestion. previous in the log, BE connects fine with my main SQL Server--it's just failing on the one i that i shut down. however the backup job i set up is only trying to copy 1 folder of about 1Mb of text files--NOTHING else. and the error still occurs a minute or so into the job. I can back up System State just fine.
ASKER
madcowz--thank you for the links but i tried all of those suggestions before posting here and i'm still having the issue.
a question though--veritas says to apply "10.0 5520 Hotfix 1" to resolve this specific issue. But, i'm not running v10.0.5520. I'm running v10.0.5484--veritas also claims that "revision 5484 - Service Pack 5" contains all previous Hotfixes. I have applied Service Pack 5 but this has not helped. This is confusing to me, maybe I still need to apply 5520 Hotfix 1 even though it was released before SP5? Would this even work on my installation as I am running v5484 and this hotfix is for v5520? if this won't work then i'm very worried because i've tried everything else...(i think)
thanks
-k
a question though--veritas says to apply "10.0 5520 Hotfix 1" to resolve this specific issue. But, i'm not running v10.0.5520. I'm running v10.0.5484--veritas also claims that "revision 5484 - Service Pack 5" contains all previous Hotfixes. I have applied Service Pack 5 but this has not helped. This is confusing to me, maybe I still need to apply 5520 Hotfix 1 even though it was released before SP5? Would this even work on my installation as I am running v5484 and this hotfix is for v5520? if this won't work then i'm very worried because i've tried everything else...(i think)
thanks
-k
goldylamont -- did I understand correctly that you've shut down SQL on the server that causes you problems at the moment? I think SQL may still be the key to your problem. Did the start of this problem correspond to the SQL shut down?
The debug log dispays "FS_NOT_FOUND (0xE00084AF) returned determining if Writer SqlServerWriter should be displayed when generating logical directory tree". This is the same error code as the final error code in your job.
"when generating logical directory tree" may also explain why it happens so quickly into the job - to me this text suggest the error is encountered during the preparation phase of the job.
If SQL is still installed on that server, but just shut down, would you be able to start it again to see if it makes a difference?
The debug log dispays "FS_NOT_FOUND (0xE00084AF) returned determining if Writer SqlServerWriter should be displayed when generating logical directory tree". This is the same error code as the final error code in your job.
"when generating logical directory tree" may also explain why it happens so quickly into the job - to me this text suggest the error is encountered during the preparation phase of the job.
If SQL is still installed on that server, but just shut down, would you be able to start it again to see if it makes a difference?
ASKER
There's three instances of SQL on the server, which to me is annoying. There's
1) SQL2005DEV -- the main one
2) SQL20005EXPRESS -- installed before i began working with client, but disabled. i dunno who installed this
3) MSDE -- annoying that this needs to be there. But I can't uninstall it because Veritas needs a SQL database to store info and the silly program wouldn't recognize SQL2005DEV saying that it needs SQL2000SP3a or better (but isn't SQL2005SP4 better than old ass SQL2000SP3a?).
Plus, i've never even tried to backup a SQL database. Also, this is the first time I've installed Veritas on this server and it has not worked yet, so there was no point specifically that veritas stopped working, rather it hasn't worked yet.
i still haven't had a chance to try installing 5520 Hotfix 1 but i will try this evening. i'll keep my fingers crossed. thanks for input. i'll let you know as soon as i get somewhere on this what is going on.
1) SQL2005DEV -- the main one
2) SQL20005EXPRESS -- installed before i began working with client, but disabled. i dunno who installed this
3) MSDE -- annoying that this needs to be there. But I can't uninstall it because Veritas needs a SQL database to store info and the silly program wouldn't recognize SQL2005DEV saying that it needs SQL2000SP3a or better (but isn't SQL2005SP4 better than old ass SQL2000SP3a?).
Plus, i've never even tried to backup a SQL database. Also, this is the first time I've installed Veritas on this server and it has not worked yet, so there was no point specifically that veritas stopped working, rather it hasn't worked yet.
i still haven't had a chance to try installing 5520 Hotfix 1 but i will try this evening. i'll keep my fingers crossed. thanks for input. i'll let you know as soon as i get somewhere on this what is going on.
ASKER
forgot to mention--Veritas claims to connect to the main SQL2005DEV just fine. it only complains about the instance that is shut down.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
honmapog, that's it! i just needed to upgrade to 10.1. i think it's silly how non-obvious this was. I installed the version of backup exec that came with the server then i ran all the upgrades and hotfixes and it still wouldn't work. i didn't know that i could go from 10.0 to 10.1 without having to shell out cash...and then why would i if i couldn't get it to work anyway. it kinda sucked because i couldn't find anywhere on the site that even mentioned you could upgrade versions or that basically 10.0 wouldn't work at all.
thanks!
thanks!
Regardless of running 2005 SQL, this has solved my problem of noit backing up anything on the local server, shares, anyhting, yet backing up remote servers and exchange. Has baffled me for a while and whilst being very scared with no backups for the last 7 days, I can now sleep again....good work!!!
Found the Solution - Stop SQL VSS writers service and disable it.
I found that "ihotdesk"'s solution worked for me as well, and I didn't have to update Backup Exec.
ASKER
i stopped using Symantec Backup Exec altogether. it's slow, bloated and buggy--maybe if you're an enterprise customer with lots and lots of servers it could be useful but for small business it's much better to just use the free and easy NTbackup and backup to a USB or eSATA hard drive. I have SQL backing up to disk on schedule also.
I have seent his cause this error before.