Windows Forum

Ask something
Discussion Locked

Windows 2000 Server DFS and NTFRS

0 helpful
2 replies

by kthurston

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

we're running a dfs with a link to a server at each site. each link has a replica back at our main site on our backup server to serve as a backup to the remote site. one remote server keeps logging a series of NTFRS errors in the NTFRS Event log. 13506;13555;13502;13505;13501;13516 - in that order. I can't find any technet info on the process. I have found an article on error 13505, but the event log message that I have states that "The File Replication Service has stopped after taking an assertion failure."

because of this problem, directories inside the dfs folder on the remote server are duplicating with _NTFRS_"hex value" added onto the end. staff mapped to that directory are able to read data off the original directory, but all data writes are made to the new directory.

any clues as to what is causing this one?

2 replies

by joseph moore

Ok, here is some info from Eventid.net:

13506 - A known problem, not fixed yet. See Technet article 296776. That Technet article just referred you to another article, 307319.

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 his computer until the following recovery steps are performed. A bunch of steps that really aren't viable are listed for a Technet article that does not exist anymore! So, nothing there.13502 - The File Replication Service is stopping.

13505 - Nothing at eventid.net, but you found your own article that was not useful.

13501 - The File Replication Service is starting.

13516 - The File Replication Service is no longer preventing the computer COMPUTERNAME from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.
Type "net share" to checkfor the SYSVOL share.
This is listed as a normal message when FRS starts up.

by joseph moore

So, is ANY of that helpful? Perhaps.

The Technet article 307319 that is referenced by the first Event is very useful. The URL is here:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;307319
(please remove any spaces)

It tells about apatch for FRS that was post SP2 that took care of the problems indicated in the article.
Well, SP3 is out now.
So, I am gonna suggest up apply SP3 to all Win2K machines that are part of the DFS structure. See if the errors continue after that.

hope this helps

This discussion is closed to new replies.