Home | Site Map | How To | Windows Vista | Case Studies | Articles | Forums | Services | Donations | Careers | About Us | Contact Us|

Event ID: 13550, 13552 and 13555 - The File Replication Service errors

FRS problem because of low space

Symptoms: 1. On Distributed File System (DFS) replica members or domain controllers that are hosting a SYSVOL replica set, you may find an event that is similar to the following in Event Viewer:

Event ID: 13552 - The File Replication Service is unable to add this computer to the following replica set: "DFS_DOMAIN_ROOT|BIN"
Windows error status code is FRS error status code is FrsErrorJournalInitFailed

Or/and

Event ID: 13555 - 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:

Or/and

Event ID: 13559 - The File Replication Service has detected that the replica root path has changed from "c:\bin" to "c:\bin". If this is an intentional move then a file with the name NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path. This was detected for the following replica set: "DFS_DOMAIN_ROOT|BIN".

2. Your have FRS issue after upgrading Windows 2000 DC to 2003 DC

3. Logon script doesn't run after logon the domain.

Cause: After you have applied 811370 (http://support.microsoft.com/kb/811370/EN-US/) hotfix - Issues That Are Fixed in the Post-Service Pack 3 Release of Ntfrs.exe, the Windows server may not have sufficient free space (at lease 512 MB) to contain the journal file, the USN Journal cannot initialize; therefore, it logs the above events in Event Viewer.

Resolution: You may have three options to fix this issue.

1. Delete Files to Create Additional Disk Space.
2. Move the File Replication Service Staging Folder.
3. Set the USN Journal Size Back to 128 MB

Related Topics

FRS Tools

Troubleshooting Windows Event ID errors
Upgrade 2000 DC to 2003 DC Issues
Move FRS Staging Folder
Set USN Journal Size to 128 MB