cancel
Showing results for 
Search instead for 
Did you mean: 

Symantec SR Backup fails 0xE4F3000F - VSS Error

StefTS
Level 2

Hi all,

we are using a SBS 2011 Standard with System Recovery 2013 R2. We have used Backup Exec 2010 R3 before and had trouble with that too. The VSS Microsoft Exchange Writer gets into state 9 (timed out).

Backup protocol says:

Fehler E4F3000F: Unexpected VSS writer error. Check the application event log for writer specific error. Failed VSS writers: Microsoft Exchange Writer.

Details: 0xE4F3000F

I can reboot the server or the service but it will occur after 1-2 days again. We can't do any full or incremental backups in that time.

Writer name: "Microsoft Exchange Writer"
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {9b6d5bed-27f5-4409-8257-dea8f2450938}
State: [9] Failed
Last error: Timed out

I've been searching for a solution for days but no luck yet. Any help is appreciated.

Many thanks in advance

Stef

5 REPLIES 5

Markus_Koestler
Moderator
Moderator
   VIP   

Have you tried just stopping/starting the vss services before the backup?

Karl_Smith
Level 2
Partner

Glad(?) we're not the only ones that have come across this issue!
We've a number of servers that are now running SSR2013 R2 and all have this at one point. When running a Windows Backup we never get a VSS issue.

We do as Markus has suggested and this seems to help, it doesn't work all the time and a reboot is then needed to kick things back in gear.

We've been working with Symantec on this for sometime now, still no luck as to a fix :(

Anyway, in to see who else is having this issue and any ideas.

Karl.

criley
Moderator
Moderator
Employee Accredited

What version of Exchange are you running?

Please provide the exact errors that are seen in the Windows event logs. Do you still have a support case open for this? If yes, can you please provide the case number.

StefTS
Level 2

Hi,

we're running an Exchange 2010. Restarting the VSS services wouldn't help. You had to delete all shadow copys as well.

However the backup seems to run fine now. We had some warnings regarding VSS and Sharepoint in the event log (Event ID: 8230). We couldn't get them out, so we stopped the Sharepoint services completely. I don't know if this was the solution but since then, the backup runs fine.

Stef

StefTS
Level 2

Hi,

Backup failed again with this error message:

'OS-Error 2.147.754.994.'.

So Sharepoint wasn't the reason.

Stef