Microsoft Exchange 2003/2007/2010 backup fails with an error "E000FED1: A failure occurred querying the Writer status"

Article:TECH125176  |  Created: 2010-01-26  |  Updated: 2014-01-02  |  Article URL http://www.symantec.com/docs/TECH125176
Article Type
Technical Solution

Product(s)

Issue



Problem occurs while performing exchange backup, Microsoft Exchange writer crashes while taking snapshot of Exchange.


Error



Job Log Description:

Backup- V-79-57344-65233 - AOFO: Initialization failure on: "Exchange server name\Microsoft Information Store\First Storage Group". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.

Check the Windows Event Viewer for details.
Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Failed during prepare snapshot operation (8).

or

V-79-57344-6404 - AOFO: Initialization failure on: "\\DAGName.DomainName\Microsoft Information Store\DatabaseName". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS)
Snapshot provider error (0xE0001904): A failure occurred querying the Writer status. Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Failed during prepare snapshot operation (8).
Check the Windows Event Viewer for details.

 

Event viewer on exchange server shows following event IDs

Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9840
Description: An attempt to prepare the storage group 'First Storage Group' for backup failed because the storage group is already in the process of being backed up. The error code is 1293. (Note that if a backup was recently aborted, then it may take several minutes for the system to detect the aborted backup and initiate backup cleanup procedures, so this message may be generated if an attempt was made to backup a storage group before a previous backup attempt had fully terminated.)


When you try to perform a VSS backup of a mailbox database or of a public folder database in Microsoft Exchange Server 2003, the backup operation fails. Additionally, the following event is logged in the event log:
Event Type: Error
Event Source: MSExchangeIS
Event Category: Exchange VSS Writer
Event ID: 9607
Description: Error code 0x50d when preparing for backup. 
Data: 0000: 42 61 63 6b 75 70 20 69 Backup i 0008: 6e 20 70 72 6f 67 72 65 n progre 0010: 73 73 2e 00 ss..

 

Log Name:      Application
Source:        MSExchangeIS
Date:          7/22/2010 2:17:06 AM
Event ID:      9814
Task Category: Exchange VSS Writer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:   Exchange server FQDN
Description:
Exchange VSS Writer (instance 86453ccb-1181-45fe-9e7c-072b7494e440:8) failed with error code -2403 when preparing the database engine for backup of database 'Mailbox Database' (activation preference number).
 

Log Name:      Application
Source:        ESE
Date:          7/22/2010 2:17:06 AM
Event ID:      2007
Task Category: ShadowCopy
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Exchange server FQDN
Description:
Information Store (2064) Shadow copy instance 8 aborted.

 

Log Name:      Application
Source:        MSExchangeIS
Date:          10/28/2010 7:51:52 AM
Event ID:      9609
Task Category: Exchange VSS Writer
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EXCHANGE01.network.com
Description:
Exchange VSS Writer (instance 2f5bbb68-ba32-42e1-8e03-e78ada2acbed:16) failed with error code -2403 when preparing for Snapshot.


Cause



This problem may occur if the following conditions are true:

  1. VSS uses the Microsoft Jet database engine to freeze or thaw a snapshot backup.
  2. The Jet database engine encounters an error.
  3. The Jet database engine silently frees all storage groups from the snapshot session when the error occurs.
  4. VSS snapshots are present on the volume hosting Exchange or Exchange logs at the time Backup Exec attempted the backup.

When these conditions are true, the Jet database engine does not report the correct status of these storage groups to Exchange. Therefore, Exchange does not reset the backup-in-progress state. If you try to back up the affected storage group again, the given error occurs.


Solution



This is Microsoft exchange related issue and solution is present on following Microsoft technical article :-
Event ID 9840 or 9607 is logged when a VSS backup operation fails in Exchange 2007, Exchange 2010 or in Exchange 2003 
 If getting Event ID 477, Source as ESE on Exchange Server :

    Event ID 477
    Source ESE
    Description Catalog Database (628) The log range read from the file <log file path> at offset <offset> for <bytes number> bytes failed verification due to a range checksum mismatch. The read operation will fail with error <error code>. If this condition persists then please restore the logfile from a previous backup.

    Please review the following items, perform the following suggestions listed below and if the issue persist please contact Microsoft technical support for further assistance in resolving the Exchange Database issue.

    Restore the database from a previous backup.

  • Perform a repair on the database following the Microsoft recommendations located here http://support.microsoft.com/kb/272570/EN-US/ 
  • Run any hardware diagnostic tools available for the hard disk on which the Exchange database resides.
  • Update firmware and drivers for the hard disk controllers on the Exchange server.

NOTE: For further information about EventID 477 consult the following Microsoft KB document: http://support.microsoft.com/kb/810411

 
Following are some points and steps which can be considered before consulting Microsoft:
 
  • If Exchange writer is in failed state, normally just rebooting the Exchange server will bring back the writer status to 'stable' state. Check the writer status by running the command 'vssadmin list writers' from command prompt on Exchange Server.
  • Review other backup provider schedules including the Microsoft Exchange Database Maintenance Schedule to ensure that backups time frames are not conflicting. Adjust accordingly to resolve the error.
 
Restart Microsoft Exchange Replication service on Exchange server and retry the backup for High Availability Server (Exchange 2007 or later). 
 
Method 1: Dismount all databases in the storage group

Use this method if the event ID 9840 that was logged on the Exchange 2007 server contained error code 2403.
To dismount all databases in the storage group, follow these steps:
  1. Click Start, point to All Programs, point to Exchange Server 2007, and then click Exchange Management Console.
  2. Expand Server Configuration, and then expand the storage group that is listed in the event ID 9840 message that was logged on the Exchange 2007 server.
  3. Right-click each database in that storage group, and then click Dismount Database.
  4. Click Yes to confirm the operation.
  5. After the dismount operation is complete, right-click the database again, and then click Mount Database.
  6. Try to perform the backup operation that resulted in event ID 9840.
     
If this method does not resolve the problem, try method 2.
 
Method 2: Restart the Microsoft Exchange Information Store service

Use this method if the event ID 9840 that was logged on the Exchange 2007 server contained error code 1293. Use this method if Event ID 9607 was logged on Exchange 2003. Additionally, use this method if method 1 did not resolve the problem.
To restart the Microsoft Exchange Information Store service, follow these steps:
 
  1. Click Start, point to All Programs, point to Administrative Tools, and then click Services.
  2. Right-click Microsoft Exchange Information Store, and then click Restart.
  3. Try to perform the backup operation that resulted in event ID 9840.


 If issue still persists, Please contact Microsoft Support for further assistance.

 

In order to verify that no snapshots are present, follow these steps:

  1. Open a command prompt on the Exchange server and type the command "Vssadmin list Shadows".
  2. If a snapshot exists, it will be listed. Before attempting to delete the snapshot make a note of the time at which it was taken. This will help to determine if the orphaned snapshot was created during or outside a backup. If the snapshot was created outside a backup, check for scripts or application that could have created it (for example some applications take snapshots by creating Scheduled Windows tasks).
  3. Make a note of the ShadowId and use command "Vssadmin delete shadows /Shadow=<ShadowId>" to delete it.

It is also suggested to run Windows updates and install all available hotfixes on Exchange Servers and reboot.

 

The writer timeouts if there is another snapshot process is completing or in process:

If run command "vssadmin list writers" it will show Exchange writer status in Failed State 9. Here, need to check if no other third party application using VSS, like Volume level Shadow Copies on the system drives. If so, need to disable the Shadow Copies on these drives. Kindly note that disabling the shadow copies for the drive will delete all existing Shadow Copies.

 

This error "V-79-57344-65233 - A failure occurred querying the Writer status.", can also occur during Exchange Incremental backup of a SBS 2011:

It will give similar errors in the job log:

Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, the process can be repeated (0x800423f3), State: error during the backup preparation (7).


Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, the process can be repeated (0x800423f3), State: error during the blocking process (9).

This error causes if Circular Logging is enabled on Exchange. A differential or Incremental backup cannot be done if circular logging is enabled. To perform Incremental or differential type of backups, the logging method on Exchange needs to be changed by disabling the Circular Logging. Refer www.symantec.com/docs/TECH11310


Supplemental Materials

SourceUMI
ValueV-79-57344-65233
Description

A failure occurred querying the Writer status


SourceEvent ID
Value9840
Description

An attempt to prepare the storage group 'sg3' for backup failed because the storage group is already in the process of being backed up. The error code is 1293. (Note that if a backup was recently aborted, then it may take several minutes for the system to detect the aborted backup and initiate backup cleanup procedures, so this message may be generated if an attempt was made to backup a storage group before a previous backup attempt had fully terminated.)


SourceEvent ID
Value9607
Description

Error code 0x50d when preparing for backup


SourceError Code
ValueE000FED1
Description

A failure occurred querying the Writer status



Legacy ID



346503


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


Terms of use for this information are found in Legal Notices