Restore of an Exchange 2007 database fails with the error "0xe000fed1 - A failure occurred querying the Writer status"


Restore of an Exchange 2007 database fails with the error "0xe000fed1 - A failure occurred querying the Writer status"

Error Message

0xe000fed1 - A failure occurred querying the Writer status

Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: 0x800423f3, State: 0013. A failure occurred querying the Writer status.

The job log displays the following errors: 



This issue occurs if the option "Restore all transaction logs; do not delete existing transaction logs (no loss restore)" is selected while performing a restore with a fresh copy of the Exchange Database, because it is not possible to do this type of restore with an empty Exchange Database.


1. On the navigation bar in Backup Exec, click Restore.
2. On the Restore Job Properties pane, click Settings | Microsoft Exchange.
3. Select the option "Purge existing data and restore only the databases and transaction logs from the backup sets". (Figure 2)

Figure 2

4. Rerun the restore.

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.
There are currently no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. This issue may be resolved in a future major revision of the software at a later time. 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

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)