Backup of a Windows Server 2003 System State with Backup Exec fails with final error: 0xe000fedf - A failure occurred reading an object

Article:TECH50883  |  Created: 2007-01-21  |  Updated: 2012-12-25  |  Article URL http://www.symantec.com/docs/TECH50883
Article Type
Technical Solution

Product(s)

Issue



Backup of a Windows Server 2003 System State with Backup Exec fails with final error: 0xe000fedf - A failure occurred reading an object.


Error



WARNING: "System?State\System Files\System Files" is a corrupt file. This file cannot verify.

Final error: 0xe000fedf - A failure occurred reading an object.
Final error category: Resource Errors


Cause



The error occurs because one of the system files contained in the System State is found to be corrupt or some third party application is interfering with the backup of these files.


Solution



In order to confirm which file is corrupt perform the following:

1. Place the Backup Exec Remote Agent service into debug mode (see related documents for instructions).

2. Create a new backup job with only System State selected and run the job.

3. job will fail with the following errors:

WARNING: "System?State\System Files\System Files" is a corrupt file. This file cannot verify.

Final error: 0xe000fedf - A failure occurred reading an object.
Final error category: Resource Errors

4. In the debug log for Remote Agent, look for the point of failure:

--------------------------------------------------------------------------------------------------------------------------------------------------------------------
[2684] 02/20/07 14:49:13 brUtil::SetupDLE Successfully set up to read the object 'C:' '\windows\system32\' 'sfc.exe' 'c:\windows\system32\sfc.exe'
[2684] 02/20/07 14:49:13 brUtil::OpenActiveObject Information: Active Object is a File C:\windows\system32\sfc.exe
[2684] 02/20/07 14:49:15 brUtil::SetupDLE Successfully set up to read the object 'C:' '\windows\system32\' '' 'c:\windows\system32\'
[2684] 02/20/07 14:49:15 brUtil::OpenActiveObject Information: Active Object is a File C:\windows\system32\
[2684] 02/20/07 14:49:15 brUtil::OpenActiveObject Error: 0x2000FE07 Could not find the object  c:\windows\system32\
[2684] 02/20/07 14:49:15 Status FS_NO_MORE (0x2000FE07) for Component System Files in SHADOW::ReadComponent
[2684] 02/20/07 14:49:15   AD:Status FS_READING_OBJECT_FAILURE (0xE000FEDF) calling FS_ReadObj in SystemState::ReadObj:233
---------------------------------------------------------------------------------------------------------------------------------------------------------------------

In this example of the debug log, the file listed just after "sfc.exe" is the file that is found to be corrupt. By looking further in the log, files added to the list to be backed up are in this order:

---------------------------------------------------------------------------------------------------------------------------------------------------------------------
[2684] 02/20/07 14:48:43    Adding c:\windows\system32\sfc.dll to the backup file list
[2684] 02/20/07 14:48:43    Adding c:\windows\system32\sfc.exe to the backup file list
[2684] 02/20/07 14:48:43    Adding c:\windows\system32\sfcfiles.dll to the backup file list
[2684] 02/20/07 14:48:43    Adding c:\windows\system32\sfc_os.dll to the backup file list
[2684] 02/20/07 14:48:43    Adding c:\windows\system32\sfmapi.dll to the backup file list
[2684] 02/20/07 14:48:43    Adding c:\windows\system32\sfmatmsg.dll to the backup file list
[2684] 02/20/07 14:48:43    Adding c:\windows\system32\sfmctrs.dll to the backup file list
---------------------------------------------------------------------------------------------------------------------------------------------------------------------

Here it can be seen that the "sfcfiles.dll" is the next file in the list to be backed up after "sfc.exe." The "sfcfiles.dll" is the object that cannot be read and therefore is corrupt.

5.  Another way to confirm that this file is corrupt is by running a backup of the System State with NT Backup. Note** NT Backup will not fail with any errors during the backup, instead the report from the backup will need to be reviewed.

Follow these steps to use NT Backup:
 
 
a. Click on Start -> All Programs -> Accessories -> System Tools -> Backup
b. Uncheck "Run in wizard mode" and click Cancel
c. Repeat step a. to open NT Backup again.
d. Click on Tools -> Options -> Backup Log and select Detailed
e. Click OK
 f.  Click on the Backup tab and select the System State
g. For Backup Destination select File and choose a location and file name.
h. Click Start Backup
 i. Click Advanced and select Verify data after backup
 j. Click OK
k. Click Start Backup
 l. When the backup finishes click on the Report button to see the report
m. Save the report as a txt file.
n. In this report search for the corrupt file - in example above "sfcfiles.dll" - notice that the file will not be listed in the report which means that NT Backup did not even backup the file. Even though no errors were reported, this confirms that the file is corrupt.
 

To resolve this issue the following steps would help:

1. If the Operating System was installed with a Service Pack - such as SP1 for Windows 2003 - re-apply the service pack and download all Windows updates.

2. In the case of Windows 2003 R2 - run an in-place upgrade to R2 and apply updates.

3. If running an ANTIVIRUS like McAfee on the affected server; try disabling that.

4. If reinstallation of service pack cannot be performed then speak with Microsoft to resolve the issue with corrupt file.

Once the file is successfully backed up using NT Backup then Backup Exec will be able to perform a backup without errors.


 

 


Supplemental Materials

SourceUMI
Valuev-79-57344-65247
Description

A failure occurred reading an object.


SourceUMI
ValueV-79-8192-65031
Description

FS_NO_MORE. Cannot backup directory and its subdirectories


SourceError Code
Value0x2000fe07
Description

FS_NO_MORE. Cannot backup directory and its subdirectories


SourceError Code
Value0xe000fedf
Description

A failure occurred reading an object



Legacy ID



287544


Article URL http://www.symantec.com/docs/TECH50883


Terms of use for this information are found in Legal Notices