Backup Exec 10d error - Backup- Shadow?Copy?Components Shadow?Copy?ComponentsV-79-57344-65247 - A failure occurred reading an object.
I'm getting these errors in my worklog while doing a full backup (achive bit reset) with Backup Exec 10d (10.1 with SP2 + hotfix 43, 45 and 46) on Windows Server 2003 R2 (domain controller):
Job Completion Status
Job ended: 13. desember 2006 at 14:50:44
Completed status: Failed
Final error: 0xe000fedf - A failure occurred reading an object.
Final error category: Resource Errors
For additional information regarding this error refer to link V-79-57344-65247
Errors
Click an error below to locate it in the job log
Backup- Shadow?Copy?Components Shadow?Copy?ComponentsV-79-57344-65247 - A failure occurred reading an object.
Exceptions
Click an exception below to locate it in the job log
Backup- Shadow?Copy?Components Shadow?Copy?ComponentsWARNING: "Shadow?Copy?Components\System?Service\Event Logs\Event Logs" is a corrupt file.
This file cannot verify.
Verify- Shadow?Copy?Components Shadow?Copy?ComponentsWARNING: "Event Logs" is a corrupt file.
This file cannot verify.
I have followed the link to the support article on "V-79-57344-65247" (http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml?EvtID=V-79-57344-65245) and have tried most of what I can think about:
Link 1) When performing System State backups with the File Server Resource Manager (FSRM) installed, Quota Reports are not generated and the job will fail:
I have run the reports, I have verified that the folder C:\System Volume Information\SRM\Reports\ is not empty. At the moment there are 8 xml files there.
Link 2) V-79-57344-65245 - A failure occurred accessing the object list.
I have requested the HOTFIX for KB 833167 from microsoft and recieved it. I did not think it would work on R2 since my files was newer, and I was right. The hotfix is for non R2 windows server 2003. I am not using DFS, and I'm not getting the errors described in KB 867712.
I've also tried applying the patch described in http://support.microsoft.com/kb/913648/en-us. That did not help.
What can I do to fix this error?