2006-03-27 05:26:02 UTC
folders between our branch offices (8). Each branch has a DC and is properly
configured in DNS and Sites. This all worked until recently when one or two
replicas would spew 13508 and 13506 errors until I ran a D2 restore.
All would be fine for a few days and then it would start again. The 13506
assertion message complains about a failed consistency check
(!IS_GUID_ZERO(ChangeOrder->pParentGuid)) in ChrgOrderAccept at line 2373.
The error has appeared on several, but not all replicas.
Replication is set to run during our non-production hours (overnight) and
has plenty of time to complete. We are below all the stated limits of
DFS/FRS, although I am aware that replicating roaming profiles and redirected
folders is not supported as we have it configured.
Sysvol/AD replication is working fine (and has always worked). I have
tested by placing a text file in each of the DCs sysvol and it does appear in
the other DCs folders during the next window. Sonar tells me that everything
is fine with the exception that ntfrs is usually failed on the problem
Repadmin, dcdiag, netdiag, and dns troubleshooting tools all indicate no
problems, except of course ntfrs is not running on the current problem
Restarting ntfrs manually doesn't help either. The service manager is
restarting at regular intervals too. Ntfrs will run for less than one minute
before failing on assertion.
I've looked through the ntfrs_nnnn.log debug files and am simply overwhelmed
by the volume of information (a tool to parse this would be handy). Using
grep to search for error|access|fail doesn't produce any clues to the problem.
Finally, even with the failures; most of the content would replicate
successfully. However, *most* of the data being replicated is not good
I've disabled replication this weekend and hacked together a robocopy script
to keep things moving between targets until I can figure this out.
Anyone have any pointers, tips, or suggestions on getting this solved?