Forum Discussion

Jan_Rustico's avatar
Jan_Rustico
Level 4
10 years ago

Microsoft Exchange Writer failed

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)

 

7.6
Backing Up
Backup and Recovery
Basics
Best Practice
NetBackup
Performance
Troubleshooting
Windows Server (2003-2008)
  • revarooo's avatar
    revarooo
    10 years ago

    You will need to speak with Microsoft support about that.

  • revarooo's avatar
    revarooo
    Level 6
    10 years ago

    You will need to speak with Microsoft support about that.

  • Michael_G_Ander's avatar
    Michael_G_Ander
    Level 6
    10 years ago

    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.

     

     

  • gurminder_singh's avatar
    gurminder_singh
    Level 5
    10 years ago

    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/