FRS - The File Replication Service has detected that the replica set "Domain System Volume SYSVOL SHARE)

Hi all,

Quick overview (Domain Functional Level: 2008, Forest Functional Level: 2008)

the client has 2 domain controllers (DC1 and DC2 both running Windows Server 2008) that are in the state of JRNL_WRAP_ERROR.
This problem has existed since May 2013 and wasn't picked up until a 3rd DC (Windows Server 2012 R2) was added to the domain and didn't replicate the SYSVOL share. Backups therefore are out of date (a year and a bit)

On DC1
Event ID: 13561 - JRNL_WRAP_ERROR
Event ID: 13562 - Could not bind to a Domain Controller. Will try again at next polling cycle.
Sysvol/Netlogon shares are accessible

Event ID: 13508 - The FRS is having trouble enabling replication from DC2 to DC1 and will keep retrying.
Event ID: 13561 - JRNL_WRAP_ERROR
Sysvol/Netlogon shares are inaccessible

On DC3
Event ID: 13508 - The FRS is having trouble enabling replication from DC2 to DC3 and will keep retrying.
Event ID: 13508 - The FRS is having trouble enabling replication from DC1 to DC3 and will keep retrying.
Event ID: 13565 - FRS is initializing the system volume with data from another DC. Computer DC3 cannot become a DC until this process is complete
Event ID: 5706 - The Netlogon service could not create server share C:\Windows\SYSVOL\sysvol\domain\SCRIPS. The following error occured: The system cannot find the file specified.

There is also a transitive forest trust between this domain and another domain.
DNS zones are replicating ok.

Any advice?

Microsoft support call?

Thanks in advance
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.

The forest trust is what I'm not sure about here.  Otherwise, you need to set the BURFLAGS registry key on all of the DCs.

Basic steps are to stop FRS service on all three.  Make a backup copy of the SYSVOL and NETLOGON folder on each DC (Don't need to do this on the new DC since it doesn't have them yet.)

On the DC that you trust the most to have the best information, set BURFLAGS to D4.  On the other two DCs, set it to D2.  Start FRS on the DC where you set it to D4 and give it a few minutes.  Monitor the BURFLAGS key to make sure it goes back to 0 and check the event logs for FRS.  If all seems good, then start FRS on the other two DCs.  Same deal - monitor.

Once all are happy, you may have to merge some data between the NETLOGON and SYSVOL folders you backed up.

Here's an article that might help a little.

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
SummerhitsAuthor Commented:
Thanks very much for the reply.

I think the DC that trust the most is DC1 in this case as DC2 doesn't appear to be working well at all.

Was worried about doing that due to  the forest trust.

Another thing i was thinking of was unplugging DC2 and doing a dcpromo /forceremoval with a metadata cleanup.

At this stage it seems like the only option.
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 OS

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.