SYSVOL not replicating from PDC to BDC

I have small Windows 2003 Server network and I recently added a BDC to it. For a long time the BDC never worked. If the PDC wasn't availible, my clients could not logon. I then looked into the event viewer and found these two events in the File Replication section:

Event Type:     Warning
Event Source:     NtFrs
Event Category:     None
Event ID:     13565
Date:          9/10/2005
Time:          7:08:55 AM
User:          N/A
Computer:     MAIN7
Description:
File Replication Service is initializing the system volume with data from another domain controller. Computer MAIN7 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
 
To check for the SYSVOL share, at the command prompt, type:
net share
 
When File Replication Service completes the initialization process, the SYSVOL share will appear.
 
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
----------------------------------------------------------------------------------------------------
Event Type:     Warning
Event Source:     NtFrs
Event Category:     None
Event ID:     13508
Date:          9/10/2005
Time:          7:14:45 AM
User:          N/A
Computer:     MAIN7
Description:
The File Replication Service is having trouble enabling replication from MAIN to MAIN7 for c:\windows\sysvol\domain using the DNS name main.HOME.HOME. FRS will keep retrying.
 Following are some of the reasons you would see this warning.
 
 [1] FRS can not correctly resolve the DNS name main.HOME.HOME from this computer.
 [2] FRS is not running on main.HOME.HOME.
 [3] The topology information in the Active Directory 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.

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


I then looked at the PDC and found thses events in the same section:

Event Type:     Error
Event Source:     NtFrs
Event Category:     None
Event ID:     13568
Date:          9/10/2005
Time:          10:45:41 AM
User:          N/A
Computer:     MAIN
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.
----------------------------------------------------------------------------------------------------
I also get this on the PDC

Event Type:     Warning
Event Source:     NtFrs
Event Category:     None
Event ID:     13562
Date:          9/8/2005
Time:          5:33:50 AM
User:          N/A
Computer:     MAIN
Description:
Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller main.HOME.HOME for FRS replica set configuration information.
 
 Could not bind to a Domain Controller. Will try again at next polling cycle.


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


I have tried everything and I don't know what to do. I cannot find information on my specific problem.