none
The File Replication Service is having trouble enabling replication

    Question

  • Hi everyone,

    Just wondering if anyone out there has run into the following error that started without much warning. Yet, following instructions on how to solve the problem haven't help me much.

    ERROR:

    The File Replication Service is having trouble enabling replication
    from [Server2] to [Server1] for c:\windows\sysvol\domain
    using the DNS name [Server2].domain.com. FRS will keep retrying.
    Following are some of the reasons you would see this warning.
     
     [1] FRS can not correctly resolve the DNS name [Server2].domain.com
         from this computer.
        
         ANSWER: I can ping both, back and forth using the FQN.
        
     [2] FRS is not running on [Server2].domain.com.
     
         ANSWER: I chekced the services in both servers = both working.
     
      [3] The topology information in the Active Directory for this replica
          has not yet replicated to all the Domain Controllers.
         
         ANSWER: The service was working before. How can I check if the topology
         info is gone? How should I tackle this one?
      
     
      ADITIONAL DATA:
     
     i. RPC is working. I can eventview back and forth.
     ii. Space in the disks is fine. Both servers have plenty of space for replication.
     iii. I have stopped and started the FRS to force the systems to start all over again = problem persists. 


    Thank you all!!
    • Moved by Bruce-Liu Friday, November 25, 2011 1:37 AM (From:Server Manager)
    Thursday, November 24, 2011 1:37 AM

Answers

  • The event id 13508 & 13509 indicates replication failure between the DC.There could be many reason why this can happen.
    DNS missconfig,network latency issue,secure channel between the DC broken,FRS in Journal Wrap error state.Performance issue on the server,server may have reached tombstone life cycle period,time difference between the sever,firewall blocking the replication Ports,etc.

    Most of the time it is DNS misconfig or network connectivity issue.

    1.Check the DNS setting on the Server's it should point to itself assuming DNS role is installed on the server.If the public ip address is added in the NIC DNS setting remove the same and add to DNS forwarders if required.
    If 127.0.0.1 is entered as dns remove the same and add ip address.Add alternate DNS setting.

    2.Check NIC binding the NIC which is online and has ip details should be in first order.If multiple NIC are present then disabled the unrequired NIC.

    3.Ran ipconfig /flushdns and ipconfig /registerdns.Restart the netlogon and DNS service

    4.Check the windows firewall is disabled.

    5.Ran repadmin /syncall /AdeP on all DC to force the replication

    6.Once done ran dcdiag /q  and repadmin /replsum to check for any errors and post the same.Check the eventlogs(DNS,FRS,Directory service) for any warning or errors and post the same.

    7.Check the firewall ports.http://geekswithblogs.net/TSCustomiser/archive/2007/05/09/112357.aspx

    8.Have a look at this.
    http://www.eventid.net/display.asp?eventid=13508&eventno=349&source=ntfrs&phase=1
    http://technet.microsoft.com/en-us/library/bb727056.aspx

    Hope this helps.

    Regards,
    Sandesh Dubey.
    -------------------------------
    MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator
    My Blog: http://sandeshdubey.wordpress.com
    This posting is provided AS IS with no warranties, and confers no rights.


    • Marked as answer by Bruce-Liu Tuesday, November 29, 2011 9:34 AM
    Saturday, November 26, 2011 1:25 AM

All replies

  • Hi,

     

    Before we go further, I would like to confirm if an FRS 13509 message appears in Event Viewer. If so, the problem has been corrected.

     

    If not, please check if the FRS 13508 message only appeared once or always appears. If it always appears, please follow the steps below to troubleshoot it:

     

    1.    Run the following command to synchronize the clock time with the domain controller:

     

    net time \\(domain controller name) /set /y

     

    2.    If the problem continues, please temporarily turn off firewall. Then , open Event Viewer to check if the error comes up again.

     

    Hope this helps.

     

    Regards,

    Bruce

    • Marked as answer by Bruce-Liu Tuesday, November 29, 2011 9:34 AM
    • Unmarked as answer by Carlos de Paula Tuesday, December 13, 2011 6:29 PM
    Friday, November 25, 2011 10:42 AM
  • The error "The File Replication Service is having trouble enabling replication from [Server2] to [Server1] for c:\windows\sysvol\domain using the DNS name [Server2].domain.com. FRS will keep retrying. " indicates there can be the network problem which can be due to high latency or disruption of connection, security software preventing connection to other dc during Sysvol and its content sync. This can also be an intermittent issue which is corrected automatically when connection was restored.

    If this error is frequently seen, you need more investigation. Is sysvol has been excluded from scanning, because sometime access to sysvol is locked during antivirus scan. Also, do you see journal wrap error? What is the size of the sysvol, there can be corrupt data too in the sysvol folder.

    http://blogs.technet.com/b/btrst4/archive/2004/06/15/156320.aspx

     

    Regards  


    Awinish Vishwakarma

    MY BLOG:  http://awinish.wordpress.com/


    This posting is provided AS-IS with no warranties/guarantees and confers no rights.
    • Marked as answer by Bruce-Liu Tuesday, November 29, 2011 9:34 AM
    • Unmarked as answer by Carlos de Paula Tuesday, December 13, 2011 6:29 PM
    Friday, November 25, 2011 11:07 AM
    Moderator
  • Hello,

    please proceed like that:

    • Make sure that each DC / DNS server points to its private IP address as primary DNS server and other internal DNS servers as secondary ones
    • Make sure that each DC without DNS points to internal DNS servers as DNS servers
    • Make sure each DC has one IP address and one NIC card

    Once done, run ipconfig /registerdns and restart netlogon on each DC you have.

    Also, check that needed ports for AD replication are not blocked: http://technet.microsoft.com/en-us/library/bb727063.aspx

    and check also connectivity.

    If this does not help, disable all security softwares and refer to that: http://support.microsoft.com/kb/290762

    If the problem persists consider rebuilding the SYSVOL tree: http://support.microsoft.com/kb/315457

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

     

    • Marked as answer by Bruce-Liu Tuesday, November 29, 2011 9:34 AM
    • Unmarked as answer by Carlos de Paula Tuesday, December 13, 2011 6:28 PM
    Friday, November 25, 2011 1:07 PM
  • The event id 13508 & 13509 indicates replication failure between the DC.There could be many reason why this can happen.
    DNS missconfig,network latency issue,secure channel between the DC broken,FRS in Journal Wrap error state.Performance issue on the server,server may have reached tombstone life cycle period,time difference between the sever,firewall blocking the replication Ports,etc.

    Most of the time it is DNS misconfig or network connectivity issue.

    1.Check the DNS setting on the Server's it should point to itself assuming DNS role is installed on the server.If the public ip address is added in the NIC DNS setting remove the same and add to DNS forwarders if required.
    If 127.0.0.1 is entered as dns remove the same and add ip address.Add alternate DNS setting.

    2.Check NIC binding the NIC which is online and has ip details should be in first order.If multiple NIC are present then disabled the unrequired NIC.

    3.Ran ipconfig /flushdns and ipconfig /registerdns.Restart the netlogon and DNS service

    4.Check the windows firewall is disabled.

    5.Ran repadmin /syncall /AdeP on all DC to force the replication

    6.Once done ran dcdiag /q  and repadmin /replsum to check for any errors and post the same.Check the eventlogs(DNS,FRS,Directory service) for any warning or errors and post the same.

    7.Check the firewall ports.http://geekswithblogs.net/TSCustomiser/archive/2007/05/09/112357.aspx

    8.Have a look at this.
    http://www.eventid.net/display.asp?eventid=13508&eventno=349&source=ntfrs&phase=1
    http://technet.microsoft.com/en-us/library/bb727056.aspx

    Hope this helps.

    Regards,
    Sandesh Dubey.
    -------------------------------
    MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator
    My Blog: http://sandeshdubey.wordpress.com
    This posting is provided AS IS with no warranties, and confers no rights.


    • Marked as answer by Bruce-Liu Tuesday, November 29, 2011 9:34 AM
    Saturday, November 26, 2011 1:25 AM
  • Thank you all for your help!

    All of the above suggestions checked. Replication still is failing ;-(

    What command line tools do we have to test | troubleshoot replication?  


    Thank you all!!
    Thursday, December 08, 2011 9:26 PM
  • Can you ran dcdiag /q and repadmin /replsum and post the log.

    Also check the directory service,FRS,DNS event log for any errors and warning and post the same.

    Regards,
    Sandesh Dubey.
    -------------------------------
    MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator
    My Blog: http://sandeshdubey.wordpress.com
    This posting is provided AS IS with no warranties, and confers no rights.




    Friday, December 09, 2011 1:41 AM
  • Thank you Sandesh. Here are the logs and info:

    ########################################################
    LOGS
    ########################################################

    C:\Documents and Settings\Administrator>dcdiag /q
             There are warning or error events within the last 24 hours after the
             SYSVOL has been shared.  Failing SYSVOL replication problems may cause
             Group Policy problems.
             ......................... FP1-17315021 failed test frsevent
            
    ########################################################

    C:\Documents and Settings\Administrator>repadmin /replsum
    Replication Summary Start Time: 2011-12-12 20:48:34

    Beginning data collection for replication summary, this may take awhile:
      .......


    Source DC           largest delta  fails/total  %%  error
     FP1-17315021              13m:39s    0 /  10    0
     HS1-17315021              58m:39s    0 /  10    0
     TS1-17315021              57m:36s    0 /  15    0
     TS2-17315021              50m:37s    0 /  15    0


    Destination DC    largest delta    fails/total  %%  error
     FP1-17315021              08m:41s    0 /  10    0
     HS1-17315021              50m:39s    0 /  10    0
     TS1-17315021              58m:40s    0 /  15    0
     TS2-17315021              57m:36s    0 /  15    0

    ########################################################
    C:\>systeminfo
    ########################################################

    Host Name:                 FP1-17315021
    OS Name:                   Microsoft(R) Windows(R) Server 2003, Standard Edition

    OS Version:                5.2.3790 Service Pack 2 Build 3790
    OS Manufacturer:           Microsoft Corporation
    OS Configuration:          Primary Domain Controller
    OS Build Type:             Multiprocessor Free
    Registered Owner:          Authorized Server
    Registered Organization:   ADP Dealer Services
    Product ID:                69712-640-7934381-45060
    Original Install Date:     8/11/2006, 9:24:16 AM
    System Up Time:            315 Days, 13 Hours, 28 Minutes, 18 Seconds
    System Manufacturer:       IBM
    System Model:              eserver xSeries 346 -[884005U]-
    System Type:               X86-based PC
    Processor(s):              2 Processor(s) Installed.
                               [01]: x86 Family 15 Model 4 Stepping 10 GenuineIntel
    ~2800 Mhz
                               [02]: x86 Family 15 Model 4 Stepping 10 GenuineIntel
    ~2800 Mhz
    BIOS Version:              IBM    - 1001
    Windows Directory:         C:\WINDOWS
    System Directory:          C:\WINDOWS\system32
    Boot Device:               \Device\HarddiskVolume1
    System Locale:             en-us;English (United States)
    Input Locale:              en-us;English (United States)
    Time Zone:                 (GMT-06:00) Central Time (US & Canada)
    Total Physical Memory:     1,023 MB
    Available Physical Memory: 144 MB
    Page File: Max Size:       2,985 MB
    Page File: Available:      1,964 MB
    Page File: In Use:         1,021 MB
    Page File Location(s):     C:\pagefile.sys
    Domain:                    aamd.local
    Logon Server:              \\FP1-17315021
    Hotfix(s):                 183 Hotfix(s) Installed.
                               [01]: File 1
                               [02]: File 1
     ........................................................
                               [178]: KB960714 - Update
                               [179]: KB960715 - Update
                               [180]: KB960803 - Update
                               [181]: KB961063 - Update
                               [182]: KB961373 - Update
                               [183]: KB967715 - Update
    Network Card(s):           1 NIC(s) Installed.
                               [01]: Broadcom NetXtreme Gigabit Ethernet
                                     Connection Name: Local Area Connection 2
                                     DHCP Enabled:    No
                                     IP address(es)
                                     [01]: 20X.18X.19X.X
                                    
    ########################################################
    EVENTVIEWER
    ########################################################

    he File Replication Service is having trouble enabling replication from
    TS2-17315021 to FP1-17315021 for c:\windows\sysvol\domain using the DNS name
    ts2-17315021.aamd.local. FRS will keep retrying.
     Following are some of the reasons you would see this warning.
     
     [1] FRS can not correctly resolve the DNS name ts2-17315021.aamd.local from this computer.
     [2] FRS is not running on ts2-17315021.aamd.local.
     [3] The topology information in the Active Directory for this replica has not yet replicated
         to all the Domain Controllers.


    Thank you all!! Prax
    Tuesday, December 13, 2011 2:58 AM
  • The event id 13508 & 13509 indicates replication failure between the DC.There could be many reason why this can happen.
    DNS missconfig,network latency issue,secure channel between the DC broken,FRS in Journal Wrap error state.Performance issue on the server,server may have reached tombstone life cycle period,time difference between the sever,firewall blocking the replication Ports,etc.

    Most of the time it is DNS misconfig or network connectivity issue.

    1.Check the DNS setting on the Server's it should point to itself assuming DNS role is installed on the server.If the public ip address is added in the NIC DNS setting remove the same and add to DNS forwarders if required.
    If 127.0.0.1 is entered as dns remove the same and add ip address.Add alternate DNS setting.

    2.Check NIC binding the NIC which is online and has ip details should be in first order.If multiple NIC are present then disabled the unrequired NIC.

    3.Ran ipconfig /flushdns and ipconfig /registerdns.Restart the netlogon and DNS service

    4.Check the windows firewall is disabled.

    5.Ran repadmin /syncall /AdeP on all DC to force the replication

    6.Once done ran dcdiag /q  and repadmin /replsum to check for any errors and post the same.Check the eventlogs(DNS,FRS,Directory service) for any warning or errors and post the same.

    7.Check the firewall ports.http://geekswithblogs.net/TSCustomiser/archive/2007/05/09/112357.aspx

    8.Have a look at this.
    http://www.eventid.net/display.asp?eventid=13508&eventno=349&source=ntfrs&phase=1
    http://technet.microsoft.com/en-us/library/bb727056.aspx

    Hope this helps.

    Regards,
    Sandesh Dubey.
    -------------------------------
    MCSE|MCSA:Messaging|MCTS|MCITP:Enterprise Adminitrator
    My Blog: http://sandeshdubey.wordpress.com
    This posting is provided AS IS with no warranties, and confers no rights.



    Just want to thanks so much for your post. I had critical issues related to replication between  our win2k DC wind2k8 DC.

    Errors in wn2k DC as below

    "Naming information cannot be located because

    The specified domain either does not exists or could not be contacted "

    Also when try to create AD objects it did not allow me create anything. There was error related RID

    After following your instructions given above, I am so happy to tell you that my DC environment replication work like a charm   ::))

    Just want to thanks so much mate

    Cheers

    PRas
    • Edited by PrazAU Thursday, December 12, 2013 11:18 AM
    Thursday, December 12, 2013 11:18 AM