AD child domain replication issues

I have a child domain that has two DC's (2012).

The 1st DC has this error (1) which seems to be there for approx 6 months. Is there any risk running the command to enable the replication again after such a long period. There are only to DC's in this child domain. I wondering what is the safest and best way to fix this issue.

wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="" call ResumeReplication

error (1) 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.

It also has these roles:
RID pool manager
Infrastructure master

The 2nd DC has this error

The DFS Replication service stopped replication on the folder with the following local path: C:\Windows\SYSVOL\domain. This server has been disconnected from other partners for 109 days, which is longer than the time allowed by the MaxOfflineTimeInDays parameter (60). DFS Replication considers the data in this folder to be stale, and this server will not replicate the folder until this error is corrected.
Who is Participating?
The 1st DC is showing that replication is stopped on that DC since long back ago
U can enable auto recovery on this server (2012 server) but I would not recommend it because it is not updated since many days
This auto recovery function is actually enabled in 2008 \ 2008 R2, however MS has released new hotfix which disables this feature
With windows 2012 this auto recovery is disabled by default

Check below article for more details

To have DFSR perform AutoRecovery when a dirty database shutdown is detected, edit the following registry value on Windows Server 2012. If the value does not exist, you must create it.
Key: HKLM\System\CurrentControlSet\Services\DFSR\Parameters
Value: StopReplicationOnAutoRecovery
Type: Dword
Data: 0

With 2012 R2 autorecovery is enabled by default for DFSR Sysvol

I still suggest that on 1st DC non authoritatively restore DFSR so that it will get updated sysvol copy from DC2 and you will back in business
U can follow non authoritative restore in link provided in my 1st comment
Your DFSR sysvol got outdated
You need to authoritatively restore DFSR sysvol database on PDC and also need to restore DFSR database on ADC non authoritatively

Check below article for step by steps:
jimbobrocksAuthor Commented:
What about the event 2213. I found this article also:
Is there a time when this window has gone too long?
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.