Server 2012R2 Sysvol replication failing
Hi
I have a Server 2012r2 active directory domain with two DCs. I recently added a GPO and started having sporadic issues with the settings being applied to computers. I noticed the folder containing the policies on one DC had not replicated to the other DC. Event viewer is showing the below error.
I have found many suggestions as to how to fix this but would like some clarification as to how to proceed. The below suggestion to "Enable Journal Wrap Automatic Restore" seems easy enough but I have found blogs stating that this could potentially make the issue worse. I am also finding the solution of performing a non-authoritative restore by changing the burflag key to D2 on the DC having the error message. Will this sync from the other DC and if so does this overwrite what is on the failed DC? I ask because the failed DC is the one containing the new policy.
Any help will be appreciated.
Log Name: File Replication Service
Source: NtFrs
Date: 3/11/2015 8:11:13 PM
Event ID: 13568
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: contoso.com
Description:
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\
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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="NtFrs" />
<EventID Qualifiers="49152">13568</
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2015-03-12T03:
<EventRecordID>31</EventRe
<Channel>File Replication Service</Channel>
<Computer>contoso.com</Com
<Security />
</System>
<EventData>
<Data>DOMAIN SYSTEM VOLUME (SYSVOL SHARE)</Data>
<Data>c:\windows\sysvol\do
<Data>\\.\C:</Data>
<Data>5</Data>
</EventData>
</Event>
I have a Server 2012r2 active directory domain with two DCs. I recently added a GPO and started having sporadic issues with the settings being applied to computers. I noticed the folder containing the policies on one DC had not replicated to the other DC. Event viewer is showing the below error.
I have found many suggestions as to how to fix this but would like some clarification as to how to proceed. The below suggestion to "Enable Journal Wrap Automatic Restore" seems easy enough but I have found blogs stating that this could potentially make the issue worse. I am also finding the solution of performing a non-authoritative restore by changing the burflag key to D2 on the DC having the error message. Will this sync from the other DC and if so does this overwrite what is on the failed DC? I ask because the failed DC is the one containing the new policy.
Any help will be appreciated.
Log Name: File Replication Service
Source: NtFrs
Date: 3/11/2015 8:11:13 PM
Event ID: 13568
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: contoso.com
Description:
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\
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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="NtFrs" />
<EventID Qualifiers="49152">13568</
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2015-03-12T03:
<EventRecordID>31</EventRe
<Channel>File Replication Service</Channel>
<Computer>contoso.com</Com
<Security />
</System>
<EventData>
<Data>DOMAIN SYSTEM VOLUME (SYSVOL SHARE)</Data>
<Data>c:\windows\sysvol\do
<Data>\\.\C:</Data>
<Data>5</Data>
</EventData>
</Event>
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The domain was upgraded from a 2003 domain. I did also notice the error is listed under 'File Replication Service' versus DFS Replication. Does this change the potential fix?
In troubleshooting teh issue I have viewed several KBs about moving from FRS to DFSR. Is this an upgrade i could do in the state replication is now? Assuming no if I perform the recommended fix per the event can i do this during production hours?
In troubleshooting teh issue I have viewed several KBs about moving from FRS to DFSR. Is this an upgrade i could do in the state replication is now? Assuming no if I perform the recommended fix per the event can i do this during production hours?
You have to follow the directions in the error to reset the journal. Once you restart netlogon, or ...., you should change the registry entry back to 0.
Once this issue us cleared up, you can/should transition away from having NTFRS handling the replication of sysvol.
Once this issue us cleared up, you can/should transition away from having NTFRS handling the replication of sysvol.
ASKER
Can I perform the fix during production or will this take network services offline?
You have two dcs, the system on which this error is display is not serving, net share is sysvol listed there.
Make sure the other dc has sysvol published (net share)
I think the process is between 5 and 10 minutes before sysvol is reshared on this system.
Yes, the sysvol is used in login and GPO/.......scripts,
If you are more comfortable, run this later on, but make sure as soon as you trigger the reconstruct the journal, change the registry value back to 0 and wait until sysvol is reshared.
Make sure the other dc has sysvol published (net share)
I think the process is between 5 and 10 minutes before sysvol is reshared on this system.
Yes, the sysvol is used in login and GPO/.......scripts,
If you are more comfortable, run this later on, but make sure as soon as you trigger the reconstruct the journal, change the registry value back to 0 and wait until sysvol is reshared.
ASKER
Both DCs are showing Sysvol as shared. Is there a way to confirm that the second DC or the one that does not have the newly created GPO in Sysvol folder is sharing Sysvol information?
ASKER
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\
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.
[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\
Double click on the value name
"Enable Journal Wrap Automatic Restore"
and update the value.
not by default if the domain was upgraded to 2012R2... it still might be FRS... and you have to prepare to upgrade to DFSR jus the SYSVOL replication....