+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 21
Windows Server 2000/2003 Thread, Sysvol not replicating to second DC in Technical; Event Type: Warning Event Source: NtFrs Event Category: None Event ID: 13508 Date: 08/03/2012 Time: 17:01:25 User: N/A Computer: DC2 ...
  1. #1

    CHR1S's Avatar
    Join Date
    Feb 2006
    Location
    Birmingham
    Posts
    4,489
    Thank Post
    1,575
    Thanked 479 Times in 302 Posts
    Rep Power
    215

    Sysvol not replicating to second DC

    Event Type: Warning
    Event Source: NtFrs
    Event Category: None
    Event ID: 13508
    Date: 08/03/2012
    Time: 17:01:25
    User: N/A
    Computer: DC2
    Description:
    The File Replication Service is having trouble enabling replication from DC1 to DC2 for c:\windows\sysvol\domain using the DNS name DC1.UK. FRS will keep retrying.
    Following are some of the reasons you would see this warning.

    [1] FRS can not correctly resolve the DNS name DC1.UK from this computer.
    [2] FRS is not running on DC1.UK.
    [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
    Ive checked DNS, I can ping each DC from the other, I can ping the DCs GUIs.

    FRS is running as the other DFS shares are replicating successfully too.

    DCdiag only fails on FRSevent (as above)

    The sysvols on each DC most certainly dont match!

    HELP!!

  2. #2

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    15,846
    Thank Post
    877
    Thanked 1,680 Times in 1,460 Posts
    Blog Entries
    12
    Rep Power
    444
    Are the IP settings correct on both DCs?
    I assume you have tried a reboot?
    Can you see the Servers DNS records in DNS (check the DNS on both servers)

  3. #3

    CHR1S's Avatar
    Join Date
    Feb 2006
    Location
    Birmingham
    Posts
    4,489
    Thank Post
    1,575
    Thanked 479 Times in 302 Posts
    Rep Power
    215
    DNS looks fine, replicates correctly too.

    Tried reboots, tried service restarts (frs)

    Event Type: Information
    Event Source: NtFrs
    Event Category: None
    Event ID: 13516
    Date: 09/03/2012
    Time: 11:25:26
    User: N/A
    Computer: DC2
    Description:
    The File Replication Service is no longer preventing the computer DC2 from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.
    Still no replication

  4. #4

    Join Date
    Apr 2007
    Location
    Christchurch
    Posts
    420
    Thank Post
    41
    Thanked 64 Times in 62 Posts
    Rep Power
    25
    Have you tried to access each server from the other using the dns name rather than the IP? Could point to a DNS problem if IP works but DC1.UK etc doesnt !!

  5. #5

    CHR1S's Avatar
    Join Date
    Feb 2006
    Location
    Birmingham
    Posts
    4,489
    Thank Post
    1,575
    Thanked 479 Times in 302 Posts
    Rep Power
    215
    Replmon says all replications were successfull on both DCs

    Both servers can see each other by IP/DNS name/GUI name

    FRS error message keeps being thrown up on DC2 only

  6. #6

    Join Date
    Apr 2007
    Location
    Christchurch
    Posts
    420
    Thank Post
    41
    Thanked 64 Times in 62 Posts
    Rep Power
    25
    Silly I know but have you checked that there is plenty of space on both sysvol drives? Also .. try copying and pasting a file from one dc to the others sysvol folder and vice versa .. might show up a permissions problem ..

  7. #7

    CHR1S's Avatar
    Join Date
    Feb 2006
    Location
    Birmingham
    Posts
    4,489
    Thank Post
    1,575
    Thanked 479 Times in 302 Posts
    Rep Power
    215
    New error -
    Event Type: Error
    Event Source: NtFrs
    Event Category: None
    Event ID: 13561
    Date: 09/03/2012
    Time: 12:07:09
    User: N/A
    Computer: DC1
    Description:
    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:\winnt\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:".

    Following recovery steps will 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.
    [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.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    After creating the reg value to auto fix I get this error -

    Event Type: Warning
    Event Source: NtFrs
    Event Category: None
    Event ID: 13560
    Date: 09/03/2012
    Time: 12:07:10
    User: N/A
    Computer: DC1
    Description:
    The File Replication Service is deleting this computer from the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" as an attempt to recover from the error state,
    Error status = FrsErrorSuccess
    At the next poll, which will occur in 5 minutes, this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.

    For more information, see Help and Support Center at Events and Errors Message Center: Basic Search.
    Last edited by CHR1S; 9th March 2012 at 12:10 PM.

  8. #8

    CHR1S's Avatar
    Join Date
    Feb 2006
    Location
    Birmingham
    Posts
    4,489
    Thank Post
    1,575
    Thanked 479 Times in 302 Posts
    Rep Power
    215
    Event Type: Information
    Event Source: NtFrs
    Event Category: None
    Event ID: 13554
    Date: 09/03/2012
    Time: 12:12:10
    User: N/A
    Computer: DC1
    Description:
    The File Replication Service successfully added the connections shown below to the replica set:
    "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"

    "DC2.UK"
    "DC2.UK"

    Is that fixed then? lol

  9. #9

    Join Date
    Apr 2007
    Location
    Christchurch
    Posts
    420
    Thank Post
    41
    Thanked 64 Times in 62 Posts
    Rep Power
    25
    The second one is not an error its just a warning that DC1 is being deleted from the replica set and then re-added to it. It will also trigger a full tree replication process to sync all server replications sets including hopefully your sysvol ...

  10. Thanks to Brpilot99 from:

    CHR1S (9th March 2012)

  11. #10

    Join Date
    Apr 2007
    Location
    Christchurch
    Posts
    420
    Thank Post
    41
    Thanked 64 Times in 62 Posts
    Rep Power
    25
    Hopefully yes !!

  12. #11

    CHR1S's Avatar
    Join Date
    Feb 2006
    Location
    Birmingham
    Posts
    4,489
    Thank Post
    1,575
    Thanked 479 Times in 302 Posts
    Rep Power
    215
    I "think" its fixed, I created a test folder on one DC and it replicated almost immediatly to the other.

    Going to monitor and see how it goes.

    Thanks for the support guys

  13. #12

    Join Date
    Apr 2007
    Location
    Christchurch
    Posts
    420
    Thank Post
    41
    Thanked 64 Times in 62 Posts
    Rep Power
    25
    Well done !! Have a fab weekend !!

  14. #13

    CHR1S's Avatar
    Join Date
    Feb 2006
    Location
    Birmingham
    Posts
    4,489
    Thank Post
    1,575
    Thanked 479 Times in 302 Posts
    Rep Power
    215
    Erm, spoke too soon!

    All GPO application on PCs is now failing because its looking for two policies which dont exist.

  15. #14

    Join Date
    Apr 2007
    Location
    Christchurch
    Posts
    420
    Thank Post
    41
    Thanked 64 Times in 62 Posts
    Rep Power
    25
    Does it tell you which policies its looking for .. if so can you check and see if they actually exist ... Check with GPO manager on both servers just in case theres still a replication issue

  16. #15

    CHR1S's Avatar
    Join Date
    Feb 2006
    Location
    Birmingham
    Posts
    4,489
    Thank Post
    1,575
    Thanked 479 Times in 302 Posts
    Rep Power
    215
    AD and GPOs are identical over doth DCs, The two missing GPOs are just long GUID strings so I have no way of knowing what they are.

    I have a hunch that these are ADMX files and the repair has messed with my schema.
    Might rerun adprep from the server 2008 R2 disk and repopulate my ADMX files again.
    Last edited by CHR1S; 9th March 2012 at 01:06 PM.

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. Replies: 8
    Last Post: 25th November 2010, 10:33 AM
  2. DHCP not giving out second DNS to XP
    By ZeroHour in forum Windows Server 2008
    Replies: 9
    Last Post: 28th January 2009, 11:05 AM
  3. Proxy settings not there on second logon.
    By robinhood in forum Learning Network Manager
    Replies: 7
    Last Post: 6th October 2007, 11:14 AM
  4. Xterm not conecting to proxy
    By TechMonkey in forum *nix
    Replies: 7
    Last Post: 4th October 2006, 11:08 AM
  5. Some of GP not applied to one PC
    By Pear in forum Windows
    Replies: 8
    Last Post: 16th December 2005, 02:14 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
  •