複製錯誤 8452 命名操作正被移除或不會從指定的伺服器複寫Replication error 8452 The naming context is in the process of being removed or is not replicated from the specified server

本文內容

本主題解釋，包括症狀、原因，以及如何解析 Active Directory 複寫錯誤 8452：命名操作正被移除或不會複寫從指定的伺服器。This topic explains symptoms, causes and how to resolve Active Directory replication error 8452: The naming context is in the process of being removed or is not replicated from the specified server.症狀造成解析度 Symptoms Causes Resolutions 症狀DCDIAG 報告的 Active Directory 複寫測試失敗，錯誤狀態碼 (8452):「命名操作正被移除或不會從指定的伺服器複寫」。Testing server: <site name><destination dc name>
Starting test: Replications
* Replications Check
[Replications Check,<destination DC name] A recent replication attempt failed:
From <source DC> to <destination DC>
Naming Context: <directory partition DN path>
The replication generated an error (8452):
The naming context is in the process of being removed or is not replicated from the specified
server. The failure occurred at <date> <time>.
The last success occurred at <date> <time>.
3 failures have occurred since the last success.REPADMIN。EXE 報告的最後一個︰ 複寫失敗的狀態 8452。REPADMIN 命令通常引用 8452 狀態，包括但不是限於：SymptomsDCDIAG reports that Active Directory Replications test has failed with error status code (8452): "The naming context is in the process of being removed or is not replicated from the specified server."Testing server: <site name><destination dc name>
Starting test: Replications
* Replications Check
[Replications Check,<destination DC name] A recent replication attempt failed:
From <source DC> to <destination DC>
Naming Context: <directory partition DN path>
The replication generated an error (8452):
The naming context is in the process of being removed or is not replicated from the specified
server. The failure occurred at <date> <time>.
The last success occurred at <date> <time>.
3 failures have occurred since the last success.REPADMIN.EXE reports that the last replication attempt has failed with status 8452.REPADMIN commands that commonly cite the 8452 status include but are not limited to:

REPADMIN 進行REPADMIN /REPLSUMREPADMIN /SHOWREPSREPADMIN /REPLSUM

REPADMIN /SYNCALLREPADMIN /SYNCALL

下列範例輸出從「REPADMIN 進行」CONTOSO-DC2 從顯示輸入的複寫，以 CONTOSO lax-dc1 失敗與「命名操作正被移除或不會從指定的伺服器複寫」錯誤：Default-First-Site-NameCONTOSO-DC1
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: b6dc8589-7e00-4a5d-b688-045aef63ec01
DSA invocationID: b6dc8589-7e00-4a5d-b688-045aef63ec01
==== INBOUND NEIGHBORS ======================================
DC=contoso,DC=com
Default-First-Site-NameCONTOSO-DC2 via RPC
DSA object GUID: 74fbe06c-932c-46b5-831b-af9e31f496b2
Last attempt @ <date> <time> failed, result 8452 (0x2104):
The naming context is in the process of being removed or is not replicated from the specified server.
<#> consecutive failure(s).
Last success @ <date> <time>.
在 Active Directory 網站和服務，如果您使用滑鼠右鍵按一下連接物件並按一下 [複製現在，錯誤「命名操作正被移除或不會從指定的伺服器複寫。」連接物件來源俠上按一下滑鼠右鍵，然後選擇 [「立即複寫「失敗，並「命名操作正被移除或不會從指定的伺服器複寫」。下方螢幕上會顯示錯誤訊息文字和螢幕擷取畫面：對話方塊的標題文字：立即複寫對話方塊的訊息文字：下列錯誤同步命名操作時發生<directory 磁碟分割名稱 %>的網域控制站<來源俠>網域控制站<目的地俠>: 命名操作正被移除或不會從指定的伺服器複寫。將不會繼續操作。NTDS KCC、NTDS 一般或 Microsoft-Windows-ActiveDirectory_DomainService 事件 8452 狀態的登入 directory 服務事件登入。Active Directory 事件通常引用 8452 狀態，包括但不是限於：The following sample output from "REPADMIN /SHOWREPS" shows inbound replication from CONTOSO-DC2 to CONTOSO-DC1 failing with the "The naming context is in the process of being removed or is not replicated from the specified server" error:Default-First-Site-NameCONTOSO-DC1
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: b6dc8589-7e00-4a5d-b688-045aef63ec01
DSA invocationID: b6dc8589-7e00-4a5d-b688-045aef63ec01
==== INBOUND NEIGHBORS ======================================
DC=contoso,DC=com
Default-First-Site-NameCONTOSO-DC2 via RPC
DSA object GUID: 74fbe06c-932c-46b5-831b-af9e31f496b2
Last attempt @ <date> <time> failed, result 8452 (0x2104):
The naming context is in the process of being removed or is not replicated from the specified server.
<#> consecutive failure(s).
Last success @ <date> <time>.
In Active Directory Sites and Services, if you right-click the connection object and click Replicate now, the error "The naming context is in the process of being removed or is not replicated from the specified server." Right-clicking on the connection object from a source DC and choosing "replicate now" fails with "The naming context is in the process of being removed or is not replicated from the specified server.". The on-screen error message text and screenshot is shown below:Dialog title text: Replicate NowDialog message text: The following error occurred during the attempt to synchronize naming context <%directory partition name%> from Domain Controller <Source DC> to Domain Controller <Destination DC>: The naming context is in the process of being removed or is not replicated from the specified server.The operation will not continue.NTDS KCC, NTDS General or Microsoft-Windows-ActiveDirectory_DomainService events with the 8452 status are logged in the directory service event log.Active Directory events that commonly cite the 8452 status include but are not limited to:

事件編號Event ID

事件來源Event Source

事件字串Event String

15861586

NTDS 一般NTDS General

檢查點 PDC 未成功。The checkpoint with the PDC was unsuccessful.檢查點程序將會重試一次在四小時的時間。The checkpointing process will be retried again in four hours.完整進行同步處理的安全性資料庫舊版的網域控制站可能如果升級之前的下一步成功檢查點 pdc 這台電腦。A full synchronization of the security database to downlevel domain controllers may take place if this machine is promoted to be the PDC before the next successful checkpoint.傳回錯誤：命名操作正被移除或不會複寫從指定的伺服器。The error returned was: The naming context is in the process of being removed or is not replicated from the specified server.

讓通常會發生這個錯誤網域控制站的初始複寫複寫拓撲 mca 複寫拓撲定義在 Active Directory 目的地網域控制站的複本。自然時發生錯誤修改複寫 Active Directory 森林中的拓撲：新增或移除的磁碟分割或森林（也就是促銷或降級的第一個或最後一個網域控制站網域，或新增或移除應用程式的磁碟分割，包括預設 DNS 應用程式的磁碟分割）。的新增或移除的磁碟分割 directory 現有的網域控制站（也就是促銷或降級通用伺服器或新增或移除應用程式的磁碟分割）。中複寫拓撲或（的新的網域控制站，現有的網域控制站的降級升級、變更慣用或指定 bridgehead，建置替代複寫路徑回應︰ 複寫失敗或離線 Dc，以及及網站連結變更）設定的變更。錯誤可能是暫時性的來源 Dc 及的磁碟分割的每個目的 DC 也會複寫從已輸入複寫觸發複製操作，直到進行的變更上述森林中。︰ 複寫失敗避免拓撲變更森林中的端點-複寫時錯誤可能是持續。觸發 REPADMIN.EXE 遠端 (尤其是 /SYNCALL) 或「複寫現在命令」DSSITE.MSC 複本上 DC 觸發複寫 Active Directory 位置有不同的目的地俠複寫比目的 DC 有定義它的 Active Directory 位置中的磁碟分割來源網域控制站的清單。Windows 2000 的網域控制站的視這個時發生錯誤的通用伺服器降級時保守型移除唯讀磁碟分割中的物件。在 GC 降級物件移除大幅改進 Windows Server 2003 及更新版本。NTDS 複寫事件 1586 年造成當已取回或傳輸未複寫直接合作夥伴的之前的角色擁有者為網域控制站 PDC FSMO 網域中的角色。中少數條件，錯誤會造成損壞屬性，例如在hasMasterNCs或msds-hasMasterNCs。這篇文章「詳細資訊」一節包含解釋列出的這篇文章徵一節中的診斷及系統管理工具產生 8452 錯誤的原因。在 [摘要] 錯誤 8452 交貨下列的任何人是否：時 DC1 <-DC2 複寫 NC 的車載機起始、DC1 還有從 DC2 NC 不複本連結。時 DC1 <-複寫車載機起始的 NC DC2，NC 正被移除 DC2 上。網域混合的環境中 PDC FSMO 的角色針對從 DC2 DC1，但在 DC1 從 DC2 不複本連結。CausesThis error most commonly occurs when replication topology on a domain controller that initiates replication differs from the replication topology defined on the copy of Active Directory on the destination domain controller.The error naturally occurs when the replication topology in an Active Directory forest is modified by:Adding or removing partitions to or from the forest (that is, the promotion or demotion of the first or last domain controller in a domain, or the addition or removal of an application partition, including default DNS application partitions).The addition or removal of directory partitions on existing domain controllers (that is, the promotion or demotion of a global catalog server or addition or removal of an application partition).Changes in replication topology or settings (that is, the promotion of new DCs, the demotion of existing DCs , changes to preferred or nominated bridgeheads, the building of alternate replication paths in response to replication failures or offline DCs, as well as site and site link changes).The error can be transient in a forest undergoing the changes above until the set of source DCs and partitions that each destination DC replicates from has inbound replicated by triggering replication operations.The error can be persistent when replication failures prevent the end-to-end replication of topology changes in the forest. The error is most commonly seen in replication scenarios triggered by REPADMIN.EXE remotely (especially /SYNCALL) or the "replicate now command" in DSSITE.MSC where the copy of Active Directory on the DC triggering replication has a different list of source DCs that a destination DC replicates partitions from than what the destination DC has defined in its copy of Active Directory. Windows 2000 domain controllers are particularly prone to this error during demotion of global catalog servers as they are slow to remove objects from read-only partitions. Object removal during GC demotion improved dramatically on Windows Server 2003 and later. The NTDS Replication event 1586 is caused when the PDC FSMO role for the domain has been seized or transferred to a domain controller that was not a direct replication partner of the previous role holder.In rare conditions, the error can be caused by corruption in attributes like hasMasterNCs or msds-hasMasterNCs.The "More Information" section of this article contains explanations as to why the diagnostic and administrative tools listed in the Symptoms section of this article generate the 8452 error.In summary, Error 8452 happens if anyone of the following is true:When DC1 <- DC2 replication is initiated for a NC, on DC1 there is no replica link for the NC from DC2.When DC1 <- DC2 replication in initiated for a NC, the NC is in the process of being removed on DC2.In mixed domain environment, PDC FSMO role is transferred from DC2 to DC1, but on DC1 there is no replica link from DC2.解析度等。如前面所提到，此條件為通常暫時性，而且不一樣保證疑難排解。如果複寫拓撲的這篇文章原因一節中列出的類型的變更的樹系 Active Directory 中進行，等待時間自動修正的錯誤條件。的「repadmin /syncall」命令對等使用避免之前網域控制站提出複寫和目的地 Dc 複寫同意來源網域控制站的相關和 directory 磁碟分割複寫。原始做在正確的位置。推入和拉變更連接物件和周圍所需的磁碟分割變更直接移如果您想要執行立即複寫來 Active Directory 網站和服務 DC1 DC2 DC3 從命令，對焦 DC3 DC2 來操作。如果錯誤會造成根本原因 #3，然後使用者提供的正確輸入之後，將不會發生錯誤。例如案例 #3 個 #1 中案例中輸入正確的使用者如果<src DC>的在<目的地 DC>從複本連結<src 俠>的<NC>，將會執行 repadmin /replicate 命令已成功。解析封鎖端點-複寫︰ 複寫失敗。REPADMIN /REPLICATENTDS 複寫事件 1586 年NTDS 複寫事件 1586，轉移的 Active Directory 網域控制站 PDC 模擬器角色目前複寫直接合作夥伴的上一個肯定。如果的通用 Windows 2000 的伺服器降級導致錯誤，請執行批次檔」Directory 服務忙才能完成作業」一節中KB 249256https://support.microsoft.com/default.aspx?scid=kb;EN-US;249256 (https://support.microsoft.com/default.aspx?scid=kb;EN-US;249256)。ResolutionsWait. As mentioned, this condition is usually transient and does not normally warrant troubleshooting.If replication topology changes of the type listed in the Cause section of this article are taking place in your Active Directory forest, wait for the error condition to correct itself with time.Avoid the use of the "repadmin /syncall" command and equivalents until domain controllers initiating replication and the destination DCs being replicated to agree about the source DCs and directory partitions being replicated.Make originating changes in the right places.Push and Pull changes to connection objects and partition changes around as requiredGo DirectIf you want to run the Replicate now command from DC3 to DC2 from Active Directory Sites and Services on DC1, focus the operation on DC3 to DC2.If the error is caused by root cause #3, then after the user gives the correct input, the error will not happen. For example, in case #1 of scenario #3, if the user input a correct <src DC> such that on <dest DC> there is a replica link from <src DC> for <the NC>, the repadmin /replicate command will be executed successfully.Resolve replication failures that block end-to-end replication.REPADMIN /REPLICATENTDS Replication event 1586For NTDS Replication event 1586, transfer the PDC emulator role to an Active Directory domain controller that is currently a direct replication partner of the previous PDC emulator.If the error is caused by the demotion of a Windows 2000 global catalog server, execute the batch file in the "Directory Service is too busy to complete the operation" section of KB 249256https://support.microsoft.com/default.aspx?scid=kb;EN-US;249256 (https://support.microsoft.com/default.aspx?scid=kb;EN-US;249256).更多的資訊More InformationREPADMIN /SYNCALL REPADMIN /syncall 作業會使 DC 起始複寫其來源複寫合作夥伴的所有，並讓來源複寫合作夥伴起始複寫他們來源複寫合作夥伴的所有等等。，例如假設有複寫拓撲 DC1 <-DC2 <-DC3。如果您執行 DC1」repadmin /syncall」，它將會起始下列複寫：DC2 <-DC3，以及 DC1 <-DC2。有兩個位置錯誤 8452 可能會發現在本案例中的案例：案例 1：變更，讓 DC2 輸入複寫 DC4 的因此目前拓撲變成 DC1 複寫拓撲<-DC2 <-DC4。如果您之前 DC2 了解執行 DC1 上「repadmin /syncall」<-DC4 拓撲變更輸入的複製 DC1、syncall 作業將會起始 DC2 <-DC3 複寫因為 DC1 仍然有舊複寫拓撲儲存在本機。因為 DC2 這時上 KCC 建立 DC4 從複本連結且刪除複本連結 DC3，從 DC2 複寫從<-DC3 無法執行及操作登 8452 錯誤。案例 2：假設上 DC3 NC 正在移除您在執行時「repadmin /syncall <NC>] DC1 上。DC2 <-DC3 複寫初始化以前一樣。在 DC3 NC 正被移除，因為它不是有效複寫來源，並會出現錯誤 8452。REPADMIN /SYNCALL The REPADMIN /syncall operation will cause a DC to initiate replication from all of its source replication partners and make the source replication partners initiate replication from all of their source replication partners, and so on. For example, suppose we have a replication topology DC1 <- DC2 <- DC3. If you run "repadmin /syncall" on DC1, it will initiate the following replication: DC2 <- DC3, and DC1 <- DC2.There are two cases where error 8452 might be observed in this scenario:Case 1: Change the replication topology to make DC2 inbound replicate from DC4 so that the current topology becomes DC1 <- DC2 <- DC4.If you run "repadmin /syncall" on DC1 before knowledge of the DC2 <- DC4 topology change inbound replicates to DC1, the syncall operation will initiate DC2 <- DC3 replications because DC1 still has the old replication topology stored locally. Because on DC2 at this moment KCC has created a replica link from DC4 and has deleted the replica link from DC3, the replication from DC2 <- DC3 cannot be executed and the operation logs error 8452.Case 2: Suppose a NC on DC3 is being removing when you run "repadmin /syncall <the NC>" on DC1. DC2 <- DC3 replication will be initiated as before. Because the NC on DC3 is in the process of being removed, it is not a valid replication source, and the error 8452 appears.Active Directory Sites and Services (DSSITE.MSC) -> Replicate NowThe Active Directory Sites and Services snap-in (DSSITE.MSC) uses the topology information stored in the local copy of Active Directory. Given the replication topology DC1 <- DC2 <- DC3, a connection object exists under the NTDS Settings object of DC2. This connection object represents the route for DC2 to inbound replicate a NC (or multiple NCs) from DC3. If you right-click on this connection object and select Replicate now, DC3 initiates replication from DC2.As in the REPADMIN /SYNCALL example, there are also two cases where we might observe error 8452:Case 1: Suppose we change the replication topology on DC2 to make it inbound replicate from DC4. The new replication topology is DC1 <- DC2 <- DC4. Until knowledge of this this topology change outbound replicates to DC1, the topology on DC1 is still the old topology of DC1 <- DC2 <- DC3. Starting the Active Directory Sites and Services UI focused on DC1s copy of Active Directory still shows that DC2 has an inbound connection object from source DC3. Right-clicking on DC3's inbound connection object from DC2 and choosing Replicate now will initiate a DC2 <- DC3 replication on DC2. However, the KCC on DC2 already removed the replica link inbound replicating to DC2 from DC3 and created a replica link to DC2. Because the replication attempt DC2 <-> DC2 cannot be executed, the request fails error 8452.Case2: Suppose we are removing a NC on DC3 when we right-click the connection object and select Replicate now on DC1 to initiate DC2 <- DC3 replication for this NC. Because the NC on DC3 is in the process of being removed, DC3 is not a valid replication source, and error 8452 appears.Active Directory Sites and Services (DSSITE.MSC) -> Replicate NowThe Active Directory Sites and Services snap-in (DSSITE.MSC) uses the topology information stored in the local copy of Active Directory. Given the replication topology DC1 <- DC2 <- DC3, a connection object exists under the NTDS Settings object of DC2. This connection object represents the route for DC2 to inbound replicate a NC (or multiple NCs) from DC3. If you right-click on this connection object and select Replicate now, DC3 initiates replication from DC2.As in the REPADMIN /SYNCALL example, there are also two cases where we might observe error 8452:Case 1: Suppose we change the replication topology on DC2 to make it inbound replicate from DC4. The new replication topology is DC1 <- DC2 <- DC4. Until knowledge of this this topology change outbound replicates to DC1, the topology on DC1 is still the old topology of DC1 <- DC2 <- DC3. Starting the Active Directory Sites and Services UI focused on DC1s copy of Active Directory still shows that DC2 has an inbound connection object from source DC3. Right-clicking on DC3's inbound connection object from DC2 and choosing Replicate now will initiate a DC2 <- DC3 replication on DC2. However, the KCC on DC2 already removed the replica link inbound replicating to DC2 from DC3 and created a replica link to DC2. Because the replication attempt DC2 <-> DC2 cannot be executed, the request fails error 8452.Case2: Suppose we are removing a NC on DC3 when we right-click the connection object and select Replicate now on DC1 to initiate DC2 <- DC3 replication for this NC. Because the NC on DC3 is in the process of being removed, DC3 is not a valid replication source, and error 8452 appears.REPADMIN /REPLICATE 或 REPADMIN /SYNC的 repadmin 複寫（或同步）命令觸發俠的目的地來源俠立即複寫命名操作（directory 磁碟分割）。其（簡體）語法：repadmin /replicate <dest DC> <src DC> <replicated NC>有兩個觸發錯誤 repadmin /replicate（或同步）命令時用於起始複寫 8452 案例：案例 1: <src DC>參數不是合作夥伴的複寫<目的地 DC>的<複寫 NC>。例如，我們已複寫拓撲 DC1 <-DC2 <-DC3 DC2 同步來從 DC3 NC。如果我們撥打電話：repadmin /replicate DC2 DC1 <the NC>DC2 將會起始複寫 DC1。因為 DC2 不需要從連結複本 DC1 NC，此複寫的無法執行，並會出現錯誤 8452。案例 2: NC 時，會被移除 src 俠上執行下列命令：repadmin /replicate <dest DC> <src DC> <the NC>在本案例中<src DC>有效複寫來源並不會出現錯誤 8452。REPADMIN /REPLICATE or REPADMIN /SYNCThe replicate (or sync) command of repadmin triggers immediate replication of a naming context (directory partition) to a destination DC from a source DC. Its (simplified) syntax is:repadmin /replicate <dest DC> <src DC> <replicated NC>There are two cases that will trigger error 8452 when the repadmin /replicate (or sync) command is used to initiate a replication:Case 1: the <src DC> parameter is not a replication partner of <dest DC> for <replicated NC>. For example, we have a replication topology DC1 <- DC2 <- DC3 in which DC2 syncs a NC from DC3. If we call: repadmin /replicate DC2 DC1 <the NC>DC2 will initiate replication from DC1. Because DC2 does not have a replica link from DC1 for the NC, this replication cannot be executed, and error 8452 appears.Case 2: the NC is being removed on src DC when the following command is run: repadmin /replicate <dest DC> <src DC> <the NC>In this case, <src DC> is not a valid replication source and error 8452 appears.DCDIAG的 repadmin showrepl（或 showreps）命令針對每個來源網域控制站的目標 DC 有輸入的連接物件報告複寫狀態。檢查即時複寫之間網域控制站 dcdiag 複寫測試。如果 repadmin 也會顯示錯誤 8452 /showrepl 報告或 dcdiag//test︰ 複寫報告，是因為的複製的 NC 已停用來源俠上一次複寫現象時。DCDIAGThe showrepl (or showreps) command of repadmin reports the replication status for each source DC from which the destination DC has an inbound connection object. The Replications test of dcdiag checks for timely replication between DCs. If error 8452 appears in a repadmin /showrepl report or dcdiag /test:replications report, the reason is that the replicated NC is being removed on the source DC when the last replication happened.NTDS 複寫事件 1586 年NTDS 複寫事件 1586 年也包含 Windows nt4.0 和 Active Directory 網域控制站在混合的網域環境中。在這個網域混合的環境，彼此 Active Directory 肯定複製到 NT 4 Bdc 使用舊版 netlogon 複寫通訊協定時使用 DS 複寫通訊協定，將複寫 Active Directory 網域控制站。在這種情形下 Active Directory PDC FSMO 角色擁有者會複寫 NT4 Bdc 通用網域中的單點。PDC 維護檢查點的每個 BDC 代表複寫最新的變更。如果 PDC 模擬器角色轉移到另一個 Active Directory domain 網域控制站，每個人 BDC 檢查點的相關資訊必須複製到新的肯定。因此新肯定必須直接複寫關係舊肯定使用。如果新肯定不會複寫直接與舊肯定（亦即上新的肯定從舊的肯定不複本連結），然後 8452 會顯示錯誤事件 1586 年。NTDS Replication Event 1586NTDS replication event 1586 is generated in a mixed domain environment which contains both Windows NT 4.0 and Active Directory domain controllers. In this mixed domain environment, Active Directory domain controllers replicate amongst themselves using the DS replication protocol, while the Active Directory PDC emulator replicates to Windows NT 4 BDCs using the legacy netlogon replication protocol. In this case the Active Directory PDC FSMO role holder is the single point for replication to NT4 BDCs in a common domain. The PDC maintains a checkpoint for each BDC representing the most recent replicated change. If the PDC emulator role is transferred to another Active Directory domain controller in the domain, the information about each individual BDC's checkpoint must be replicated to the new PDC emulator. Hence the new PDC emulator must have a direct replication relationship with the old PDC emulator. If the new PDC emulator does not replicate directly with the old PDC emulator (that is on the new PDC emulator there is no replica link from old PDC emulator), then error 8452 appears in event 1586.降級還有其他傳回 DRAERR_NoReplica 錯誤的案例。期間俠降級、DC 定位會發現 DC 複寫區域的變更。如果找到的俠不會複寫直接與即將降級 DC，DRAERR_NoReplica 將會退還和稱呼 DC 定位找到 [目標 DC。在本案例中，該錯誤未登讓它不上述。DemotionThere is another scenario that returns DRAERR_NoReplica error. During DC demotion, DC locator will find a DC to replicate local changes to. If the found DC does not replicate directly with the DC being demoted, DRAERR_NoReplica will be returned and DC locator will be called to find a destination DC. In this scenario, the error is not logged so it is not observed.
疑難排解 Active Directory 操作失敗的錯誤 8452:「命名操作正被移除或不會從指定的伺服器複寫」。
https://support.microsoft.com/kb/2023704
Active Directory 複寫型號的運作方式
https://technet.microsoft.com/library/cc772726(WS.10).aspxrepsFrom，RepsFromhttps://msdn.microsoft.com/library/cc228409(PROT.13).aspx
Troubleshooting Active Directory operations that fail with error 8452: "The naming context is in the process of being removed or is not replicated from the specified server."
https://support.microsoft.com/kb/2023704
How the Active Directory Replication Model Works
https://technet.microsoft.com/library/cc772726(WS.10).aspxrepsFrom, RepsFromhttps://msdn.microsoft.com/library/cc228409(PROT.13).aspx