Answered by:
The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner.

-
Hi everyone,
I was creating a new domain in an existing forest. When I promoted my machine and configuration was at last stages, my DC (only DC of root domain in my test lab) was switched off. I cancel the wizard, turned on the DC and then again ran the promotion wizard but this time with new domain name.
At last stages of promotion I got the following error (shown in following screen shot)
I ran repadmin.exe on my domain controller and it gave the following results (shown in following screen shot). I have few DCs turned off and some are removed but they still exist in site and services.
Please help me find out whats causing the error.
/ Karim
Question
Answers
-
Hi,
Have you checked the health of your DC by running dcdiag command?
And if you have removed DCs, please make sure that you clean up its metadata: https://technet.microsoft.com/en-us/library/cc816907%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
And regarding to troubleshootAD Replication error: The DSA operation is unable to proceed because of a DNS lookup failure, please refer to the following KB to have a try:
https://support.microsoft.com/en-us/help/2021446/troubleshooting-ad-replication-error-8524-the-dsa-operation-is-unable-to-proceed-because-of-a-dns-lookup-failure
Best Regards,
Wendy JiangPlease remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Marked as answer by Karim Buzdar Wednesday, April 12, 2017 11:20 AM
All replies
-
-
>>I have few DCs turned off and some are removed but they still exist in site and services.
You must delete them manually.
>>I ran repadmin.exe on my domain controller and it gave the following results (shown in following screen shot)
What s srv02? Is it alive or turned off or removed?
MCSAnykey
- Edited by Artem S. Smirnov Saturday, April 8, 2017 4:44 PM
-
-
-
Hi,
Have you checked the health of your DC by running dcdiag command?
And if you have removed DCs, please make sure that you clean up its metadata: https://technet.microsoft.com/en-us/library/cc816907%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396
And regarding to troubleshootAD Replication error: The DSA operation is unable to proceed because of a DNS lookup failure, please refer to the following KB to have a try:
https://support.microsoft.com/en-us/help/2021446/troubleshooting-ad-replication-error-8524-the-dsa-operation-is-unable-to-proceed-because-of-a-dns-lookup-failure
Best Regards,
Wendy JiangPlease remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Marked as answer by Karim Buzdar Wednesday, April 12, 2017 11:20 AM
-
Seems to be a DNS issue, change of IP stooped the replication, try to update SRV02 DNS entry on server2016
http://www.windowstricks.in/2009/07/how-to-resolve-island-issue.html
Regards,
Ganesamoorthy.S
www.windowstricks.in) -
Thank you everyone for your help.
I cleaned active directory and it worked./ Karim
- Proposed as answer by Wendy JiangModerator Thursday, April 13, 2017 2:00 AM