Active Directory
A set of directory-based technologies included in Windows Server.
4,010 questions
Here you have the image as an attachment.
"The replication partner: XXX shows replication errors"......!?
Marin Marinov
1
Reputation point
Hello everyone, on the attached picture you can see the topology of my lab. I`m having troubles promoting the server called DC-2-2 to a domain controller for child.office-2.local. I got "The replication partner: DC-2.office-2.local shows replication errors." In the txt file you can find the output of "Install-ADDSDomain". I can not figure out how to use repadmin.exe to narrow down the cause of the issue. May I ask you for help?
12 answers
Sort by: Most helpful
-
Marin Marinov 1 Reputation point
2023-03-03T16:22:10.97+00:00 here you have the screenshot as an attachment
Dave Patrick 343.3K Reputation points MVP2023-03-03T16:28:37.9666667+00:00 can not figure out how to use repadmin.exe to narrow down the cause of the issue.
I'd check the FRS Replication or DFS Replication event logs for clues. Then if needed you can try a non-authoritative sync.
If you're using older FRS you can follow along here. https://support.microsoft.com/en-us/help/290762/using-the-burflags-registry-key-to-reinitialize-file-replication-servi
or for DFSR follow along here. https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo-
--please don't forget to
upvoteandAccept as answerif the reply is helpful---
Dave Patrick 343.3K Reputation points MVP
2023-03-03T18:52:19.88+00:00 Just checking if there's any progress or updates?
--please don't forget to
upvoteandAccept as answerif the reply is helpful--
Dave Patrick 343.3K Reputation points MVP2023-03-07T16:30:09.2133333+00:00 You can try a non-authoritative sync, or another option is to demote, reboot, promo again the problematic one.
https://learn.microsoft.com/en-US/troubleshoot/windows-server/group-policy/force-authoritative-non-authoritative-synchronization#how-to-perform-a-non-authoritative-synchronization-of-dfsr-replicated-sysvol-replication-like-d2-for-frs-
--please don't forget to
upvoteandAccept as answerif the reply is helpful---
Marin Marinov 1 Reputation point
2023-03-07T18:11:57.1266667+00:00 I have reviewed the suggested article and I thing it is not applicable to my problem. I will try everything from scratch.
Sign in to comment
Marin Marinov 1 Reputation point2023-03-07T18:24:03.76+00:00 Use answers to provide solutions to the user's question.
Sign in to answer-
Dave Patrick 343.3K Reputation points MVP
2023-03-07T18:30:47.0333333+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
unzippedtext files up on OneDrive and share a link.
Sign in to comment
Please don't forget to close up the thread here by marking answer.
Just checking if there's any progress or updates?
--please don't forget to
upvoteandAccept as answerif the reply is helpful--Hello Patrick, thank you for your answer. Here is what I found:
---DC-2`s DFS replication event logs---
"The DFS Replication service failed to contact domain controller to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.
Additional Information:
Error: 160 (One or more arguments are not correct.)"
Thus I checked the DNS.
C:\Users\Administrator>nslookup 10.0.0.35
Server: localhost
Address: 127.0.0.1
**** localhost can't find 10.0.0.35: Non-existent domain*
C:\Users\Administrator>nslookup DC-2-2
Server: localhost
Address: 127.0.0.1
**** localhost can't find DC-2-2: Non-existent domain*
C:\Users\Administrator>nslookup DC-2-2.office-2.local
Server: localhost
Address: 127.0.0.1
**** localhost can't find DC-2-2.office-2.local: Non-existent domain*
C:\Users\Administrator>nslookup DC-2-2.office-2.local
Server: localhost
Address: 127.0.0.1
**** localhost can't find DC-2-2.office-2.local: Non-existent domain*
There is no problem for DC-2-2 to resolve the name of it`s partner. Both server are using the correct DNS address. There is no connection issue. Any suggestion?
Sign in to comment