Discussion:
The File Replication Service has stopped after taking an assertion failure.
(too old to reply)
sasa
2006-04-04 18:52:15 UTC
Permalink
We have been having problems with DFS replication between 4 DFS
servers. Windows 2003 sp1. Now the main DFS server is giving error "The
File Replication Service has stopped after taking an assertion
failure."
Please help.
Ned Pyle (MSFT)
2006-04-04 20:40:25 UTC
Permalink
Hi Sasa,

Based on the error description (I'll wager you are also seeing in the 13505
event something like "(QKey != QUADZERO)" ?) you are going to want to open a
case with MS. We are going to want to have NTFRS debug logging cranked up to
a very verbose setting to see what's going on. The Engineer will also want
to give you the latest post SP1 version of NTFRS.EXE scheduled for SP2, as
this issue is frequently fixed in various builds of the service (combined
with a database reset using BURFLAGS).

Without a case, you can't get the hotfix, which is why I recommend you call
in.

Ned
Post by sasa
We have been having problems with DFS replication between 4 DFS
servers. Windows 2003 sp1. Now the main DFS server is giving error "The
File Replication Service has stopped after taking an assertion
failure."
Please help.
sasa
2006-04-05 13:04:04 UTC
Permalink
Thanks.

We actually performed a non authorative restore on sysvol yesterday and
FRS is now working except DFS now has moved some folders and files into
NTFRS_PreExisting which I don''t know how to fix.
Ned Pyle (MSFT)
2006-04-06 13:19:48 UTC
Permalink
Looks like you cut right to the case on BURFLAGS. :) If the issue recurrs,
definitely give us a call for a case - we've seen this before, and non-auth
restore may only be a temporary reprieve.

The NTFRS_PreExisting folder is created when you do a non-auth restore, and
holds all the files that previously existed in the folder structure. As FRS
starts back up in D2 mode, it sends information about each file it has in
PreExisting to its partner server - this way if the files are unchanged, it
can just pull the file out of PreExist and put it back where it belongs,
instead of copying the whole thing over the wire again. Once all is said and
done and the FRS event log shows a 13516 saying it's working again, there
shouldn't be anything left in pre-existing.

Ned
Post by sasa
Thanks.
We actually performed a non authorative restore on sysvol yesterday and
FRS is now working except DFS now has moved some folders and files into
NTFRS_PreExisting which I don''t know how to fix.
Loading...