Consider the following scenario. You try replicate files between a Microsoft Windows Server 2003-based domain controller and another Microsoft Windows-based domain controller.
On the Windows Server 2003-based domain controller, events that resemble the following are logged in the File Replication Service (FRS) log.
Back to the top
Event 1
Type: Error
Event ID: 13555
Source: NtFrs
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: Recovery Steps:
[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window: net stop ntfrs net start ntfrs
If this fails to clear up the problem then proceed as follows.
[2] For Active Directory Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled: If there is at least one other Domain Controller in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative. If there are NO other Domain Controllers in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary. If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
[3] For Active Directory Domain Controllers that host DFS alternates or other replica sets with replication enabled:
(3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
(3-b) If this server is the only Active Directory Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
(3-c) Restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
(3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
[4] For other Windows servers:
(4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q c:\windows\ntfrs\jet
(4-d) net start ntfrs
(4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time). Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members.
Back to the top
Event 2
Type: Error
Event ID: 13552
Source: NtFrs
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 "DC1.contoso.com" Replica set member name is "DC1" 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 Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time.
In this scenario, you cannot replicate files on the Windows Server 2003-based domain controller that contains these entries.
Back to the top
This problem occurs when a file ID for data in the FRS database does not match the file ID for the data in the update sequence number (USN) journal database.
Back to the top
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/) How to back up and restore the registry in Windows
To work around this problem, restore the SYSVOL data from a domain controller that can replicate files to the domain controller that cannot replicate files. Use the non-authoritative method to restore this data. For more information about how to rebuild SYSVOL data, click the following article number to view the article in the Microsoft Knowledge Base:
315457 (http://support.microsoft.com/kb/315457/) How to rebuild the SYSVOL tree and its content in a domain
To back up and restore the SYSVOL data, follow these steps:
| 1. |
Back up the following folders in a temporary location that is not in the SYSVOL folder:
| • |
%SystemRoot%\SYSVOL\Domain\Policies |
| • |
%SystemRoot%\SYSVOL\Domain\Scripts |
Note To retain the permissions for these folders, back up these folders in a location that is on the same volume as the SYSVOL folder. |
| 2. |
Perform a non-authoritative restore on this replica set. To do this, follow these steps:
| a. |
Click Start, click Run, type cmd, and then click OK. |
| b. |
At the command prompt, type the following command, and then press ENTER:
net stop ntfrs |
| c. |
Click Start, click Run, type regedit, and then click OK. |
| d. |
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup |
| e. |
Right-click the BurFlags entry, and then click Modify. |
| f. |
In the Value data box, type D2, and then click OK. |
| g. |
On the File menu, click Exit. |
| h. |
At the command prompt, type the following command, and then press ENTER:
net start ntfrs | |
Back to the top
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top
For more information about using the BurFlags registry key, click the following article number to view the article in the Microsoft Knowledge Base:
290762 (http://support.microsoft.com/kb/290762/) Using the BurFlags registry key to reinitialize File Replication Service replica sets
Back to the top
