Server 2003 NTFRS problem

I have a 2003 server that has had the  Journal Wrap Error for quite some time. I have hit that error before on other servers and simply changing the registry entry in Ntfrs\Parameters\EnableJournalWrapAutoRestore fixes the problem but on this server it didn't. It actually trashed out the domain and made it inaccessible.

   DCDiag and NetDiag say everything is fine. I started playing with Burflags, The D2 Burflag didn't do anything. The D4 finally said that the sysvol is now shared and no longer preventing the server from becoming a domain controller but at that point the Scripts and Policies folders were gone and it was a mess. I do have an image backup so I am restored to the point where the server works but still has the Ntfrs error. Based on the above does anyone have and insight on how to correct this error?
LVL 15
LockDown32OwnerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MaheshArchitectCommented:
You have done this wrongly
If your sysvol is corrupted on all DCs, then only you should attempt D4 on PDC and followed by D2 on other ADCs
1st of all if the problem server is PDC, then you should not use D2 in 1st place.
In that case you should 1st transfer FSMO roles to other healthy server and then you can try D2 on problem server
Further If D2 burgflag didn't help, you should not use D4 on same server
What you are telling the server that now you are the authoritative server for sysvol and since this server already have issues, you got in mess

Now I can see only one way to resolve the issue
If all of your DCs are facing sysvol issue, then 1st attempt D4 on PDC and followed by D2 on other DCs, if this is not the case then,

Check your PDC server or any other healthy server where sysvol and netlogon status is OK
Run Net Share from command prompt to ensure that sysvol and netlogon are shared out
Also run dcdiag /test:sysvolcheck and dcdiag /test:netlogons on that dc and verify if those tests are OK
Then restart NTFRS service on that DC and check if you are getting 13516 event id in frs event logs on same server

Now if this is PDC, its fine, otherwise make this server PDC by transferring FSMO roles from existing PDC

Then attempt D2 burgflag on problematic by pointing it to PDC, I am not able to recollect exact registry to point it to PDC from getting Sysvol
https://support.microsoft.com/en-us/kb/290762

If still you get errors, The last option could be demote problematic DC gracefully / forcefully if you get errors by running dcpromo /forceremoval and then remove metadata entries
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
LockDown32OwnerAuthor Commented:
I had to read about 6 articles because none of them explained it well. It was pretty simple. D4 for single controller. It is as simple as that and worked.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.