Event ID 13568 Source Ntfrs File Replication

I am working as an IT Professional with two different companies but sometime some issues occurs on both locations and you are unable to get the cause that why it happens on both different locations on same day but today I got an Error in Events and that was like as under;

 EVENT ID 13568 Source NtFrs

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.
Instead of any blah blah discussion, here is the solution

Solution 1: (Recommended)


Solution 2: Worked Sometimes;

1. Expand "HKLM\System\CurrentControlSet\Services\NtFrs\Parameters"
2. Change value for "Enable Journal Wrap Automatic Restore" from 0 to 1.
[If the DWORD Value does not exist, create a new one with the exact spelling as above, including spaces but without the quotes.]
3. Stop the NTFRS Service (open a command prompt and type "net stop ntfrs")
4. Start the NTFRS Service (net start ntfrs)
5. Monitor the File Replication Service Event Logs for events:

Event ID 13553 – The DC is performing the recovery process
Event ID 13554 – The DC is ready to pull the replica from another DC.
Event ID 13516 - At this point go to step 6. (the problem is resolved if you receive this event)

6. Using a command prompt type: "net share" and look for the Netlogon and Sysvol Shares to appear.
The Journal Wrap error is only fixed after the Domain Controller receives the new SYSVOL replica from a peer Domain Controller. This may take a period of time depending on where your peer DC is located and on bandwidth.
7. Change value for "Enable Journal Wrap Automatic Restore" from 1 to 0.


Get Socially Engaged with IP Address and Host Team !