GRT (Granular Recovery Technology) restore of emails in Exchange 2010 fails with error "Error writing file data"

Article:TECH201808

Created: 2013-01-18

Updated: 2013-01-18

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

NOTE: If you are experiencing this particular known issue, we recommend that you to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.

Article Type
Technical Solution

Product(s)

Show all

Languages

Show all

Problem

GRT restore of email(s) in Exchange 2010 fails with following error :

Error

Error in the job log:

Error writing file data

0xe000fe2d - The backup of the item is bad.

Error in SGMON (or beremote debug) on Client Access Server:

"LP_ENV::MsgError: error 0xe000fe2d processing object Database?MailboxName?Top of Information Store?Inbox?Subject of the email"

Error in EWSdebug log:

Exception in Saving Properties Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Environment

Microsoft Exchange 2010

Cause

This can happen if the email was corrupt at the time of backup itself. In that case GRT restore will not work. Refer technote www.symantec.com/docs/TECH180064 for details. If the email is not corrupt and it can be saved properly as well as accessed from Outlook then issue matches with the one documented in this technote.

Solution

Workaround:

Restore mailbox database to recovery database and extract the email(s) from the recovery database. Refer to following technote for information on how to restore database to recovery database: www.symantec.com/docs/TECH77853

Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.

This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see www.symantec.com Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.

Supplemental Materials

Source

UMI

Value

V-79-57344-765

Description