Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Recurring Exchange Writer Errors

Created: 11 Dec 2012 | 8 comments

A client of ours is running Exchange Server 2007 under Windows SBS 2008 and the Backup Exec 2012 job will periodically fail with the following error:

Backup- \\W2K8\Microsoft Information Store\First Storage Group
V-79-57344-65233 - AOFO: Initialization failure on: "\\W2K8\Microsoft Information Store\Second 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 timed out (0x800423f2), State: Failed during freeze operation (9).

What's wacky, to me, is that the job will run successfully 60-80%, but when it fails, it always fails with the above error.  Does anyone have any ideas on how to prevent this failure from occurring?


Comments 8 CommentsJump to latest comment

lmosla's picture

Hi  There are a few hotfixes out that should resolve this issue.  Make sure that Backup Exec is completely updated to the most recent patch and that the agent has been pushed out.

Let me know the result.

RescueMe's picture


The Backup Exec software is already fully patched and the agent has been pushed out to all remote computers.


lmosla's picture

Does the customer have a virus protection program running? If so make an exclusion for the following (note: where the default location is usually the C drive)

on the Media Server

  • C:\Program Files\Symantec\Backup Exec\beserver.exe
  • C:\Program Files\Symantec\Backup Exec\beremote.exe
  • C:\Program Files\Symantec\Backup Exec\bengine.exe
  • C:\Program Files\Symantec\Backup Exec\benetns.exe
  • C:\Program Files\Symantec\Backup Exec\pvlsvr.exe
  • C:\Program Files\Symantec\Backup Exec\BkUpexec.exe

Remote Agent

  • C:\Program Files\Symantec\Backup Exec\RAWS\beremote.exe
RescueMe's picture

There currently is no virus protection running on this system.


psj_symhelp's picture

perform below step to solve the problem

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.

Finally 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

pkh's picture

If you are going to quote substantially from a document like the one below, it would be better to just put a link to the document.  Otherwise, people might think that you are plagarising.

psj_symhelp's picture


does problem resolved with above technical note ?

pkh's picture

If you want an update on the status of the problem, PM the user.