複寫錯誤 1256 年遠端系統不是可用Replication error 1256 The remote system is not available

適用於:Windows Server 2016、Windows Server 2012 R2、Windows Server 2012Applies To: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012

此文章將描述包括症狀、原因和案例解析度步驟時 Active Directory︰ 複寫失敗,錯誤 1256 年:遠端系統尚未提供。This article describes the symptoms, cause, and resolution steps for cases when Active Directory replication fails with error 1256: The remote system is not available. 症狀原因解析度 Symptoms Cause Resolution
症狀 DCDIAG 報告的 Active Directory 複寫測試失敗,錯誤 1256 年:「遠端系統無法使用。」Starting test: Replications [Replications Check, <Destination DC>] A recent replication attempt failed: From <source DC> to <destination DC> Naming Context: <directory partition DN path> The replication generated an error (1256): The remote system is not available. For information about network troubleshooting, see Windows Help. The failure occurred at <date> <time> The last success occurred at <date> <time> REPADMIN。EXE︰ 複寫失敗的狀態 1256 年的報告。REPADMIN 命令通常引用 1256 年狀態,包括但不是限於: Symptoms The DCDIAG reports that the Active Directory Replications test has failed with error 1256: "The remote system is not available."Starting test: Replications [Replications Check, <Destination DC>] A recent replication attempt failed: From <source DC> to <destination DC> Naming Context: <directory partition DN path> The replication generated an error (1256): The remote system is not available. For information about network troubleshooting, see Windows Help. The failure occurred at <date> <time> The last success occurred at <date> <time> REPADMIN.EXE reports that a replication attempt has failed with status 1256.REPADMIN commands that commonly cite the 1256 status include but are not limited to:
REPADMIN /REPLSUMREPADMIN /SHOWREPLREPADMIN /REPLSUMREPADMIN /SHOWREPLREPADMIN 進行REPADMIN /FAILCACHEREPADMIN /SHOWREPSREPADMIN /FAILCACHE
範例輸出從「REPADMIN 進行」描繪輸入的複寫 LonEMEADC 從「遠端系統不適」錯誤的 LonContosoDC 失敗如下所示:Repadmin: running command /showrepl against full DC localhost LondonLONCONTOSODC DSA Options: IS_GC Site Options: (none) DSA object GUID: a29bbfda-8425-4cb9-9c66-8e07d505a5c6 DSA invocationID: d58a6322-6a28-4708-82d3-53b7dcc13c1a ==== INBOUND NEIGHBORS ====================================== <snip> DC=ForestDnsZones,DC=Contoso,DC=com LondonLONEMEADC via RPC DSA object GUID: cd691606-63d1-4cc8-b77a-055674ba569d Last attempt @ 2010-06-10 17:35:46 failed, result 1256 (0x4e8): The remote system is not available. For information about network troubleshooting, see Windows Help. <#> consecutive failure(s). Last success @ <date> <time>. NTDS KCC、NTDS 複寫或 ActiveDirectory_DomainService 事件 1256 年狀態的登入 directory 服務事件登入。Sample output from "REPADMIN /SHOWREPS" depicting inbound replication from LonEMEADC to LonContosoDC failing with "The remote system is not available" error is shown below: Repadmin: running command /showrepl against full DC localhost LondonLONCONTOSODC DSA Options: IS_GC Site Options: (none) DSA object GUID: a29bbfda-8425-4cb9-9c66-8e07d505a5c6 DSA invocationID: d58a6322-6a28-4708-82d3-53b7dcc13c1a ==== INBOUND NEIGHBORS ====================================== <snip> DC=ForestDnsZones,DC=Contoso,DC=com LondonLONEMEADC via RPC DSA object GUID: cd691606-63d1-4cc8-b77a-055674ba569d Last attempt @ 2010-06-10 17:35:46 failed, result 1256 (0x4e8): The remote system is not available. For information about network troubleshooting, see Windows Help. <#> consecutive failure(s). Last success @ <date> <time>. NTDS KCC, NTDS Replication, or ActiveDirectory_DomainService events with the 1256 status are logged in the directory service event log.
事件編號Event ID事件來源Event Source事件字串Event String
1085時,才會登入事件 1085 NTDS 診斷值」5 複寫事件]已設定為 1 或更高版本。1085Event 1085 is logged only if the NTDS Diagnostics value "5 Replication Events" has been set to a value of 1 or higher.NTDS 複寫ActiveDirectory_DomainServiceNTDS ReplicationActiveDirectory_DomainService事件內部:Active Directory Domain Services 與 directory 服務下列網路位址,不可能會同步下列 directory 磁碟分割。Internal event: Active Directory Domain Services could not synchronize the following directory partition with the directory service at the following network address.
13081308NTDS KCCActiveDirectory_DomainServiceNTDS KCCActiveDirectory_DomainService後續複製下列網域控制站的嘗試一直無法偵測知識一致性檢查程式 (KCC)。複製下列 directory 服務連續嘗試一直無法偵測知識一致性檢查程式 (KCC)。The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following domain controller has consistently failed. The Knowledge Consistency Checker (KCC) has detected that successive attempts to replicate with the following directory service has consistently failed.
原因 目的地俠失敗繫結至來源俠時使用 RPC win32 錯誤碼會顯示在Repsfrom該磁碟分割的狀態通常架構或組態磁碟分割因為其複寫,較高優先順序。RPC 繫結失敗之後,若要清除該相同來源俠目的地 Dc 佇列執行清理維持常態。這是不想使用無法將它連接到俠複製浪費時間來完成。它已不會嘗試從佇列已經清除的磁碟分割的同步,因為已登入 1256 年狀態。在目的地俠位置複製架構、設定及幾個 GC 非寫入磁碟分割的來源 DC 案例中,造成 RPC 繫結失敗架構與設定分割 win32 錯誤狀態是登入。目的地俠將取消擱置中複寫工作剩餘磁碟分割,然後登入 win32 錯誤 1256 年的狀態。 在 [摘要:1256 年已登入為每個分割目的 DC 取消因為連接失敗之前發生的來源 DC 同步要求的結果複寫狀態。 Cause When the destination DC fails to bind to the source DC using RPC, a win32 error code appears in the Repsfrom status for that partition - usually Schema or Configuration partitions because they are replicated at a higher priority. After an RPC bind failure has occurred, a cleanup routine will run to clear the destination DCs queue from that same source DC. This is done to avoid wasting time attempting to replicate with a DC that it cannot connect to. Because it has not attempted a sync for the partitions that have been cleared from the queue, a status 1256 is logged. In a scenario where destination DC replicates Schema, Configuration, and several GC non-writable partitions from the source DC, the win32 error status for the Schema and Configuration partitions that caused the RPC bind failure is logged. The destination DC will then cancel the pending replication tasks for the remaining partitions and log win32 error 1256 for the status. In summary: 1256 is logged as the replication status per partition as a result of the destination DC cancelling the sync request from the source DC due to a connectivity failure previously encountered.
解析度 win32 錯誤 1256 年不應該會對焦的疑難排解努力,改為尋找 led RPC 繫結故障複寫狀態,然後依照參考 TechNet 上的對應的文章。Microsoft 知識庫文章2498185http://support.microsoft.com/kb/2498185包含疑難排解文章 Active Directory 複寫的清單。 為了判斷實際 win32 錯誤疑難排解使用下列方法: 檢視repadmin 進行/showrepl目的地俠輸出。 找出來源俠輸出清單所有 win32 狀態都訊息每個分割區中的。 的 win32 狀態列出的不是 1256 年應該疑難排解努力對焦。 使用repadmin /showrepl * /csv輸出: 篩選欄 K上次失敗狀態:,清除0(空白) 篩選欄 C,目的 DSA:清除(全選),然後選取位置登 1256 年狀態 DC。 如果 1256 年登入多個來源俠、篩選欄 F,來源 DSA:,清除(全選),然後選取一個 DC 縮小。 欄 K,上次失敗狀態會列出 1256s,以及真實 win32 錯誤導致 RPC 繫結失敗。 在以下的範例,win32 錯誤 1722 年已登入的設定和架構分割和應該會對焦的疑難排解。 Resolution The win32 error 1256 should not be the focus of troubleshooting efforts, instead find the replication status that led to the RPC bind failure and then follow the corresponding article on TechNet. Microsoft Knowledge Base article 2498185http://support.microsoft.com/kb/2498185 contains a list of Active Directory Replication troubleshooting articles. In order to determine the actual win32 error to troubleshoot use one of the following methods: View repadmin /showreps or /showrepl output on the destination DC. Identify Source DC in the output and list all win32 status messages per partition. The win32 status that is listed that is not a 1256 should be the focus of troubleshooting efforts. Using repadmin /showrepl * /csv output: Filter column K, Last Failure Status:, clear 0 and (Blanks). Filter column C, Destination DSA: Clear (Select All) and select just the DC where the 1256 status is logged. If 1256 is logged on more than one Source DC, Filter column F, Source DSA:, clear (Select All) and Select just one DC to narrow the focus. Column K, Last Failure Status will list the 1256s along with the real win32 error that led to the RPC bind failure. In the following example, win32 error 1722 is logged for the Configuration and Schema partitions and should be the focus of troubleshooting.
BB CC DD 電子E FF HH I J 鍵J KK
目的地 DSA 網站Destination DSA Site 目的地 DSADestination DSA 命名操作Naming Context 來源 DSA 網站Source DSA Site 來源 DSASource DSA 失敗次數Number of Failures 上次失敗Last Failure Time 上次成功Last Success Time 上次成功狀態Last Success Status
倫敦London LONCONTOSODCLONCONTOSODC DATA-CN = 設定,俠 = Contoso 特區 = comCN=Configuration,DC=Contoso,DC=com 倫敦London LONEMEADCLONEMEADC 1111 6/10/2010 17:356/10/2010 17:35 6/10/2010 14:506/10/2010 14:50 17221722
倫敦London LONCONTOSODCLONCONTOSODC DATA-CN = 區結構描述 DATA-CN = 設定,俠 = Contoso 特區 = comCN=Schema,CN=Configuration,DC=Contoso,DC=com 倫敦London LONEMEADCLONEMEADC 1111 6/10/2010 17:356/10/2010 17:35 6/10/2010 14:506/10/2010 14:50 17221722
倫敦London LONCONTOSODCLONCONTOSODC DC = ForestDnsZones 特區 = Contoso 特區 = comDC=ForestDnsZones,DC=Contoso,DC=com 倫敦London LONEMEADCLONEMEADC 1111 6/10/2010 17:356/10/2010 17:35 6/10/2010 14:506/10/2010 14:50 12561256
倫敦London LONCONTOSODCLONCONTOSODC 俠 = corp,俠 = Contoso 特區 = comDC=corp,DC=Contoso,DC=com 倫敦London LONEMEADCLONEMEADC 1111 6/10/2010 17:356/10/2010 17:35 6/10/2010 14:506/10/2010 14:50 12561256
倫敦London LONCONTOSODCLONCONTOSODC 俠 = EMEA 特區 = Contoso 特區 = comDC=EMEA,DC=Contoso,DC=com 倫敦London LONEMEADCLONEMEADC 1111 6/10/2010 17:356/10/2010 17:35 6/10/2010 14:506/10/2010 14:50 12561256
倫敦London LONCONTOSODCLONCONTOSODC DC = apac,DC = Contoso 特區 = comDC=apac,DC=Contoso,DC=com 倫敦London LONEMEADCLONEMEADC 1111 6/10/2010 17:356/10/2010 17:35 6/10/2010 14:506/10/2010 14:50 12561256
起始之間來源和目的地 Dc 使用 repadmin 複寫手動同步。 Repadmin /replicate DestinationDC SourceDC DN of partition reporting status 1256 (使用/readonly切換 GC 磁碟分割或/selsecrets切換目的地是否 RODC) repadmin /replicate loncontosodc lonemeadc.emea.contoso.com dc=forestdnszones,dc=contoso,dc=com DsReplicaSync() failed with status 1722 (0x6ba): The RPC server is unavailable. 後手動起始複寫狀態已經從 1256 年 1722 年的磁碟分割,需要注意: Initiate a manual replication sync between source and destination DCs using repadmin. Repadmin /replicate DestinationDC SourceDC DN of partition reporting status 1256 (use /readonly switch for GC partition or /selsecrets switch if destination is an RODC) repadmin /replicate loncontosodc lonemeadc.emea.contoso.com dc=forestdnszones,dc=contoso,dc=com DsReplicaSync() failed with status 1722 (0x6ba): The RPC server is unavailable. Take note that after manually initiating replication for the partition that the status has changed from 1256 to 1722:
BB CC DD 電子E FF HH I J 鍵J KK
目的地 DSA 網站Destination DSA Site 目的地 DSADestination DSA 命名操作Naming Context 來源 DSA 網站Source DSA Site 來源 DSASource DSA 失敗次數Number of Failures 上次失敗Last Failure Time 上次成功Last Success Time 上次成功狀態Last Success Status
倫敦London LONCONTOSODCLONCONTOSODC DATA-CN = 設定,俠 = Contoso 特區 = comCN=Configuration,DC=Contoso,DC=com 倫敦London LONEMEADCLONEMEADC 1111 6/10/2010 17:356/10/2010 17:35 6/10/2010 14:506/10/2010 14:50 17221722
倫敦London LONCONTOSODCLONCONTOSODC DATA-CN = 區結構描述 DATA-CN = 設定,俠 = Contoso 特區 = comCN=Schema,CN=Configuration,DC=Contoso,DC=com 倫敦London LONEMEADCLONEMEADC 1111 6/10/2010 17:356/10/2010 17:35 6/10/2010 14:506/10/2010 14:50 17221722
倫敦London LONCONTOSODCLONCONTOSODC DC = ForestDnsZones 特區 = Contoso 特區 = comDC=ForestDnsZones,DC=Contoso,DC=com 倫敦London LONEMEADCLONEMEADC 1212 6/10/2010 17:356/10/2010 17:35 6/10/2010 14:506/10/2010 14:50 17221722
倫敦London LONCONTOSODCLONCONTOSODC 俠 = corp,俠 = Contoso 特區 = comDC=corp,DC=Contoso,DC=com 倫敦London LONEMEADCLONEMEADC 1111 6/10/2010 17:356/10/2010 17:35 6/10/2010 14:506/10/2010 14:50 12561256
倫敦London LONCONTOSODCLONCONTOSODC 俠 = EMEA 特區 = Contoso 特區 = comDC=EMEA,DC=Contoso,DC=com 倫敦London LONEMEADCLONEMEADC 1111 6/10/2010 17:356/10/2010 17:35 6/10/2010 14:506/10/2010 14:50 12561256
倫敦London LONCONTOSODCLONCONTOSODC DC = apac,DC = Contoso 特區 = comDC=apac,DC=Contoso,DC=com 倫敦London LONEMEADCLONEMEADC 1111 6/10/2010 17:356/10/2010 17:35 6/10/2010 14:506/10/2010 14:50 12561256
疑難排解 Active Directory 操作失敗,錯誤 1256 年:遠端系統尚未提供。 http://support.microsoft.com/kb/2200187 Troubleshooting Active Directory operations that fail with error 1256: The remote system is not available. http://support.microsoft.com/kb/2200187