I am trying to get a Windows 2003 SBS SP1server to replicate to a newly\nadded Server 2003 SP2 Domain Controller. Replication has stalled. The\nsource server has the following error in the File Replication Service Event\nLog:\n\nEvent Type: Error\nEvent Source: NtFrs\nEvent Category: None\nEvent ID: 13568\nDate: 05/08/2008\nTime: 12:32:41 PM\nUser: N/A\nComputer: HPS001\nDescription:\nThe File Replication Service has detected that the replica set "DOMAIN\nSYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.\n\nReplica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"\nReplica root path is : "c:\windows\sysvol\domain"\nReplica root volume is : "\\.\C:"\nA Replica set hits JRNL_WRAP_ERROR when the record that it is trying to\nread from the NTFS USN journal is not found. This can occur because of one\nof the following reasons.\n\n Volume "\\.\C:" has been formatted.\n The NTFS USN journal on volume "\\.\C:" has been deleted.\n The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can\ntruncate the journal if it finds corrupt entries at the end of the journal.\n File Replication Service was not running on this computer for a long\ntime.\n File Replication Service could not keep up with the rate of Disk IO\nactivity on "\\.\C:".\nSetting the "Enable Journal Wrap Automatic Restore" registry parameter to 1\nwill cause the following recovery steps to be taken to automatically recover\nfrom this error state.\n At the first poll, which will occur in 5 minutes, this computer will be\ndeleted from the replica set. If you do not want to wait 5 minutes, then run\n"net stop ntfrs" followed by "net start ntfrs" to restart the File\nReplication Service.\n At the poll following the deletion this computer will be re-added to\nthe replica set. The re-addition will trigger a full tree sync for the\nreplica set.\n\nWARNING: During the recovery process data in the replica tree may be\nunavailable. You should reset the registry parameter described above to 0 to\nprevent automatic recovery from making the data unexpectedly unavailable if\nthis error condition occurs again.\n\nTo change this registry parameter, run regedit.\n\nClick on Start, Run and type regedit.\n\nExpand HKEY_LOCAL_MACHINE.\nClick down the key path:\n"System\CurrentControlSet\Services\NtFrs\Parameters"\nDouble click on the value name\n"Enable Journal Wrap Automatic Restore"\nand update the value.\n\nIf the value name is not present you may add it with the New->DWORD Value\nfunction under the Edit Menu item. Type the value name exactly as shown\nabove.\n\nFor more information, see Help and Support Center at\n[URL]http://go.microsoft.com/fwlink/events.asp[/URL].\n\nThis server had a crash recently and CHKDSK found errors on the disk The\nserver seems healthy except for the above errors\n\nI made the suggested registry entry and stopped and started the service but\nit has not fixed the error.\n\nThe destination server has the following error (multiple times) in the File\nReplication Service Event Log:\n\nEvent Type: Warning\nEvent Source: NtFrs\nEvent Category: None\nEvent ID: 13508\nDate: 5/08/2008\nTime: 1:30:43 PM\nUser: N/A\nComputer: MIGRATIONDC\nDescription:\nThe File Replication Service is having trouble enabling replication from\nHPS001 to MIGRATIONDC for c:\windows\sysvol\domain using the DNS name\nHPS001.herzigprosser.local. FRS will keep retrying.\nFollowing are some of the reasons you would see this warning.\n\n FRS can not correctly resolve the DNS name HPS001.herzigprosser.local\nfrom this computer.\n FRS is not running on HPS001.herzigprosser.local.\n The topology information in the Active Directory for this replica has\nnot yet replicated to all the Domain Controllers.\n\nThis event log message will appear once per connection, After the problem\nis fixed you will see another event log message indicating that the\nconnection has been established.\n\nFor more information, see Help and Support Center at\n[URL]http://go.microsoft.com/fwlink/events.asp[/URL].\nData:\n0000: d5 04 00 00 Õ...\n\nNot sure where to go from here. Anyone?