none
AD Directory Replication Error

    Question

  • Hi,

    I have migrated my DC from Windows 2008 Standard 32-bit to Windows 2008 Enterprise R2. For this I have used a freshly installed machine and promote it to DC than transfered FSMO Roles to this new server (temporary DC)

    After doing this again installed fresh windows on old DC, DNS, DHCP using the same previous IP which Primary DC has and than again transferred roles to Primary DC from temporary DC(BDC)

    Meanwhile Additional DC is still on the Network which was auto synced with Primary DC (old), its still there on the network but replication is not taking place (ADC)

    After initial replication is done we have demoted the temporary DC from Network

    Now we are facing replication issues between Primary DC (Windows 2008 R2) and Additional DC (Windows 2008 32-bit)

         

    Log Name:      Directory Service

    Source:        Microsoft-Windows-ActiveDirectory_DomainService

    Dat

    e:          1/18/2017 11:06:55 AM
    Event ID:      2092
    Task Category: Replication
    Level:         Warning
    Keywords:      Classic
    User:          ANONYMOUS LOGON
    Computer:      BDC.domain.com
    Description:

    This server is the owner of the following FSMO role, but does not consider it valid. For the partition which contains the FSMO, this server has not replicated successfully with any of its partners since this server has been restarted. Replication errors are preventing validation of this role. 

    Operations which require contacting a FSMO operation master will fail until this condition is corrected. 
    FSMO Role: DC=domain,DC=com

    User Action: 

    1. Initial synchronization is the first early replications done by a system as it is starting. A failure to initially synchronize may explain why a FSMO role cannot be validated. This process is explained in KB article 305476. 
    2. This server has one or more replication partners, and replication is failing for all of these partners. Use the command repadmin /showrepl to display the replication errors.  Correct the error in question. For example there maybe problems with IP connectivity, DNS name resolution, or security authentication that are preventing successful replication. 
    3. In the rare event that all replication partners being down is an expected occurance, perhaps because of maintenance or a disaster recovery, you can force the role to be validated. This can be done by using NTDSUTIL.EXE to seize the role to the same server. This may be done using the steps provided in KB articles 255504 and 324801 on http://support.microsoft.com. 

    The following operations may be impacted: 
    Schema: You will no longer be able to modify the schema for this forest. 
    Domain Naming: You will no longer be able to add or remove domains from this forest. 
    PDC: You will no longer be able to perform primary domain controller operations, such as Group Policy updates and password resets for non-Active Directory Domain Services accounts. 
    RID: You will not be able to allocation new security identifiers for new user accounts, computer accounts or security groups. 
    Infrastructure: Cross-domain name references, such as universal group memberships, will not be updated properly if their target object is moved or renamed.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-ActiveDirectory_DomainService" Guid="{0e8478c5-3605-4e8c-8497-1e730c959516}" EventSourceName="NTDS Replication" />
        <EventID Qualifiers="32768">2092</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>5</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2017-01-18T06:06:55.442160600Z" />
        <EventRecordID>8013</EventRecordID>
        <Correlation />
        <Execution ProcessID="500" ThreadID="620" />
        <Channel>Directory Service</Channel>
        <Computer>BDC.domain.com/Computer>
        <Security UserID="S-1-5-7" />
      </System>
      <EventData>
        <Data>DC=domain,DC=pk</Data>
      </EventData>
    </Event>

    ===

    Wednesday, January 18, 2017 7:08 AM

Answers

  • Hi

     Please share "dcdiag","repadmin /replsum","ipconfig /all","netdom query fsmo" results..


    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

    • Marked as answer by srguy Thursday, January 19, 2017 9:03 AM
    Wednesday, January 18, 2017 8:41 AM

All replies

  • Log Name:      Directory Service
    Source:        Microsoft-Windows-ActiveDirectory_DomainService
    Date:          1/18/2017 12:03:56 PM
    Event ID:      1925
    Task Category: Knowledge Consistency Checker
    Level:         Warning
    Keywords:      Classic
    User:          ANONYMOUS LOGON
    Computer:      BDC.domain.com
    Description:
    The attempt to establish a replication link for the following writable directory partition failed. 
     
    Directory partition: 
    DC=domain,DC=pk 
    Source directory service: 
    CN=NTDS Settings,CN=ADC,CN=Servers,CN=LHR,CN=Sites,CN=Configuration,DC=domain,DC=com
    Source directory service address: 
    d2a08544-f3ef-49e7-a655-37911b4d7a5e._msdcs.domain.com
    Intersite transport (if any): 
    CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=domain,DC=com
     
    This directory service will be unable to replicate with the source directory service until this problem is corrected. 
     
    User Action 
    Verify if the source directory service is accessible or network connectivity is available. 
     
    Additional Data 
    Error value: 
    1722 The RPC server is unavailable.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-ActiveDirectory_DomainService" Guid="{0e8478c5-3605-4e8c-8497-1e730c959516}" EventSourceName="NTDS Replication" />
        <EventID Qualifiers="32768">1925</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>1</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8080000000000000</Keywords>
        <TimeCreated SystemTime="2017-01-18T07:03:56.382763800Z" />
        <EventRecordID>8033</EventRecordID>
        <Correlation />
        <Execution ProcessID="500" ThreadID="1184" />
        <Channel>Directory Service</Channel>
        <Computer>BDC.domain.pk</Computer>
        <Security UserID="S-1-5-7" />
      </System>
      <EventData>
        <Data>DC=domain,DC=pk</Data>
        <Data>d2a08544-f3ef-49e7-a655-37911b4d7a5e._msdcs.domain.pk</Data>
        <Data>The RPC server is unavailable.</Data>
        <Data>CN=NTDS Settings,CN=ADC,CN=Servers,CN=LHR,CN=Sites,CN=Configuration,DC=domain,DC=pk</Data>
        <Data>CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=domain,DC=pk</Data>
        <Data>1722</Data>
      </EventData>
    </Event>
    Wednesday, January 18, 2017 7:09 AM
  • Hi

     Please share "dcdiag","repadmin /replsum","ipconfig /all","netdom query fsmo" results..


    This posting is provided AS IS with no warranties or guarantees,and confers no rights. Best regards Burak Uğur

    • Marked as answer by srguy Thursday, January 19, 2017 9:03 AM
    Wednesday, January 18, 2017 8:41 AM
    • Edited by srguy Wednesday, January 18, 2017 9:11 AM
    Wednesday, January 18, 2017 9:10 AM
  • I would advise to start with the steps/verification I shared here in my troubleshooting guide: http://www.ahmedmalek.com/web/fr/articles.asp?artid=23

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

    Ahmed MALEK

    My Website Link

    My Linkedin Profile

    My MVP Profile

    Wednesday, January 18, 2017 11:33 PM
  • Hi,
    Regarding Event ID 2092, I would suggest to check the value of fSMORoleOwner attribute of CN=Schema,CN=Configuration,DC=domain,DC=com directly and verify that it points to the correct DC. And you could have a try to seize the FSMO and see if it works.
    Also, here is a suggested method from huntertsl to fix a similar error in the following thread:
    “Basically I just pointed my FSMO role holder's DNS to one of the other DCs and bounced it.  Bingo it replicates and all is well.  Once it is happy you can point the DNS back to itself”
    https://social.technet.microsoft.com/Forums/office/en-US/72098e3f-7b60-464a-9b9a-e70deaf1736a/replication-problems-event-id-2092?forum=winserverDS
    And about the unavailable RPC error in the event 1925, firstly please check if the firewall is blocking or needed ports are not opened. You could also refer to more details about this error from:
    How IT Works Troubleshooting RPC Errors
    https://technet.microsoft.com/en-us/library/2007.07.howitworks.aspx
    Windows Server Troubleshooting: "The RPC server is unavailable"
    http://social.technet.microsoft.com/wiki/contents/articles/4494.windows-server-troubleshooting-the-rpc-server-is-unavailable.aspx
    Best regards,
    Wendy

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, January 19, 2017 7:11 AM
    Moderator