Domain controller not successfully promoting

Ryan Wilderman 151 Reputation points
2023-01-23T13:11:08.11+00:00

I have a client with a single 2012 domain controller. Trying to add a 2022 domain controller to the domain, SYSVOL is never shared. In the DFS Replication log, I have warning events 6016, 4614, and 6804.

Log Name:      DFS Replication
Source:        DFSR
Date:          1/22/2023 3:16:13 PM
Event ID:      6016
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      CO-DC22-01.XXXX.local
Description:
The DFS Replication service failed to update configuration in Active Directory Domain Services. The service will retry this operation periodically. 
 
Additional Information: 
Object Category: msDFSR-LocalSettings 
Object DN: CN=DFSR-LocalSettings,CN=CO-DC22-01,OU=Domain Controllers,DC=XXXX,DC=local 
Error: 2 (The system cannot find the file specified.) 
Domain Controller: co-dc.XXXX.local 
Polling Cycle: 60
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="DFSR" />
    <EventID Qualifiers="32768">6016</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2023-01-22T23:16:13.5203485Z" />
    <EventRecordID>18</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>DFS Replication</Channel>
    <Computer>CO-DC22-01.XXXX.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>msDFSR-LocalSettings</Data>
    <Data>CN=DFSR-LocalSettings,CN=CO-DC22-01,OU=Domain Controllers,DC=XXXX,DC=local</Data>
    <Data>2</Data>
    <Data>The system cannot find the file specified.</Data>
    <Data>co-dc.XXXX.local</Data>
    <Data>60</Data>
  </EventData>
</Event>
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,543 questions
0 comments No comments
{count} votes

Accepted answer
  1. Dave Patrick 426.1K Reputation points MVP
    2023-01-23T13:48:23.25+00:00

    Please run;

    Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log (run on PDC emulator)
    repadmin /showrepl >C:\repl.txt (run on any domain controller)
    ipconfig /all > C:\%computername%.txt (run on EVERY domain controller)

    Also check the domain controller System and Replication (DFS or FRS) event logs for errors since last boot. Post the Event Source and Event IDs of any found. (no evtx files)

    then put unzipped text files up on OneDrive and share a link.


2 additional answers

Sort by: Most helpful
  1. Thameur-BOURBITA 28,546 Reputation points
    2023-01-23T13:56:49.66+00:00

    Hi @Ryan Wilderman

    Check if the DFSR port is not blocked between the 2 domain controllers.

    If it's not the case, you can try one of the following solutions to reinitialise DFSR replication:

    Please don't forget to mark helpful answer as accepted

    0 comments No comments

  2. Ryan Wilderman 151 Reputation points
    2023-01-24T00:55:11.53+00:00

    Thank you. The answer was actually quite clear in DCDiag.

          Starting test: DFSREvent
             The DFS Replication Event Log. 
             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. 
             A warning event occurred.  EventID: 0x800008A5
                Time Generated: 01/23/2023   10:31:16
                Event String:
                The DFS Replication service stopped replication on volume C:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication. 
                 
                Additional Information: 
                Volume: C: 
                GUID: 8DBE48AB-923E-11E3-93E7-806E6F6E6963 
                 
                Recovery Steps 
                1. Back up the files in all replicated folders on the volume. Failure to do so may result in data loss due to unexpected conflict resolution during the recovery of the replicated folders. 
                2. To resume the replication for this volume, use the WMI method ResumeReplication of the DfsrVolumeConfig class. For example, from an elevated command prompt, type the following command: 
                wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="8DBE48AB-923E-11E3-93E7-806E6F6E6963" call ResumeReplication