VMWare Agent Application GRT (Granular Restore Technology) backup of a guest Virtual Machine running Microsoft SQL Server 2008 fails with an error "0xe000fedf - A failure occurred reading an object"

  • Article ID:100024157
  • Modified Date:
  • Product(s):


Backup of a VMware ESX virtual machine running Microsoft SQL Server 2008 fails when Application GRT option is selected. Job log reports the following error

Final error: 0xe000fedf - A failure occurred reading an object.
V-79-57344-65247 - Error. Cannot backup directory \zzzVirtApp000zzz and its subdirectories.


Backup completes with exceptions:

V-79-57344-38749 - Backup Exec was unable to prepare Microsoft SQL resources for Granular Recovery Technology (GRT) operations

Error Message


Debug of the VMware Agent on Media Server and Remote Agent on the guest Virtual machine shows the following;

Beremote debug of the SQL Virtual machine shows the following details for one of the database


[fsys\sql2]          - SQL2: Snapshot Restore file list:
[fsys\sql2]          - SQL2: Logical Name: Database
[fsys\sql2]          - SQL2: Logical Name: Database_log
[fsys\sql2]          - SQL2: Logical Name: sysft_ftcat_documentindex
[fsys\sql2]          - SQL2: Physical Name: E:\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Data\Database_MSCRM.mdf
[fsys\sql2]          - SQL2: Physical Name: E:\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Data\Database_MSCRM_log.LDF
[fsys\sql2]          - SQL2: Physical Name: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\FTData\ftcat_documentindex0000


Media Server beremote debug log shows the following error;


[fsys\brfs]          - brUtil::OpenActiveObject Error: 0xE00084AF Could not open the object ftcat_documentindex0000 C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\FTData\ftcat_documentindex0000
[fsys\ohfs]          - OFF_HOST_FS::ReadObj( ) pBrUtil->ReadObject( ) Error status CODE (E00084AF)
[mounter]            - UpdateSqlPdi: failed to read object info 0xe000fedf



The above errors occur only if a particular database contains reference to the physical location of SQL Full-Text Catalog index files. With SQL Server 2008 onwards the Full-Text Catalogs are stored with the database and no longer stored at physical locations. As per the errors in the above mentioned debug log output there is no file called "ftcat_documentindex0000" present at the location "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\FTData".  This causes the backup job to fail.

Another way to confirm if this issue is specific to the database reported in the debug log is to run Remote Agent based SQL backup of that database with the AOFO (Advanced Open File Option) selected in the backup job. This backup will reportedly fail with the error "WARNING: "Database_MSCRM" is a corrupt file. This file cannot verify"


A hotfix is now available for this issue with Backup Exec 2010 R3 Rev 5204 and Backup Exec 2012 Rev 1798. Refer to the Hotfix link under Related Articles at the end of this article to obtain the hotfix needed to resolve the issue.

Backup Exec 2010 R3 Rev 5204 Hotfix 195395 - https://www.veritas.com/docs/000108122

Backup Exec 2012 Rev 1798 Hotfix 199866 - https://www.veritas.com/docs/000087030


Applies To

Note:- This issue has been seen with SQL Server 2008 instance hosting the databases for Microsoft Dynamics CRM application. If this issue is seen with any other environments and if the debug log output matches the above errors then the below provided cause and solution would still apply. 

Was this content helpful?

Get Support