Event submitted by eNTen Juergen
Event ID:

Event Type: Warning
Event Source: NtFrs
Event Category: None
Event ID: 13565
Date: 10.03.2005
Time: 18:09:24
User: N/A
Computer: xxxx
File Replication Service is initializing the system volume with data from another domain controller. Computer XXXX-CB01 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.

Solution by eNTen Juergen

2005-03-11 00:44:13 UTC

1. Stop the File Replication service on the domain controller.
2. Start Registry Editor (Regedt32.exe).
3. Locate and then click the BurFlags value under the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
4. On the Edit menu, click DWORD, click Hex, type D4, and then click OK.
5. Quit Registry Editor.
6. Move data out of the PreExisting folder.
7. Restart the File Replication Service.
Note This registry value marks the FRS replica as authoritative for the whole replica set. Set this value on only one replica, and only to resolve this specific issue. If you configure multiple replicas as authoritative, conflicts and collisions may occur in the replica set.

When you set the D4 registry setting on one domain controller, you must set the D2 registry setting on every other domain controller.

User Information
Only an Email address is required for returning users.

Hide Name


Additional Links