File Replication Service failure

Question

Hi,

We had a total crash on both our 2012 R2 domain controllers, but they are now up and running....
Repadmin show that replication is ok, but we have FRS issues (Are going to migrate to DFSR soon:)

We see the following error on both our domain controllers, and I see that they provide a resolution, but should we implement the resolution on both domain controllers right after another ? wait X number of minutes ? Only implement on one server, and then the other server will be ok ?

Thanks for any answer.

/R
Andy

Error message

---

The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Replica root path is : "c:\windows\sysvol\domain"
Replica root volume is : "\.\C:"
A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.

[1] Volume "\.\C:" has been formatted.
[2] The NTFS USN journal on volume "\.\C:" has been deleted.
[3] The NTFS USN journal on volume "\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
[4] File Replication Service was not running on this computer for a long time.
[5] File Replication Service could not keep up with the rate of Disk IO activity on "\.\C:".
Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
[1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
[2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.

WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.

To change this registry parameter, run regedit.

Click on Start, Run and type regedit.

Expand HKEY_LOCAL_MACHINE.
Click down the key path:
"System\CurrentControlSet\Services\NtFrs\Parameters"
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.

If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.

---

Answer 1

You can do an authoritative restore, choose which ever one you believe is more up to date as authoritative.
https://learn.microsoft.com/en-us/services-hub/health/remediation-steps-ad/investigate-file-replication-service-frs-journal-wrap-conditions-on-domain-controllers
https://learn.microsoft.com/en-US/troubleshoot/windows-server/networking/use-burflags-to-reinitialize-frs

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 2

Hi,

You can choose one of DCs to perform non-authoritative restore for sysvol replication.
If the issue is not resolved , you can launch a authoritative restore.
what-happens-in-a-journal-wrap
Please dob't forget to mark helpful reply as answer

Answer 3

You'll need to do a non-authoritative restore
https://learn.microsoft.com/en-us/services-hub/health/remediation-steps-ad/investigate-file-replication-service-frs-journal-wrap-conditions-on-domain-controllers
https://learn.microsoft.com/en-US/troubleshoot/windows-server/networking/use-burflags-to-reinitialize-frs

--please don't forget to upvote and Accept as answer if the reply is helpful--

Answer 4

Hi @Anonymous

Thanks for your reply.
Do I have to do that on both domain controllers since I have the error on both ?

/R
Andy

Answer 5

Hi @Thameur-BOURBITA

Thanks for reply.

We did a non-authoritative restore for sysvol replication, but the issue is not resolved.

We did this on DC1, and now if we do "net share" the SYSVOL is not shared, and in the event log we get this message

"""""""""""""""""""""""""""
Event id 13508
The File Replication Service is having trouble enabling replication from DC2 to DC1 for c:\windows\sysvol\domain using the DNS name DC2.domain.com. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name DC2.domain.com from this computer.
[2] FRS is not running on DC2.domain.com.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
"""""""""""""""""""""""""""

From the url https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/bb727056(v=technet.10)?redirectedfrom=MSDN it say we should see 13509, but have waiting for around 30 minutes now and still no event. This is 1 site, and just 2 domain controllers, so I guess that should go quickly.

You say that if that does not work we need to perform authoritative restore. Do we do that on the same DC we tried non-authoritative restore ?

Since FRS now is not working, we only have 1 domain controller, and dont want to mess up that one so no users cant login to the domain.
For information DC1 has the FSMO roles, should I leave them there or transfer them to DC2... or does that have now impact on this problem.

Thanks for any quick reply :)

/R
Andy