+ Post New Thread
Results 1 to 11 of 11
Windows Thread, SYSVOL Replication in Technical; Only my second week and already a huge problem :| There are four DCs here, two on each campus. The ...
  1. #1
    Norphy's Avatar
    Join Date
    Jan 2006
    Location
    Harpenden
    Posts
    2,233
    Thank Post
    50
    Thanked 271 Times in 209 Posts
    Blog Entries
    6
    Rep Power
    108

    SYSVOL Replication

    Only my second week and already a huge problem :|

    There are four DCs here, two on each campus. The replication of the SYSVOL and NETLOGON shares works across three of them but not on the fourth. This of course means that new login scripts and group policy objects do not appear on the fourth server if they are created on one of the other three and visa versa.

    The server which isn't replicating holds all of the FSMO roles apart from the schema master role. The server is generating an error in its event log, pasted below:

    Code:
    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. 
     
    Expand HKEY_LOCAL_MACHINE. 
    Click down the key path: 
       "System\CurrentControlSet\Services\NtFrs\Parameters" 
    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.
    I've read on MS's website here that enabling journal wrap automatic restore on versions of Windows above 2000 SP3 is not recommended so I'd rather not do that if necessary.

    I've checked repmon, the servers seem to be replicating all of their AD objects properly. I've checked everything suggested http://support.microsoft.com/kb/257338]here, everything seems to check out. DNS works, DCDIAG reports that replication is working on directory objects. I'm out of ideas. Any suggestions?

    Cheers,

    Norphy

  2. #2

    Join Date
    Aug 2005
    Location
    London
    Posts
    3,154
    Thank Post
    114
    Thanked 527 Times in 450 Posts
    Blog Entries
    2
    Rep Power
    123

    Re: SYSVOL Replication

    The easiest thing to do is probably to DCPROMO the faulty machine down and up again. This is essentially non-destructive and shouldn't take more than about 30 minutes. If you need to make sure users can keep working while you do this than transfer any FSMO roles off the machine with a problem.

    When you bring the machine back up, make sure you make it a global catalog server otherwise it won't process logons.

  3. #3

    Join Date
    Feb 2007
    Location
    Hereford
    Posts
    213
    Thank Post
    5
    Thanked 3 Times in 3 Posts
    Rep Power
    16

    Re: SYSVOL Replication

    You not the only one with this issue.
    I have this as well on my server 2003 machine.

    I only have one server on the network. It does everythink.
    DHCP,DNS, FSMO ROLES etc

    Why would i get this error if my server doesn't have anythink to replicate with?

    Is there a way to turn off FRS, would that fix the issue.

    If any ones got a solution for a one server setup please post here.

  4. #4

    Geoff's Avatar
    Join Date
    Jun 2005
    Location
    Fylde, Lancs, UK.
    Posts
    11,802
    Thank Post
    110
    Thanked 583 Times in 504 Posts
    Blog Entries
    1
    Rep Power
    224

    Re: SYSVOL Replication

    You can safely ignore these errors in a single server enviroment.

  5. #5

    Join Date
    Aug 2005
    Location
    London
    Posts
    3,154
    Thank Post
    114
    Thanked 527 Times in 450 Posts
    Blog Entries
    2
    Rep Power
    123

    Re: SYSVOL Replication

    Yes, but:

    They shouldn't happen - as goodhead says, why would you get replication errors when there's only 1 server?

    You really don't want to have only 1 server - if it ever fails you've got a big job to repair things. Put a second server in as a DC; that way you've got some redundancy and have to worry less if things ever go wrong!

  6. #6

    Join Date
    Jan 2006
    Location
    Surburbia
    Posts
    2,178
    Thank Post
    74
    Thanked 307 Times in 243 Posts
    Rep Power
    115

    Re: SYSVOL Replication

    Any suggestions?
    You could read KB290762 and everything else you can find on "burflags".

    Doesn't sound entirely the same problem, but I successfully used that on a W2K SP4 forest root (all FSMOs) a little while ago that had some event log entry saying it wouldn't act as a DC because of journal wrap. Only took 5 minutes once I'd finally convinced myself I understood what I was doing (sorry don't have value I used to hand).

  7. #7

    Join Date
    Feb 2007
    Location
    Hereford
    Posts
    213
    Thank Post
    5
    Thanked 3 Times in 3 Posts
    Rep Power
    16

    Re: SYSVOL Replication

    Quote Originally Posted by srochford
    Yes, but:

    They shouldn't happen - as goodhead says, why would you get replication errors when there's only 1 server?

    You really don't want to have only 1 server - if it ever fails you've got a big job to repair things. Put a second server in as a DC; that way you've got some redundancy and have to worry less if things ever go wrong!
    the server i'm talking about is my home dc. we have 3 dcs at the school

  8. #8

    Join Date
    Feb 2007
    Location
    Hereford
    Posts
    213
    Thank Post
    5
    Thanked 3 Times in 3 Posts
    Rep Power
    16

    Re: SYSVOL Replication

    Quote Originally Posted by Geoff
    You can safely ignore these errors in a single server enviroment.
    Geoff, thats great to know i can ignore them. How ever i hate having errors in the event logs. Even if i pretend they not there, at the back of my mind they are still there. I want get rid.

    There must be a way to tell the server not to replicate with any think.

  9. #9
    DMcCoy's Avatar
    Join Date
    Oct 2005
    Location
    Isle of Wight
    Posts
    3,424
    Thank Post
    10
    Thanked 488 Times in 428 Posts
    Rep Power
    111

    Re: SYSVOL Replication

    EDIT: I reread your original post as see you have multiple DCs, I'm really not sure what I would do there as things can get unplesant,

    For future referance for people with one DC:

    I saw this problem today on a single DC domain. I tried this http://www.jigsawboys.com/category/windows-2k3-server

    Now I'm not saying you should do this, but the service started again sucessfully after I did it. As always its a question of risk etc.

    Edit the Edit

    http://support.microsoft.com/kb/315457 has some info

  10. #10
    DMcCoy's Avatar
    Join Date
    Oct 2005
    Location
    Isle of Wight
    Posts
    3,424
    Thank Post
    10
    Thanked 488 Times in 428 Posts
    Rep Power
    111

    Re: SYSVOL Replication


  11. #11

    Join Date
    Feb 2007
    Location
    Hereford
    Posts
    213
    Thank Post
    5
    Thanked 3 Times in 3 Posts
    Rep Power
    16

    Re: SYSVOL Replication

    Quote Originally Posted by DMcCoy
    EDIT: I reread your original post as see you have multiple DCs, I'm really not sure what I would do there as things can get unplesant,

    For future referance for people with one DC:

    I saw this problem today on a single DC domain. I tried this http://www.jigsawboys.com/category/windows-2k3-server

    Now I'm not saying you should do this, but the service started again sucessfully after I did it. As always its a question of risk etc.

    Edit the Edit

    http://support.microsoft.com/kb/315457 has some info
    thanks, i'll have a go with the jigsawboys site tonight.

SHARE:
+ Post New Thread

Similar Threads

  1. Site Replication
    By wesleyw in forum Windows
    Replies: 9
    Last Post: 7th December 2007, 09:46 AM
  2. .vbs .bat error in sysvol
    By alonebfg in forum Windows
    Replies: 7
    Last Post: 16th July 2007, 07:57 PM
  3. AD Replication Error
    By kerrymoralee9280 in forum Wireless Networks
    Replies: 3
    Last Post: 12th July 2007, 09:39 AM
  4. SYSVOL Replication
    By Badger in forum Windows
    Replies: 19
    Last Post: 8th June 2007, 01:23 PM
  5. Replies: 4
    Last Post: 24th January 2007, 11:39 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •