A branch off server recently encountered a dirty shutdown. This is the second time in two weeks that this has occurred (Auto-installing windows updates the culprit and I have now disabled that). Because of the recent hotfix MS put out, disabling auto-recovery by default, I had to put in a WMIC command to resume replication. The first time this worked fine. The second time this command doesn't work. What is the best way to troubleshoot from here?
Event ID 2213:
The DFS Replication service stopped replication on volume E:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.Additional Information:
Volume: E:
GUID: 9A5EE0EE-3E9A-435B-ABF5-9CF4A0FAB5A9
Recovery Steps
1. Back up the files in all replicated folders on the volume. Failure to do so may result in data loss due to unexpected conflict resolution during the recovery of the replicated folders.
2. To resume the replication for this volume, use the WMI method ResumeReplication of the DfsrVolumeConfig class. For example, from an elevated command prompt, type the following command:
wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="9A5EE0EE-3E9A-435B-ABF5-9CF4A0FAB5A9" call ResumeReplication
For more information, see http://support.microsoft.com/kb/2663685.
Error I recieve when I attempt the WMIC command:
