DC Not replicating Sysvol

[RabbieBurns]

One of my DC's has stopped replicating the Sysvol share.

 

The instructions in the error log to fix Ive tried and it doesn't seem to have had any effect:

 

Log Name:      File Replication Service
Source:        NtFrs
Date:          24/04/2013 4:16:26 PM
Event ID:      13568
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:    DC5.
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\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.

 

Ive set the reg value back to 0 for now (had to create the key) but cant find any other solutions to this. Any ideas folks?

[pete]

Ignore the event log recommendations - they're broken and can cause more problems, see below for why:

 

Friday Mail Sack: Scooter Edition - Ask the Directory Services Team - Site Home - TechNet Blogs

 

That'll point you here: How to troubleshoot journal_wrap errors on Sysvol and DFS replica sets (says 2K, but it shows why it's happening)

 

The following are appropriate options to reduce journal wrap errors:

 

Put the FRS-replicated content on less busy volumes.

Keep the FRS service running.

Avoid making changes to FRS-replicated content while the service is turned off.

Increase the USN journal size.

 

Additionally, if you've 2008 DCs and haven't migrated SYSVOL to DFS-R (and it looks like you haven't), read this: The Case for Migrating SYSVOL to DFSR - Ask the Directory Services Team - Site Home - TechNet Blogs

[RabbieBurns]

Wow I didn't even know about that upgrade. I just upgraded through to 2008R2 over the years, raising the functional level as we went.

 

I will have to have a good read at this and start some planning. Thanks.

[pete]

Yeah, a fresh 2008 domain with do it by default, if you've come up from 2003 or earlier it's something you need to turn on - there's a fair few things like that and it's worth poking around the AskDS blog and AskPFE blog because they often post about things that make your network more reliable.

[SYNACK]

Wow I didn't even know about that upgrade. I just upgraded through to 2008R2 over the years, raising the functional level as we went.

 

I will have to have a good read at this and start some planning. Thanks.

 

It's little stuff like that that you can miss unless you are going to all the events and training or participate in an active community like this one. I had.

[mac_shinobi]

Not that it helps with your issue as per @pete 's post but found the below link and thought it may help a little bit. If you have seen or come across it already then will leave you to it and stay subscribed.

 

http://blogs.technet.com/b/askds/archive/2010/11/01/common-dfsr-configuration-mistakes-and-oversights.aspx

 

Thanks :-)

[RabbieBurns]

It seems there are a load of problems with one of the DCs. Going to demote it and re-promote it to try to resolve these issues before migrating to DFS.

[RabbieBurns]

demoted it, re-promoted it. Upgraded to DFS. All back to normal.