No announcement yet.

active directory problem - replication

  • Filter
  • Time
  • Show
Clear All
new posts

  • active directory problem - replication

    i have got four branch offices and one main office

    in each of the branch locations is a server running as a dc, dns,dhcp and file server

    the setup seams to be working but this week i have found out one of the servers has got a problem with group policys, i.e. any changes made at the ho are not replicated to this server. (this does not happen at any other location)
    (i.e. when i check the policys directory in the sysvol for this machine its a completely different state to anything else)

    yet if i change a password this replicates both ways staight away

    i have run a dsastate against this and ho:-

    Server Bytes
    server100 571151
    server300 571151

    . . . . . . . . . . . . . .
    Checking for missing replies...
    No missing replies!INFO: Server sizes are equal.
    *** Identical Directory Information Trees ***
    -=>> PASS <<=-
    closing connections...
    server100; server300;

    (server300 being branch location)

    netdiag and dcdiag also produces no problems.

    any ideas?

  • #2
    Re: active directory problem - replication

    could you please post the events from the File replication service on the DC in question?
    and also goto the GPMC and open a GPO under "details" on the right pane window check and see if the SYSVOL number matches the AD number.
    it would be looking like the following:
    5 (AD), 5 (sysvol) - (5 is an example number, it could be any number usually based on the changes you had done to the specific GPO).
    check on all your GPOs and do the same on a good working DC as well.


    • #3
      Re: active directory problem - replication

      i think i have fixed it:-

      restarted dc, and i event log was:

      The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.

      Replica set name is : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
      Replica root path is : "c:\windows\sysvol\domain"
      Replica root volume is : "\\.\C:"
      A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found. This can occur because of one of the following reasons.

      [1] Volume "\\.\C:" has been formatted.
      [2] The NTFS USN journal on volume "\\.\C:" has been deleted.
      [3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
      [4] File Replication Service was not running on this computer for a long time.
      [5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
      Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
      [1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
      [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.

      WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.

      To change this registry parameter, run regedit.

      Click on Start, Run and type regedit.

      Click down the key path:
      "System\CurrentControlSet\Services\NtFrs\Parameter s"
      Double click on the value name
      "Enable Journal Wrap Automatic Restore"
      and update the value.

      If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.

      so i followed instructions i.e. added reg entry and hey presto, sysvol was deleted and re replicated, and now is working correctly


      • #4
        Re: active directory problem - replication

        that what I thought you had , Journal Wrapping, just wanted to be sure.