Active Directory - JRNL_WRAP_ERROR on one domain controller

Technical Information: Windows 2003 forest and all domains are operating at a 2003 functionally level.

Discovered that in one of my domains, I am receiving an error / event ID: 13568. Which says "The file replication service has detected the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE) is in JRNL_WRAP_ERROR."

The domain has two domain controllers (Lets just say DC1 & DC2). Back on 10.2.2013, is when this error in my event viewer first showed up on DC1. On the same day, DC2 is reporting that it can no longer replicate with DC1. DC2 has the PDC and RID manager role. DC1 is the infrastructure master.

My question is: If I set the BurFlags on DC1 to D2, will it restore correctly from DC2? On DC2, I cannot see the SYSVOL or NETLOGON share. I can only see this on DC1.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Miguel Angel Perez MuñozCommented:
When JRNL_WRAP_ERROR on DC1 occurs, replication stops between both dc´s. On a common scenario simply doing a sysvol non-authoritative restoration ( to recover normal situation.
But you must to see sysvol on DC2, since you have not got sysvol on dc2 something is failing on this dc and stops domain controller functions.
Have you try rebooting DC2?

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
ACCESS2008Author Commented:
Thank you for the comment Miguel.

 I have rebooted DC2 multiple times but this does not seem to resolve anything. Is there something I should look for on DC2 to help me identify what may be happening? I seem to be stuck in a loop where I cannot do a non-authoritative restore because the other domain controllers are not serving off the sysvol and netlogon shares.
DrDave242Senior Support EngineerCommented:
You should look through the SYSVOL folders on both DCs to determine which one has the most up-to-date copy and set BurFlags to D4 (authoritative) on that one. If the SYSVOL and NETLOGON shares appear, set BurFlags to D2 on the other DC. If the SYSVOL and NETLOGON shares don't appear on the authoritative DC, there's no point in doing anything to the other one until you get that sorted out, which will likely involve a trip through the event logs.
ACCESS2008Author Commented:
I was able to resolve this,
As suggested by Dave, I ended up setting the BurFlags to D4 on my 2nd domain controller (DC2) as that seemed to have the most up-to-date content. I than set the rest to D2 and restarted all the services. After a few minutes my SYSVOL and NETLOGON shares were present on each domain controller followed by event ID: 13516 which states that the file replication service is no longer preventing the computer <DC2> from becoming a domain controller.

 Thanks for all the help!
DrDave242Senior Support EngineerCommented:
It isn't that big a deal, but since you followed my suggestion, shouldn't I get some of the points?
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
Active Directory

From novice to tech pro — start learning today.