none
VSS NTDS Writer Failed

    Question

  • On one of my AD 2008 domain controllers the NTDS writer is in failed state.

    Writer name: 'NTDS'
       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
       Writer Instance Id: {a0b40cc8-ded5-4497-b6dd-50f56de2dbe2}
       State: [11] Failed
       Last error: Non-retryable error

    This is Windows server 2008 STD 64 bit

    I'm trying to find out if there is a way to fix this WITHOUT rebooting my DC.  I tried restarting the VSS service.

    The cause of the failure was this.

    lsass (636) An attempt to write to the file "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\Windows\NTDS\edb.log" at offset 6029824 (0x00000000005c0200) for 512 (0x00000200) bytes failed after 0 seconds with system error 19 (0x00000013): "The media is write protected. ".  The write operation will fail with error -1032 (0xfffffbf8).  If this error persists then the file may be damaged and may need to be restored from a previous backup.

    lsass (636) Unable to write to logfile \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\Windows\NTDS\edb.log. Error -1032 (0xfffffbf8).

    Any help is greatly appreciated!

    Friday, August 10, 2012 5:42 PM

All replies

  • The primary solution for this type of issue is rebooting the server. So, please reboot the server and report back the result...

    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    • Marked as answer by Statistic Saturday, August 18, 2012 12:05 AM
    • Unmarked as answer by Statistic Saturday, February 09, 2013 7:59 PM
    Saturday, August 11, 2012 9:23 PM
  • Yeah that's what the AppAssure guys told me.  I was looking for something a little less intrusive.  I can't go around rebooting domain controllers and affecting production systems without a maintenance window.

    Sunday, August 12, 2012 7:04 PM
  • How many DCs you have in your production network? If you have more than one, you can reboot the server without any effect to your network...

    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Sunday, August 12, 2012 7:15 PM
  • Any updates for your issue?
    Friday, August 17, 2012 10:19 PM
  • Rebooting worked, but i'm not happy with it.

    • Proposed as answer by Pankul Jain Saturday, February 09, 2013 10:05 AM
    • Unproposed as answer by Pankul Jain Saturday, February 09, 2013 10:05 AM
    Saturday, August 18, 2012 12:05 AM
  • Same issue with us also , and reboot does not help, any other suggestions ??
    Saturday, February 09, 2013 10:06 AM
  • Yes actually I've found the answer.  You can run the following commands.

    "vssadmin list writers"

    You'll see some in error.

    Restart the Com and DCOM services.

    Restart the Volume Shadow Copy Service.

    Rerun the vssadmin command and check your writers.  If any are in error then you need to reboot, but I've found this works about 98% of the time.

    Saturday, February 09, 2013 8:01 PM
  • thank
    Monday, August 12, 2013 4:00 PM
  • Worked perfectly for me on SBS-2008.

    Thanks, IBTS !!

    Tuesday, March 11, 2014 1:58 PM