Thanks for the reply. I did see some of the topics covering this, but they all seemed to cover situations where there were several DCs functioning.
The newer DC was built about 1 year ago, but it never synced correctly and was powered down for over 60 days at a time. Since this is a very small, basic setup, there are no fancy or custom GPs or special groups. The problem is that no one really knows much about the infrastructure since so many people have hacked at it over the past 2 years.
Since the offline DC has never fully replicated with the original one, at what point in the seizure does it create its own sysvol?
I would prefer to resolve the journal issue if possible. My confusion is how to do it without a good DC to restore from?
Thanks again,
Aaron
On 9/6/06, Akomolafe, Deji <[EMAIL PROTECTED]> wrote:
how old is the offline DC? Does the online DC have a LOT of things (beside FSMO) that you need to sync with the offline DC? I mean, are there are lot of objects that have been created on the online DCs that have not been replicated to the offline?IF all you want to do is transfer FSMO, I'd just turn off this problematic DC, bring up the offline (known good) DC and do a FSMO roles seizure.If you still want to go through journal wrap troubleshooting, let us know. I have a couple of references to give you. You can also search this list's archives because journal wrap has been discussed to death here on several occassions.
Sincerely,
_____
(, / | /) /) /)
/---| (/_ ______ ___// _ // _
) / |_/(__(_) // (_(_)(/_(_(_/(__(/_
(_/ /)
(/
Microsoft MVP - Directory Services
www.akomolafe.com - we know IT
-5.75, -3.23
Do you now realize that Today is the Tomorrow you were worried about Yesterday? -anon
From: Aaron Burg
Sent: Wed 9/6/2006 10:03 PM
To: ActiveDir@mail.activedir.org
Subject: [ActiveDir] NTFRS - Journal Wrap Errors
Hi-I am new to the list and was hoping someone could help with an ugly situation I was brought in to clean up:I am working with a W2K native mode domain with only ONE active domain controller (W2K SP4). There is a second DC, but it was brought on-line after the journal wrap errors (Event 13568 ) began and has never replicated sysvol (doesn't even exist on the box). It appears AD and such are working with the new DC... just not NTFRS.The original DC does have sysvol and appears to be working to authenticate clients as normal. I need to get the journal wrap errors resolved so I can bring the second DC on-line, transfer FSMO roles and get the old box rebuilt since it doesn't even have redundant drives - Yikes!Everything I have read says to do a D2 non-authoritative restore, but since I only have the one DC, where would it restore from? I have run an NT backup of c:\ and system state to try and get some comfort, but still am afraid of making matters worse.Any suggestions/recommendations would be very much appreciated...I would like to get this cleaned up this week!Thanks so much,Aaron
