Today I had a strange issue. My sysvol was not being replicated across all of my Domain Controllers and this was causing Group Policy issues.
My first clue to the problem was that some computers where not applying the group policy settings. I drilled down into the event viewer for these machines and found that I was getting errors with certain policies and files not being found. I checked the main domain controller and everything was there. Strange I thought. So I then checked the other Domain controllers to find that the policies had not arrived in the sysvol folder. So the next step was to run dcdiag in an elevated command prompt. It returned an error with the File Replication Services or FRSEvent error. Event viewer on this domain controller was my next step to have a look at the file replication services log and in there I found an issue with it being replicated. I tried restarting a few services like DNS, net Logon and file replication but still no joy.
So the next step was to check the main domain controller and make sure it was allowing the other controller access. First I ran dcdiag and everything was clear, then I checked the event viewer for the file replication services. Here I found a new error referencing the JRNL_WRAP_ERROR. I googled this to find out this is in fact an outdated message and the steps to fix this have changed. Basically I had to restart the service in a recovery mode. To do this I needed to change a registry setting located here.
HKLM/System/CurrentControlSet/services/NtFrs/Parameters/Backup\Restore/Process at Statup
I needed to change the BurFlags key to D4. I then restarted the service and everything rebuilt, the other domain controllers connected and everything was happy again.
For more information check out this Microsoft Support Article.
support.microsoft.com/KB/290762
ICTtechie 