|
Noah,
Is it possible that there were more DC (s) which existed in the past and weren’t properly DCPromo’d down (like an old DC which was just turned off).
Also, is SYSVOL sharing out on this DC? You can look for an Event 13516 in the FRS event log or just go to a command prompt and type “net share” and look for SYSVOL.
If there were more DC’s in the past, then there are a few things to do to “clean up”.
Let us know if you see other computer objects in the Domain Controllers OU or in Active Directory Sites and Services…
Good Luck…Merry Merry, Happy Happy right back at ya J
Rob From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Noah Eiger
Hi –
Merry merry, happy happy everyone.
I have inherited a single DC network (W2k SP4) that is spitting out NTFRS errors (ID 13568) every time the server (or service) restarts. Several online sources give instructions for, what appears to be, forcing synchronization. However, in this case, there is nothing with which to synchronize.
My questions are: with a single DC, how could I be getting this error? And, is there anything I need to do about this error? Does it really indicate corruption in the SYSVOL?
Thanks.
-- nme |
- [ActiveDir] JRNL_WRAP_ERROR with Single DC Noah Eiger
- RE: [ActiveDir] JRNL_WRAP_ERROR with Single D... David Adner
- RE: [ActiveDir] JRNL_WRAP_ERROR with Sing... Noah Eiger
- RE: [ActiveDir] JRNL_WRAP_ERROR with Single D... Myrick, Todd (NIH/CIT)
- RE: [ActiveDir] JRNL_WRAP_ERROR with Single D... Robert Williams \(RRE\)
- RE: [ActiveDir] JRNL_WRAP_ERROR with Single D... Peter Johnson
