NtFrs 13505 assertion failure

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am having this event repeated in my FRS log roughly every five minutes. I
also have an error id 13506 (QKey != QUADZERO)
in "QHashInsertLock:" at line 696.

Topology is three DC's two GC's.

First DC in site crashed and that's when all heck broke loose with these
errors.
I have done the d2 burflags and rebuilt Ntfrs\jet still no luck.

Ntfrs is in an error state with id 13555 as well.

TIA
James
dcdiag on problem DC passes all tests but services due to ntfrs not running.
Sysvol and Netlogon are shared and I have stopped and restarted Ntfrs
numerous times,
 
Same problem here, just investigating it ....
Any hint would be nice.
Any news will be posted ...

Regards,
dl1gbm
 
dl,
I had to do a D4 on the one dc that i knew had a good copy of the sysvol and
then do a d2 on all of the others in the domain. It wasnt' that bad and I
havent had any repl issues to date. I would suggest downloading Ultrasound
which will give you a good picture of what is going on with dc's. Let me find
the KB's and I will post them here for you. Everything you need is out there
it is just a matter of finding it. The other thing I had to do was basically
delete the sysvol structure and let the d2 rebuild it or actually repopulate
the folders. The tree structure has to stay the same but you can delete the
contents and let the burflags replicate the contents. All folders must remain
intact unless there is some kind of corruption which is what your problem
sounds like to me. I will repost with more info.
 
Hello James, hello readers,

could avoid the recent issue with dcpromo (down) and dcpromo (up
again). There is still another problem however, that synchronisation
does not work properly.

The new promoted DC2 has ESENT Error 454 and SceCli 1202 every ten
minutes. DC1 has NTFRS error 13568, will now do as proposed in the
error message....

More to come ....

Regards,
dl1gbm
(Michael)
 
Back
Top