cancel
Showing results for 
Search instead for 
Did you mean: 

Microsoft Exchange Writer failed

Jan_Rustico
Level 4

We've tried to restart the target machine which sports the error below; we also tried to stop and start the said writer, still got the same issue:

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {534eb61c-849b-4558-9a89-11b4fd9f3712}
   State: [9] Failed
   Last error: Timed out

Currently using Exch Server 2013 CU6 run under Win 2012 R2 Standard, NBU 7.6.0.4 (client/server)

 

1 ACCEPTED SOLUTION

Accepted Solutions

revarooo
Level 6
Employee

You will need to speak with Microsoft support about that.

View solution in original post

3 REPLIES 3

revarooo
Level 6
Employee

You will need to speak with Microsoft support about that.

Michael_G_Ander
Level 6
Certified

Can happen if this disk reponse if not fast enough.

Another thing I have see on Exchange servers, is memory exhaustion causing problems with the VSS/Volsnap system.

The system & application event logs on the Exchange server is where I would start.

 

 

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

gurminder_singh
Level 5

Hi

 

If you are still facing issue after rebooting client you can try to re-register vss dll file with help of steps mentioned at below link

http://careexchange.in/how-to-re-register-vss-volume-shadow-copy-service-in-windows-server-2008-r2/