Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

Troubleshooting
Research
Professional Opinions
Ask a Question
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

troubleshooting Question

FRS Event ID 13568

Avatar of nmmcfk
nmmcfkFlag for United States of America asked on
Windows Server 2003Windows Server 2008
42 Comments1 Solution1262 ViewsLast Modified:
Hi all,

I recently promoted a 2008 server in my 2003 AD to act as a redundant DC. Everything went fine during the promotion and all but I have a problem with my file replication. On my original 2003 server DC, I get the event ID 13568:

Event Type:      Error
Event Source:      NtFrs
Event Category:      None
Event ID:      13568
Date:            2/23/2010
Time:            6:31:07 AM
User:            N/A
Computer:      NMMC-DC
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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.




And my 2008 server obviously I get Event ID's that the RFS does not replicate. Event ID 13508:


Log Name:      File Replication Service
Source:        NtFrs
Date:          2/23/2010 6:33:20 AM
Event ID:      13508
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      FILE-BK.NMMC-NET.local
Description:
The File Replication Service is having trouble enabling replication from nmmc-dc.NMMC-NET.local to FILE-BK for c:\windows\sysvol\domain using the DNS name nmmc-dc.NMMC-NET.local. FRS will keep retrying.
 Following are some of the reasons you would see this warning.
 
 [1] FRS can not correctly resolve the DNS name nmmc-dc.NMMC-NET.local from this computer.
 [2] FRS is not running on nmmc-dc.NMMC-NET.local.
 [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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="NtFrs" />
    <EventID Qualifiers="32768">13508</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2010-02-23T11:33:20.000Z" />
    <EventRecordID>98</EventRecordID>
    <Channel>File Replication Service</Channel>
    <Computer>FILE-BK.NMMC-NET.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>nmmc-dc.NMMC-NET.local</Data>
    <Data>FILE-BK</Data>
    <Data>c:\windows\sysvol\domain</Data>
    <Data>nmmc-dc.NMMC-NET.local</Data>
    <Binary>D5040000</Binary>
  </EventData>
</Event>



Thanks in advance
ASKER CERTIFIED SOLUTION
Avatar of abolinhas
abolinhasFlag of Portugal image

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Commented:
This problem has been solved!
Unlock 1 Answer and 42 Comments.
See Answers