VSS errors related to NTDS writer failures

KB ID: 1697
Product: Veeam Backup & Replication
Version: 6.x, 7.x, 8.x
Published:
Last Modified: 2015-05-11

Challenge

Veeam Backup & Replication job using Application-Aware Processing to process a Domain Controller fails with one the following errors:

Unable to release guest. Details: Unfreeze error: [Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [NTDS]. Class ID: [{b2014c9e-8711-4c5c-a5a9-3cf384484757}]. Instance ID: [{66fddc15-0e4c-4a2a-ad31-32eaf6dae8a3}]. Writer\'s state: [VSS_WS_FAILED_AT_POST_SNAPSHOT]. Error code: [0x800423f4].]
 
Error: VSSControl: 0 Backup job failed.
Cannot create a shadow copy of the volumes containing writer's data.
Cannot prepare the [NTDS] data to a subsequent restore operation.
Cannot process NTDS data.
Cannot create a backup copy of the BCD.
  
Error: VSSControl: -1 Backup job failed.
Cannot create a shadow copy of the volumes containing writer's data.
Cannot prepare the [NTDS] data to a subsequent restore operation.
Cannot process NTDS data.
Cannot create a backup copy of the BCD. Cannot get [BcdStore] object. COM error: Code: 0xffffffff

Solution

The actions listed in this section are to be performed within the Guest OS of the DC that is having these issues.
 
The cause is most likely one of the following, if a listed troubleshooting step requires attention test the Veeam job after performing that troubleshooting task before proceeding on to further troubleshooting steps.
 
──────────────────────────────────────────────────────────
Verify that the NTDS VSS writer is stable.
──────────────────────────────────────────────────────────
From and elevated command prompt run the following command:



vssadmin list writers
 
The results will appear as:

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {ee24b741-eaf7-4663-8f95-b92ae8c5e164}
   State: [1] Stable
   Last error: No error

If not listed as stable reboot the DC.
 
──────────────────────────────────────────────────────────
Verify that Automatic mounting of new volumes enabled.
──────────────────────────────────────────────────────────
From a Run command (Win+R) execute the command diskpart.
 
From within Diskpart run the following command.

 
automount
 
If the results do not show “Automatic mounting of new volumes enabled.” Run the following command:

automount enable
 
──────────────────────────────────────────────────────────
Verify that there are no .bak keys in the ProfileList within the Registry.
──────────────────────────────────────────────────────────
From a Run command (Win+R) execute the command regedit.
 
Within the registry navigate to:


HKLM\Software\Microsoft\Windows NT\CurrentVersion\ProfileList
 
There will be a list of Keys, you must remove any ending in .bak

User-added image

More Information

The Majority of cases are resolved uses the above 3 troubleshooting steps. However in rare cases the WMI repository must be rebuilt. To do this please refer to the following article:
http://blogs.technet.com/b/askperf/archive/2009/04/13/wmi-rebuilding-the-wmi-repository.aspx
 
How helpful is this article: 
2.7 out of 5 based on 64 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Request new content

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Orphus system