"Sysvol" not replicating on a win 2012 DC...event 2213 logged in DFSR log

Issue:

We have 3 Win 2012 DCs and one of the DCs (DC1) started logging event 2213 with below text:

"The DFS Replication service stopped replication on volume C:. 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: C:
GUID: 5A8F8A87-DA18-11E2-93F6-806E6F6E6967
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="5A8F8A87-DA18-11E2-93F6-806E6F6E6967" call ResumeReplication
For more information, see http://support.microsoft.com/kb/2663685."


I read through MS KB 2958414 and gathered following troubleshooting info:
Following command returns sysvol share for all 3 DCs:
For /f %i IN ('dsquery server -o rdn') do @echo %i && @(net view \\%i | find "SYSVOL") & echo
Following command reports a state value of 4 for other 2 DCs but for this DC (DC1) it fails to report a state value and indicates "No Instance(s) Available.":
For /f %i IN ('dsquery server -o rdn') do @echo %i && @wmic /node:"%i" /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo WHERE replicatedfoldername='SYSVOL share' get replicationgroupname,replicatedfoldername,state
Following command returns a value of 60 days for MaxOfflineTimeInDays, so freshness state on all 3 DCs is enabled:
For /f %i IN ('dsquery server -o rdn') do @echo %i && @wmic /node:"%i" /namespace:\\root\microsoftdfs path DfsrMachineConfig get MaxOfflineTimeInDays
Event ID 4012 is not logged on this DC but event 2213 started appearing about 3 months back.


Query about Actions required:
From the troubleshooting info above I think the following portion of Step3 in above article applies to our situation: "If content freshness is not enabled or triggered and there are three or more domain controllers in the domain"
So according to the article I should backup SYSVOL data on each domain controller and run the ResumeReplication WMI method on the affected domain controllers. Is that correct?
And would the following command provided in the event id 2213 be the correct one to run?:-
wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="5A8F8A87-DA18-11E2-93F6-806E6F6E6967" call ResumeReplication
mc7Asked:
Who is Participating?
 
Michael PfisterConnect With a Mentor Commented:
Backup the sysvols on your domain controllers in case changes were made on different DCs that haven't been replicated to the others (which can cause a conflicts).

And yes, to resume replication just run the wmic command on an elevated command prompt on the affected DC.
0
 
Michael PfisterCommented:
When DFS replication has recovered you should see  event ID 2214
0
 
Michael PfisterCommented:
Asker never came back, answer should have helped
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.