Read on here. You may need to just wait a bit.
https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/replication-error-8452
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I raise a new RODC (Windows 2016 Standart), the role is only "Active Directory Domain Services", not GC.
After the first reboot, repadmin /showrepl sees all of the inbound neighbors, /replsummary sees the RODC in the list of incoming DSAs.
After 15 minutes there are no inbound neighbors, there is no RODC in the list of incoming DSAs.
When trying to replicate from the "Sites and Services" snap-in, an error is generated: "the naming context is in the process of being deleted or has not been replicated from the specified server."
There are no firewalls between RODC and RWDC.
Net share shows that the NETLOGON and SYSVOL shares have been created.
dcdiag /test:connectivity, dns passed without errors.
Thanks in advance for your help.
Read on here. You may need to just wait a bit.
https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/replication-error-8452
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
Hi Pavel,
strange indeed. If it was a matter of waiting, it should be OK now, so there is something else.
Are there any related events in the Directory Services logs on the DCs? What does "dcdiag /v" tell you?
Please try to gather some more information in order to be able to ghet the whoole picture, I think you are missing something here.
Regards,
Stoyan
Hello there,
The error message "the naming context is in the process of being deleted or has not been replicated from the specified server." is due to inconsistent AD replication.
I would like to suggest you verify your AD health using below Microsoft GUI tool (Active Directory Replication Status Tool)
https://www.microsoft.com/en-in/download/details.aspx?id=30005
Please make sure that:
-Each DC / DNS server points to its private IP address as the primary DNS server and to other internal DNS servers as secondary ones
-Each DC without DNS points to internal DNS servers as DNS servers
-Each public DNS server is set as a forwarder and not in IP addressing
Once done, run ipconfig /registerdns and restart netlogon on all DCs.
-------------------------------------------------------------------------------------------------------------------------------------------
--If the reply is helpful, please Upvote and Accept it as an answer–