10-17-2011 08:31 AM
HI All,
My Exchange Full backup keeps failiing with this error:
Error category : Security Errors Error : e0001904 - 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 operat For additional information regarding this error refer to link V-79-57344-6404
The link that it refers to is irrelevant, it mentions events that do not occur.
Can any one help, or at least point me in the right direction.
If you need more info please ask.
Thanks,
-Tim
10-17-2011 09:04 AM
On the Exchange server open the command promp and run the following command:
VSSADMIN LIST WRITERS
This will display the status of all the writers on the server which will also include the Exchange writers. Check the status of the Exchange writers (it may be Unstable).
If th status of Exchange writers is Unstable then you will have to reboot the Exchange server and then try the backups.
Thanks,
-Sush...
10-17-2011 09:16 AM
Hi Sush,
Thanks for the reply, unfortunately I have done that, and they were all No Errors.
V Confusing.
-Tim
10-17-2011 09:18 AM
Here is the output from it:
10-17-2011 10:42 AM
Is this export from immediately after the backup has failed ?
If not, run a backup, after failure run the vss list writers command.
10-17-2011 11:40 AM
Hi Tim,
It doesn't matter if your VSS writers show as failed in the details you provided before or after the backup...if they failed before the backup, it explains the failed backup. If they failed after the backup, they still need to be fixed.
You have 2 options, both of which I'd personally do:
1. Run the VSS Rollup Patch from the MS site and install it. Once done, reboot your server and run: vssadmin list writers again to check they are stable:
http://support.microsoft.com/kb/940349
2. ...if they are, leave it as is. If not, reregister the VSS *.dlls using the Symantec TN below:
http://www.symantec.com/business/support/index?page=content&id=TECH70486
Report back with an update.
Thanks!
10-18-2011 03:28 AM
Hi Craig,
I have previously done step 1, and so obv didn't have an impact.
I can't do Step 2, as that is for 2008 and my exchange is on 2003. Though there was a link to another MS KB article that had similar fixes (http://support.microsoft.com/kb/940032).
So I have done them and we will see if that makes a difference.
Also fyi, a reboot (of exchange) always manages to fix it, but after a while it then fails again.
Cheers,
-Tim
10-18-2011 04:02 AM
Any errors in the eventlog of the Exchange server at the same time as the backup runs ?
10-18-2011 04:26 AM
Hi Tim,
I've used #2's Symantec TN to successfully reregister the VSS DLLs on a Server 2008 server...you just need to create the batch file, and run it with adminstrator rights...nothing to it. You don't need a server restart and it doesn't interfere with anything. I've done it a number of times over the past couple of months. Exchange doesn't have anything to do with reregistering the *.dlls.
Thanks!
10-18-2011 06:16 AM
Ah I thought it was supposed to be done on the exchange server. OK have run it on the backup server.
I take it that this does not permanently fix this issue?
Would you recommend setting it as a scheduled task to run once a week/month?
@ZeRo: There are not any relevant events, apart from the failed job (standard message), on either servers.
Cheers,
-Tim
10-18-2011 06:42 AM
Hi
Can you please ensure while your exchange backup job is runnin during same time window database maintainence is not scheduled for exchange databases if so please change the schedule
Thanks
10-18-2011 08:20 AM
Well, you'll run it on the server giving you those VSS issues. So if it is on the Exchange server, run the fix there.
If using Win2K3, the Microsoft TN that is listed points you to a small executable that you download and run. Again, this is nonintrusive and reregisters your *.dlls.