FRS errors 13552 & 13555. SYSVOL not replicating.

Question

Hi All, looking for a little help here...
Here is the scenario. My (new) client has ONLY 1 domain controller (Windows Server 2003 which I will call SERVER1). I recently installed a new 2008 R2 server and made it a replica domain controller. Everything went well until I realised that
there was no SYSVOL share on the new server. I checked FRS event logs on SERVER1 and noticed that event ID errors 13552 & 13555 have been occuring since December 2010. 
I've been reading about changing burflags to do a nonauthorative restore from a replica DC however in this case there is only 1 DC. Can someone advise how I go about fixing this?
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13552
Date:  21/06/2011
Time:  2:15:57 PM
User:  N/A
Computer: SERVER1
Description:
The File Replication Service is unable to add this computer to the following replica set:
    "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
This could be caused by a number of problems such as:
  --  an invalid root path,
  --  a missing directory,
  --  a missing disk volume,
  --  a file system on the volume that does not support NTFS 5.0
The information below may help to resolve the problem:
Computer DNS name is "server1.mydomain.local"
Replica set member name is "SERVER1"
Replica set root path is "c:\windows\sysvol\domain"
Replica staging directory path is "c:\windows\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"
Windows error status code is 
FRS error status code is FrsErrorMismatchedJournalId 
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13555
Date:  21/06/2011
Time:  2:15:57 PM
User:  N/A
Computer: SERVER1
Description:
The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed: 

Answer 1

Hi CURNS, thanks for the replies. Yes, it works in below scenario (Replication from 2003 to 2008).
There was only 1 copy of sysvol, and it was on the old DC. The new DC has not yet shared or replicated sysvol thus making the burflag D2 option a no go. I first had to fix whatever the issue was with the old DC before the new one would replicate.
I fixed replication issue with 4 easy steps:
1. stopped the FRS service on both DCs (old and new)
2. set burflag on old DC to D4 (to tell it its the boss)
To configure the SYSVOL replica set to be authoritative, follow these steps:
Click Start, click Run, type regedit, and then click OK.
Locate and then click the BurFlags entry under the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Cumulative
Replica Sets\GUID
GUID is the GUID of the domain system volume replica set that is shown in the following
registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Replica
Sets\GUID
Right-click BurFlags, and then click Modify.
Type D4 in the Value Data field (HexaDecimal), and then click OK.
3. restarted FRS service on old DC.
4. restarted FRS service on new DC.
After this I could see event logs saying FRS was now working and I confirmed sysvol and netlogon shares now existed on the new DC using net share command.
Thanks.