troubleshooting Question

JRNL_WRAP_ERROR on Windows 2003 server, added 2012 DC successfully, but can't replicate

Avatar of ruhkus
ruhkus asked on
Windows Server 2003Active Directory
2 Comments1 Solution164 ViewsLast Modified:
Up until last week, I had a single 2003 DC in a remote office. I just added a 2012 DC, but I noticed it's not fully replicating with FRS, most likely due to a JRNL_WRAP_ERROR on the 03 server, which has apparently been happening since 2012. I followed the instructions a few times to do the registry edit on "Enable Journal Wrap Automatic Restore", but that didn't seem to help. I've read up on the burflags key, but I haven't tried it yet. Assuming burflags is my next step, how should I proceed? Since the 2012 DC process succeeded, but yet isn't a fully operational DC, I wasn't sure if I should proceed with a nonauthoritative restore, or if I'd risk screwing up something. Thanks.

Burflags - https://support.microsoft.com/en-us/kb/290762

Error message on 2003 server -
The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.


Error on 2012 server for reference -

The File Replication Service is having trouble enabling replication from 2003 server to this 2012 server for c:\windows\sysvol\domain using the DNS name 2003server.domain.local
ASKER CERTIFIED SOLUTION
it_saige
Developer
Join our community to see this answer!
Unlock 1 Answer and 2 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 2 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros