May 10, 2004
Your File Replication Service event log contains 13552 and 13555 events?
Author: Rhian D. Block
rhian@vazoom.net
On a recent trip to a electrical contractor in Montomgeryville that had 2 servers (Both W2k Domain Controllers) I came across a problem relating to file replication. My first hint was actually Veritas Backup Exec which would fail its backup job because of its own local System State. The error screen below shows what Veritas output:
The event viewer on the server showed the following:
Something that caught my eye right away was the replica set root path and the replica staging directory path which pointed to files located in the D: parition of the logical drive. Problem is that the D: drive is the CD-Rom. The two partitions on the logical drive are C: and F:
Below is an article I found which fixed the problem right up. After fixing the FRS Jet Database, Veritas ran a System State backup correctly on the local machine and the FRS errors were gone in the event logs. There were a few other things I checked in Active Directory itself by use of the ADSIedit tool. This is something one would do if they wished to changed the location of the file replication staging folder to a different drive. Using the tool showed the correct location of the staging areas on the F: ... so no problem there. But I would definitely check this out too. The Microsoft article is Q291823
NOW FOR THE ARTICLE THAT FIXED THE ISSUE
For the original artical link click here
Click below to continue reading this article>
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: Error
Event Source: NtFrs
Event Category: None
Event ID: 13552
Date: 5/24/2000
Time: 3:44:57 PM
User: N/A
Computer: TEST
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 "test.Win.com"
Replica set member name is "TEST"
Replica set root path is "E:\Winnt\Sysvol\Domain"
Replica staging directory path is "E:\Winnt\Sysvol\Staging\Domain"
Replica working directory path is "O:\Winnt\Ntfrs\Jet"
Windows error status code is
FRS error status code is FrsErrorStageDirOpenFail
Event Type: Error
Event Source: NtFrs
Event Category: None
Event ID: 13555
Date: 5/24/2000
Time: 3:44:57 PM
User: N/A
Computer: TEST
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 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%\ntfrs\jet\Ntfrs.jdb
del %systemroot%\ntfrs\jet\Sys\Edb.chk
del %systemroot%\ntfrs\jet\log\edb.log
del %systemroot%\ntfrs\jet\log\res1.log
del %systemroot%\ntfrs\jet\log\res2.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.