We help IT Professionals succeed at work.

FRS replication warnings on all DC`s in domain

Medium Priority
Last Modified: 2012-06-21
we have the same FRS event warning on all of our DC`s:

there mostly event ID. 13508 and 13567 showing up.

how can i fix this problem?
Watch Question

Every 5 minutes on a domain controller, or every 20 minutes on a member server, your Event log records:

Userenv 1000
Windows cannot access the registry information at
{ file://\\<domainname.com>\sysvol\<domainname.com>\Policies\
{31B2F340-016D D-11D2-945F-00C04FB984F9}\Machine\registry.pol with (1398).

SceCli 1001
Security policy cannot be propagated. Cannot access the template. Error code=3.

Userenv 1000
The Group Policy client-side extension Security was passed flags (17) and returned a failure status code of (3).

NtFrs 13508
Description: The File Replication Service is having trouble enabling replication from <computername>
to <computername> for c:\winnt\sysvol\<domain>; retrying.To resolve this problem, synchronize the computer's clock with the domain controller that is the authoritative time server.
For each server that is experiencing this difficulty, open a CMD prompt and type:

net time \\ComputerName_Of_Authoritative_Time_Server /set /y
net stop ntfrs
net start ntfrs


it works,at least for now. i hope this fixes it forevermore and not to be a workaround.

You DNS, IP, and time stuff needs to be perfect.  If you get a 13568 on the DC that is trying to replicate, then you have JRNL_WRAP_ERROR which can be fixed this way (per Microsoft):

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:\winnt\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.
Click down the key path:
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.

Explore More ContentExplore courses, solutions, and other research materials related to this topic.