JSI Tip 3605. Your File Replication Service event log contains 13552 and 13555 events?

When you inspect the File Replication Service event log on a Windows 2000 domain controller, it contains:

Event Type: ErrorEvent Source: NtFrsEvent Category: NoneEvent ID: 13552Date: 5/24/2000Time: 3:44:57 PMUser: N/AComputer: TESTDescription: 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 "test.Win.com"             Replica set member name is "TEST"             Replica set root path is "E:WinntSysvolDomain"             Replica staging directory path is "E:WinntSysvolStagingDomain"             Replica working directory path is "O:WinntNtfrsJet"             Windows error status code is             FRS error status code is FrsErrorStageDirOpenFailEvent Type: ErrorEvent Source: NtFrsEvent Category: NoneEvent ID: 13555Date: 5/24/2000Time: 3:44:57 PMUser: N/AComputer: TESTDescription: The File Replication Service is in an error state. Files will not replicate to or from one or all             of the replica sets on his computer until the following recovery steps are performed:             --------

The most likely cause of these errors is that the FRS Jet database, or a Jet database log file, is corrupt. To fix the problem:

1. Open a CMD prompt on the domain controller and stop the NetLogon and Ntfrs services:

    net stop NetLogon
    net stop Ntfrs

2. Type:

    del %systemroot%tfrsjetNtfrs.jdb
    del %systemroot%tfrsjetSysEdb.chk
    del %systemroot%tfrsjetlogedb.log
    del %systemroot%tfrsjetlogres1.log
    del %systemroot%tfrsjetlogres2.log

3. Type:

    net start NetLogon
    net start Ntfrs

4. Check the FRS event log for expected warning 13514 and 13520.

5. Close the FRS event log and go get a cup of coffee.

6. In five minutes, recheck the FRS event log for informational messages 13553, 13554, and 13516.

NOTE: See tip 3383 How do I configure the File Replication Service (NTFRS) via the registry?

NOTE: There is a high risk of data loss if the unexpected event of a bad replication occurs. All files will be moved to NtFrs_PreExisting.