07-23-2013 05:53 AM
Hi everyone,
One of our clients uses Backup Exec 2012 SP1 and I am responsible for Backup Exec as an technical support engineer.
We have an issue for backing up Exchange database. All databases are backing up succesfully but two of them always get this error.
I need for advices in order to resolve this problem quickly.
Event id : 34113 on backup exec server
And this is the error message in backup exec :
V-79-57344-65233 - Snapshot Technology: Initialization failure on: "\\[Exchange server name]\Microso... Snapshot technology 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...
Solved! Go to Solution.
07-24-2013 06:20 PM
In a command prompt, run vssadmin list writers. If there are any writers which are not o.k., reboot your Exchange server.
07-24-2013 06:20 PM
In a command prompt, run vssadmin list writers. If there are any writers which are not o.k., reboot your Exchange server.
07-25-2013 12:58 AM
08-01-2013 01:41 AM
Now exchange server has been rebooted. And I will be monitoring exc. backup jobs to be sure.
For now it looks like rebooting the server has worked. Altough there was no error when using vssadmin list writers, rebooting the server looks like as a solution.
I will be update this issue when it has been approved.
Thank you all for your advices.
09-09-2013 11:39 AM
Event ID: 34113 - V-79-57344-65233 - Snapshot Technology: Initialization failure on: "\\ servername \Microsoft Information Store\Public Folder Database 1159845336".
Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
Snapshot technology error (0xE000FED1): A failure occurred querying the Writer status
I started getting the above error on failing backups last week, running BE 2012 v14 on a Win 2008 R2 sp1 Enterprise server. BE had run successfully for years until now. If I run vssadmin list writers, there are no errors.
If I reboot the server, then BE completes successfully. Do I understand from the above that I must reboot this server every night? I would really like to know the concept of what is happening.
09-24-2013 05:03 AM
It seems that rebooting the server solves the problem but when it happens again the server must be rebooted again.
03-17-2014 06:42 PM
Hi,
can some help me or explain further why we need to reboot the each server everytime we stumble w/ this error? On my part the exchange servers are connected to EMCVNX5300 storage. Up to now i havent found explaination why we need to reboot it.
Regards,
Ian
02-28-2017 07:03 AM
I am getting the below error but I am not running Exchange through this server. Does the solution in the feed apply to this error as well. When I ran vssadmin list writers i got failed errors on system writer says timed out, on NTDS, FRS and WMI all failed Timed out. The solution looks like a simple reboot of the server fixes this. Is this correct?
Thanks
MSWShimizu
Backup
V-79-57344-65233 - Snapshot Technology: Initialization failure on: "\\SNA00.SNAUS.com\System?State"....
Snapshot technology error (0xE000FED1): A failure occurred querying the Writer status. See the job l...
Check the Windows Event Viewer for details.
Writer Name: Active Directory, Writer ID: {B2014C9E-8711-4C5C-A5A9-3CF384484757}, Last error: The VS...
Writer Name: Background Intelligent Transfer Service, Writer ID: {4969D978-BE47-48B0-B100-F328F07AC1...
Writer Name: System Files, Writer ID: {E8132975-6F93-4464-A53E-1050253AE220}, Last error: The VSS Wr...
Writer Name: SYSVOL, Writer ID: {D76F5A28-3092-4589-BA48-2958FB88CE29}, Last error: The VSS Writer t...
Writer Name: Windows Management Instrumentation, Writer ID: {A6AD56C2-B509-4E6C-BB19-49D8F43532F0}, ...