none
AD复制故障 RRS feed

  • 问题

  • 我有个AD复制的故障问题,不知道能否得到版主的技术指导?
    因为问题在论坛可能说不太清楚,能知道“Windows Server”版主的邮箱地址吗?
    我期待能尽快解决我的这个问题。
    2009年4月19日 15:13

全部回复

  • 您好:
    AD复制故障原因的确很多,但大多数与DNS不能被正确解析有关,也就是DNS出现了故障!

    by-陈陈!
    silence-陈陈 双手剑的时代来临!
    2009年4月20日 0:55
  • 楼主看看我的做法怎么样:
         1.查看windows站点跟服务的AD同步复制有没有问题?
         2.分别在主AD跟辅助AD上面使用 repadmin /showrepl命令,查看是不是有复制问题,如有问题,根据错误提示来进行排错,到microsoft里面找kb资料
         3.使用dcdiag.exe以及netdiag.exe命令进行测试,查看AD的状态,也有可能是AD本身问题导致的

    Up And Up
    2009年4月20日 5:37
  • 您好!                         

     

    非常抱歉,根据论坛的规定,我们只能在论坛中为您提供技术支持。

     

    对于DC的复制排错是一个很复杂的问题,而您提供的信息比较少,无法找出问题所在。建议做以下测试:
    1. 2DC的主DNS服务器地址都指向同一台DNS服务器,察看解析是否正常。确保域名服务(DNS) 配置正确,正确的目录复制需要有正确的DNS 配置。

    2. 1DCPing另外一台DC的主机名和IP地址,察看是否能PING通,检查网络是否通畅。

    3. 使用w32tm命令,同步域内DC的时间,在命令提示符下输入:
    a. 单击开始,指向所有程序,指向附件,然后单击命令提示符。
    b. 键入 w32tm /resync,然后按 ENTER 键。

    4. 请您在命令提示符下输入:
    a. Dcdiag /v >c:\Dcdiag.txt
    b. Netdiag /debug >c:\Netdig.txt
    c. Repadmin /syncall c:\repadmin.txt

    请您将收集到的详细错误日志贴到论坛中,以便我们为您作的进一步分析。

     

    希望我的回答对您有所帮助,如果有什么不清楚的地方,请您告诉我。

     

    Tom Zhang 张一平
    Tom Zhang – MSFT
    2009年4月20日 9:28
    版主
  • 下载microsoft 的 directory service 的MPS report吧, 里面的有些对排错很有用的诊断报告,比如Dcdiag...
    2009年4月20日 9:55
  • 因为环境中DC的数较多,日志也实在较多,能否知道版主的邮箱地址进行沟通?

    以下列出其中一台DC的 dcdiag /v后的信息,请求从信息能得到协助。


    Domain Controller Diagnosis

    Performing initial setup:
       * Verifying that the local machine czdcn-ad-01, is a DC.
       * Connecting to directory service on server czdcn-ad-01.
       * Collecting site info.
       * Identifying all servers.
       * Identifying all NC cross-refs.
       * Found 79 DC(s). Testing 1 of them.
       Done gathering initial info.

    Doing initial required tests
      
       Testing server: GD-CZDCN\CZDCN-AD-01
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             * Active Directory RPC Services Check
             ......................... CZDCN-AD-01 passed test Connectivity

    Doing primary tests
      
       Testing server: GD-CZDCN\CZDCN-AD-01
          Starting test: Replications
             * Replications Check
             REPLICATION LATENCY WARNING
             CZDCN-AD-01: This replication path was preempted by higher priority work.
                from GDDCN-AD-02 to CZDCN-AD-01
                Reason: 同步尝试失败,因为目标 DC 当前正在等待从源同步新的部分属性。如果最近架构更改修改了部分属性集,此状态正常。目标部分属性集不是源部分属性集的子集。
                The last success occurred at (never).
                Replication of new changes along this path will be delayed.
             * Replication Latency Check
             REPLICATION-RECEIVED LATENCY WARNING
             CZDCN-AD-01:  Current time is 2009-04-22 17:19:14.
                CN=Schema,CN=Configuration,DC=ctc,DC=com
                   Last replication recieved from FSAD01 at 2009-01-20 09:58:48.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SZDCN-AD-01 at 2008-02-23 02:49:35.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from DGAD01 at 2009-01-20 09:55:55.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from MZAD01 at 2009-01-20 10:48:43.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-03 at 2009-03-05 04:03:04.
                   Last replication recieved from QYAD01 at 2009-01-20 09:58:48.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-04 at 2009-03-04 20:32:00.
                   Last replication recieved from SZDCN-AD-02 at 2008-02-23 01:53:09.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SZAD01 at 2009-01-20 10:48:33.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZJAD01 at 2009-01-20 10:48:46.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SGAD01 at 2009-01-20 10:48:33.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from CXJAD01 at 2009-01-20 10:48:43.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HZAD01 at 2009-01-20 09:46:06.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from STAD01 at 2009-01-20 09:49:54.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HQAD01 at 2009-01-20 10:46:58.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZHAD01 at 2009-01-20 10:48:47.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JYAD01 at 2009-01-20 09:46:38.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMDCN-AD-02 at 2009-04-16 13:52:19.
                   Last replication recieved from YJYAD01 at 2009-01-20 09:49:54.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from YFDCN-AD-01 at 2008-12-09 20:51:19.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDAD02 at 2009-01-20 10:49:31.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from MMAD01 at 2009-01-20 10:46:56.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZSAD01 at 2009-01-20 10:48:33.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GZAD01 at 2009-01-20 10:48:47.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from AD-02 at 2009-01-20 10:49:31.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZQAD01 at 2009-01-20 09:54:22.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from CZAD01 at 2009-01-20 09:58:48.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HYDCN-AD-02 at 2008-11-26 16:58:35.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-01 at 2009-03-05 03:48:54.
                   Last replication recieved from WBJAD01 at 2009-01-20 10:48:43.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from YJAD01 at 2009-01-20 09:59:05.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMAD01 at 2009-01-20 10:48:46.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMDCN-AD-01 at 2009-04-16 14:51:05.
                   Last replication recieved from YFAD01 at 2009-01-20 09:58:48.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SJJAD01 at 2009-01-20 10:48:33.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-02 at 2009-03-05 03:48:08.
                   Last replication recieved from HYDCN-AD-01 at 2008-11-26 17:52:12.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from AD-03 at 2009-01-20 10:48:33.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HYAD01 at 2009-01-20 10:46:56.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDAD01 at 2009-01-20 10:48:47.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SWAD01 at 2009-01-20 08:50:11.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Latency information for 34 entries in the vector were ignored.
                      33 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  1 had no latency information (Win2K DC). 
                CN=Configuration,DC=ctc,DC=com
                   Last replication recieved from FSAD01 at 2009-01-20 10:39:43.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SZDCN-AD-01 at 2008-02-23 02:49:33.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from DGAD01 at 2009-01-20 10:39:25.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from MZAD01 at 2009-01-20 10:48:42.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-03 at 2009-03-05 04:03:04.
                   Last replication recieved from QYAD01 at 2009-01-20 10:40:47.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-04 at 2009-03-04 20:32:00.
                   Last replication recieved from SZDCN-AD-02 at 2008-02-23 02:22:18.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SZAD01 at 2009-01-20 10:48:32.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZJAD01 at 2009-01-20 10:48:46.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SGAD01 at 2009-01-20 10:48:33.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from CXJAD01 at 2009-01-20 10:48:43.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HZAD01 at 2009-01-20 10:37:58.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from STAD01 at 2009-01-20 10:39:21.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HQAD01 at 2009-01-20 10:46:58.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZHAD01 at 2009-01-20 10:48:46.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JYAD01 at 2009-01-20 10:38:17.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMDCN-AD-02 at 2009-04-16 14:36:06.
                   Last replication recieved from YJYAD01 at 2009-01-20 10:39:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from YFDCN-AD-01 at 2008-12-09 20:57:06.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDAD02 at 2009-01-20 10:49:30.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from MMAD01 at 2009-01-20 10:46:14.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZSAD01 at 2009-01-20 10:48:32.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GZAD01 at 2009-01-20 10:48:46.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from AD-02 at 2009-01-20 10:49:22.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZQAD01 at 2009-01-20 10:43:23.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from CZAD01 at 2009-01-20 10:40:44.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HYDCN-AD-02 at 2008-11-26 17:44:09.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-01 at 2009-03-05 03:50:10.
                   Last replication recieved from WBJAD01 at 2009-01-20 10:48:43.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from YJAD01 at 2009-01-20 10:42:01.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMAD01 at 2009-01-20 10:48:46.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMDCN-AD-01 at 2009-04-16 14:50:30.
                   Last replication recieved from YFAD01 at 2009-01-20 10:41:32.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SJJAD01 at 2009-01-20 10:48:32.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-02 at 2009-03-05 03:49:02.
                   Last replication recieved from HYDCN-AD-01 at 2008-11-26 17:52:09.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from AD-03 at 2009-01-20 10:49:19.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HYAD01 at 2009-01-20 10:46:14.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDAD01 at 2009-01-20 10:49:09.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SWAD01 at 2009-01-20 10:38:11.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Latency information for 34 entries in the vector were ignored.
                      33 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  1 had no latency information (Win2K DC). 
                DC=ctc,DC=com
                   Last replication recieved from AD-02 at 2009-01-07 09:00:35.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from AD-03 at 2009-01-07 08:55:21.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Latency information for 27 entries in the vector were ignored.
                      4 were retired Invocations.  23 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC). 
                DC=gd,DC=ctc,DC=com
                   Last replication recieved from FSAD01 at 2009-01-07 08:59:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from DGAD01 at 2009-01-07 08:59:33.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from MZAD01 at 2009-01-07 08:59:23.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-03 at 2009-03-05 04:03:04.
                   Last replication recieved from QYAD01 at 2009-01-07 08:59:51.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-04 at 2009-03-04 20:32:01.
                   Last replication recieved from SZAD01 at 2009-01-07 09:00:10.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZJAD01 at 2009-01-07 08:59:29.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SGAD01 at 2009-01-07 08:59:45.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from CXJAD01 at 2009-01-07 08:59:37.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HZAD01 at 2009-01-07 08:59:19.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from STAD01 at 2009-01-07 08:59:33.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZHAD01 at 2009-01-07 09:00:05.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JYAD01 at 2009-01-07 08:59:17.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from YJYAD01 at 2009-01-07 08:59:36.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDAD02 at 2009-01-07 09:00:25.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from MMAD01 at 2009-01-07 08:59:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZSAD01 at 2009-01-07 08:59:48.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GZAD01 at 2009-01-07 08:59:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZQAD01 at 2009-01-07 08:59:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from CZAD01 at 2009-01-07 08:59:45.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-01 at 2009-03-05 04:01:57.
                   Last replication recieved from WBJAD01 at 2009-01-07 08:59:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from YJAD01 at 2009-01-07 08:59:42.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMAD01 at 2009-01-07 09:00:20.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from YFAD01 at 2009-01-07 08:59:42.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SJJAD01 at 2009-01-07 08:59:42.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-02 at 2009-03-05 03:58:04.
                   Last replication recieved from HYAD01 at 2009-01-07 08:59:42.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDAD01 at 2009-01-07 09:00:15.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SWAD01 at 2009-01-07 08:59:21.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Latency information for 33 entries in the vector were ignored.
                      12 were retired Invocations.  21 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC). 
                DC=hq,DC=ctc,DC=com
                   Last replication recieved from HQAD01 at 2008-11-06 17:35:14.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Latency information for 44 entries in the vector were ignored.
                      2 were retired Invocations.  41 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  1 had no latency information (Win2K DC). 
                DC=dcn,DC=gd,DC=ctc,DC=com
                   Last replication recieved from SZDCN-AD-01 at 2008-02-23 02:49:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SZDCN-AD-02 at 2008-02-23 02:46:06.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMDCN-AD-02 at 2009-04-16 14:53:16.
                   Last replication recieved from YFDCN-AD-01 at 2008-12-09 20:51:42.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HYDCN-AD-02 at 2008-11-26 17:51:56.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMDCN-AD-01 at 2009-04-16 14:51:38.
                   Last replication recieved from HYDCN-AD-01 at 2008-11-26 17:52:14.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Latency information for 5 entries in the vector were ignored.
                      5 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC). 
             * Replication Site Latency Check
             REPLICATION-RECEIVED LATENCY WARNING

              Source site:

             CN=NTDS Site Settings,CN=GD-HYDCN,CN=Sites,CN=Configuration,DC=ctc,DC=com

              Current time: 2009-04-22 17:19:14

              Last update time: 2008-11-26 17:43:39

              Check if source site has an elected ISTG running.

              Check replication from source site to this server.
             REPLICATION-RECEIVED LATENCY WARNING

              Source site:

             CN=NTDS Site Settings,CN=GD-SZDCN,CN=Sites,CN=Configuration,DC=ctc,DC=com

              Current time: 2009-04-22 17:19:14

              Last update time: 2008-02-23 02:22:55

              Check if source site has an elected ISTG running.

              Check replication from source site to this server.
             REPLICATION-RECEIVED LATENCY WARNING

              Source site:

             CN=NTDS Site Settings,CN=GD-JMDCN,CN=Sites,CN=Configuration,DC=ctc,DC=com

              Current time: 2009-04-22 17:19:14

              Last update time: 2009-04-16 14:35:51

              Check if source site has an elected ISTG running.

              Check replication from source site to this server.
             REPLICATION-RECEIVED LATENCY WARNING

              Source site:

             CN=NTDS Site Settings,CN=gdsite,CN=Sites,CN=Configuration,DC=ctc,DC=com

              Current time: 2009-04-22 17:19:14

              Last update time: 2009-01-20 10:34:18

              Check if source site has an elected ISTG running.

              Check replication from source site to this server.
             REPLICATION-RECEIVED LATENCY WARNING

              Source site:

             CN=NTDS Site Settings,CN=hqsite,CN=Sites,CN=Configuration,DC=ctc,DC=com

              Current time: 2009-04-22 17:19:14

              Last update time: 2009-01-20 10:41:37

              Check if source site has an elected ISTG running.

              Check replication from source site to this server.
             REPLICATION-RECEIVED LATENCY WARNING

              Source site:

             CN=NTDS Site Settings,CN=GD-OADCN,CN=Sites,CN=Configuration,DC=ctc,DC=com

              Current time: 2009-04-22 17:19:14

              Last update time: 2009-03-05 03:48:44

              Check if source site has an elected ISTG running.

              Check replication from source site to this server.
             ......................... CZDCN-AD-01 passed test Replications
          Test omitted by user request: Topology
          Test omitted by user request: CutoffServers
          Starting test: NCSecDesc
             * Security Permissions Check for
               DC=dcn,DC=gd,DC=ctc,DC=com
                (Domain,Version 2)
             * Security Permissions Check for
               CN=Schema,CN=Configuration,DC=ctc,DC=com
                (Schema,Version 2)
             * Security Permissions Check for
               CN=Configuration,DC=ctc,DC=com
                (Configuration,Version 2)
             * Security Permissions Check for
               DC=hq,DC=ctc,DC=com
                (Domain,Version 1)
             * Security Permissions Check for
               DC=gd,DC=ctc,DC=com
                (Domain,Version 2)
             * Security Permissions Check for
               DC=ctc,DC=com
                (Domain,Version 2)
             ......................... CZDCN-AD-01 passed test NCSecDesc
          Starting test: NetLogons
             * Network Logons Privileges Check
             [CZDCN-AD-01] An net use or LsaPolicy operation failed with error 1203, 无任何网络提供程序接受指定的网络路径。.
             ......................... CZDCN-AD-01 failed test NetLogons
          Starting test: Advertising
             The DC CZDCN-AD-01 is advertising itself as a DC and having a DS.
             The DC CZDCN-AD-01 is advertising as an LDAP server
             The DC CZDCN-AD-01 is advertising as having a writeable directory
             The DC CZDCN-AD-01 is advertising as a Key Distribution Center
             The DC CZDCN-AD-01 is advertising as a time server
             The DS CZDCN-AD-01 is advertising as a GC.
             ......................... CZDCN-AD-01 passed test Advertising
          Starting test: KnowsOfRoleHolders
             Role Schema Owner = CN=NTDS Settings,CN=AD-02,CN=Servers,CN=gdsite,CN=Sites,CN=Configuration,DC=ctc,DC=com
             [AD-02] DsBindWithSpnEx() failed with error 1722,
             RPC 服务器不可用。.
             Printing RPC Extended Error Info:
             Error Record 1, ProcessID is 5984 (DcDiag)        
                System Time is: 4/22/2009 9:19:35:535
                Generating component is 8 (winsock)
                Status is 1722: RPC 服务器不可用。

                Detection location is 323
             Error Record 2, ProcessID is 5984 (DcDiag)        
                System Time is: 4/22/2009 9:19:35:535
                Generating component is 8 (winsock)
                Status is 1237: 操作无法完成。应该重试。

                Detection location is 313
             Error Record 3, ProcessID is 5984 (DcDiag)        
                System Time is: 4/22/2009 9:19:35:535
                Generating component is 8 (winsock)
                Status is 10065: 套接字操作尝试一个无法连接的主机。

                Detection location is 311
                NumberOfParameters is 3
                Long val: 135
                Pointer val: 0
                Pointer val: 0
             Error Record 4, ProcessID is 5984 (DcDiag)        
                System Time is: 4/22/2009 9:19:35:535
                Generating component is 8 (winsock)
                Status is 10065: 套接字操作尝试一个无法连接的主机。

                Detection location is 318
             Warning: AD-02 is the Schema Owner, but is not responding to DS RPC Bind.
             Printing RPC Extended Error Info:
             Error Record 1, ProcessID is 5984 (DcDiag)        
                System Time is: 4/22/2009 9:19:35:535
                Generating component is 8 (winsock)
                Status is 1722: RPC 服务器不可用。

                Detection location is 323
             Error Record 2, ProcessID is 5984 (DcDiag)        
                System Time is: 4/22/2009 9:19:35:535
                Generating component is 8 (winsock)
                Status is 1237: 操作无法完成。应该重试。

                Detection location is 313
             Error Record 3, ProcessID is 5984 (DcDiag)        
                System Time is: 4/22/2009 9:19:35:535
                Generating component is 8 (winsock)
                Status is 10065: 套接字操作尝试一个无法连接的主机。

                Detection location is 311
                NumberOfParameters is 3
                Long val: 135
                Pointer val: 0
                Pointer val: 0
             Error Record 4, ProcessID is 5984 (DcDiag)        
                System Time is: 4/22/2009 9:19:35:535
                Generating component is 8 (winsock)
                Status is 10065: 套接字操作尝试一个无法连接的主机。

                Detection location is 318
             [AD-02] LDAP search failed with error 58,
             指定的服务器无法运行请求的操作。.
             Warning: AD-02 is the Schema Owner, but is not responding to LDAP Bind.
             Role Domain Owner = CN=NTDS Settings,CN=AD-02,CN=Servers,CN=gdsite,CN=Sites,CN=Configuration,DC=ctc,DC=com
             Warning: AD-02 is the Domain Owner, but is not responding to DS RPC Bind.
             RPC Extended Error Info not available. Use group policy on the local machine at "Computer Configuration/Administrative Templates/System/Remote Procedure Call" to enable it.
             Warning: AD-02 is the Domain Owner, but is not responding to LDAP Bind.
             Role PDC Owner = CN=NTDS Settings,CN=GDDCN-AD-01,CN=Servers,CN=gddcnsite,CN=Sites,CN=Configuration,DC=ctc,DC=com
             Role Rid Owner = CN=NTDS Settings,CN=GDDCN-AD-01,CN=Servers,CN=gddcnsite,CN=Sites,CN=Configuration,DC=ctc,DC=com
             Role Infrastructure Update Owner = CN=NTDS Settings,CN=GDDCN-AD-01,CN=Servers,CN=gddcnsite,CN=Sites,CN=Configuration,DC=ctc,DC=com
             ......................... CZDCN-AD-01 failed test KnowsOfRoleHolders
          Starting test: RidManager
             * Available RID Pool for the Domain is 41103 to 1073741823
             * gddcn-ad-01.dcn.gd.ctc.com is the RID Master
             * DsBind with RID Master was successful
             * rIDAllocationPool is 16603 to 17102
             * rIDPreviousAllocationPool is 16603 to 17102
             * rIDNextRID: 16790
             ......................... CZDCN-AD-01 passed test RidManager
          Starting test: MachineAccount
             Could not open pipe with [CZDCN-AD-01]:failed with 1203: 无任何网络提供程序接受指定的网络路径。
             Could not get NetBIOSDomainName
             Failed can not test for HOST SPN
             Failed can not test for HOST SPN
             * SPN found :LDAP/czdcn-ad-01.dcn.gd.ctc.com/dcn.gd.ctc.com
             * SPN found :LDAP/czdcn-ad-01.dcn.gd.ctc.com
             * SPN found :LDAP/CZDCN-AD-01
             * Missing SPN :(null)
             * SPN found :LDAP/500923a3-584f-4ecf-97d2-09165a7e739b._msdcs.ctc.com
             * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/500923a3-584f-4ecf-97d2-09165a7e739b/dcn.gd.ctc.com
             * SPN found :HOST/czdcn-ad-01.dcn.gd.ctc.com/dcn.gd.ctc.com
             * SPN found :HOST/czdcn-ad-01.dcn.gd.ctc.com
             * SPN found :HOST/CZDCN-AD-01
             * Missing SPN :(null)
             * SPN found :GC/czdcn-ad-01.dcn.gd.ctc.com/ctc.com
             ......................... CZDCN-AD-01 failed test MachineAccount
          Starting test: Services
             Could not open Remote ipc to [CZDCN-AD-01]:failed with 1203: 无任何网络提供程序接受指定的网络路径。
             ......................... CZDCN-AD-01 failed test Services
          Test omitted by user request: OutboundSecureChannels
          Starting test: ObjectsReplicated
             CZDCN-AD-01 is in domain DC=dcn,DC=gd,DC=ctc,DC=com
             Checking for CN=CZDCN-AD-01,OU=Domain Controllers,DC=dcn,DC=gd,DC=ctc,DC=com in domain DC=dcn,DC=gd,DC=ctc,DC=com on 1 servers
                Object is up-to-date on all servers.
             Checking for CN=NTDS Settings,CN=CZDCN-AD-01,CN=Servers,CN=GD-CZDCN,CN=Sites,CN=Configuration,DC=ctc,DC=com in domain CN=Configuration,DC=ctc,DC=com on 1 servers
                Object is up-to-date on all servers.
             ......................... CZDCN-AD-01 passed test ObjectsReplicated
          Starting test: frssysvol
             * The File Replication Service SYSVOL ready test
             [CZDCN-AD-01] An net use or LsaPolicy operation failed with error 1203, 无任何网络提供程序接受指定的网络路径。.
             The registry lookup failed to determine the state of the SYSVOL.  The

             error returned  was 1203 (无任何网络提供程序接受指定的网络路径。).  Check the FRS event

             log to see if the SYSVOL has successfully been shared.
             ......................... CZDCN-AD-01 failed test frssysvol
          Starting test: frsevent
             * The File Replication Service Event log test
             ......................... CZDCN-AD-01 failed test frsevent
          Starting test: kccevent
             * The KCC Event log test
             Failed to enumerate event log records, error 无任何网络提供程序接受指定的网络路径。
             ......................... CZDCN-AD-01 failed test kccevent
          Starting test: systemlog
             * The System Event log test
             Failed to enumerate event log records, error 无任何网络提供程序接受指定的网络路径。
             ......................... CZDCN-AD-01 failed test systemlog
          Test omitted by user request: VerifyReplicas
          Starting test: VerifyReferences
             The system object reference (serverReference)

             CN=CZDCN-AD-01,OU=Domain Controllers,DC=dcn,DC=gd,DC=ctc,DC=com and

             backlink on

             CN=CZDCN-AD-01,CN=Servers,CN=GD-CZDCN,CN=Sites,CN=Configuration,DC=ctc,DC=com

             are correct.
             The system object reference (frsComputerReferenceBL)

             CN=CZDCN-AD-01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=dcn,DC=gd,DC=ctc,DC=com

             and backlink on

             CN=CZDCN-AD-01,OU=Domain Controllers,DC=dcn,DC=gd,DC=ctc,DC=com are

             correct.
             The system object reference (serverReferenceBL)

             CN=CZDCN-AD-01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=dcn,DC=gd,DC=ctc,DC=com

             and backlink on

             CN=NTDS Settings,CN=CZDCN-AD-01,CN=Servers,CN=GD-CZDCN,CN=Sites,CN=Configuration,DC=ctc,DC=com

             are correct.
             ......................... CZDCN-AD-01 passed test VerifyReferences
          Test omitted by user request: VerifyEnterpriseReferences
      
       Running partition tests on : dcn
          Starting test: CrossRefValidation
             ......................... dcn passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... dcn passed test CheckSDRefDom
      
       Running partition tests on : Schema
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
      
       Running partition tests on : Configuration
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
      
       Running enterprise tests on : ctc.com
          Starting test: Intersite
             Skipping site GD-FSDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-SGDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-ZQDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-YFDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-MMDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-ZJDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-DGDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-STDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-CZDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-MZDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-HYDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site gddcnsite, this site is outside the scope provided by

             the command line arguments provided.
             Skipping site GD-HZDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-JYDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-ZSDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-GZDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-QYDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-SWDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-SZDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-JMDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-ZHDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-YJDCN, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site gdsite, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site hqsite, this site is outside the scope provided by the

             command line arguments provided.
             Skipping site GD-OADCN, this site is outside the scope provided by the

             command line arguments provided.
             ......................... ctc.com passed test Intersite
          Starting test: FsmoCheck
             GC Name: \\czdcn-ad-01.dcn.gd.ctc.com
             Locator Flags: 0xe00001fc
             PDC Name: \\gddcn-ad-01.dcn.gd.ctc.com
             Locator Flags: 0xe000017d
             Time Server Name: \\czdcn-ad-01.dcn.gd.ctc.com
             Locator Flags: 0xe00001fc
             Preferred Time Server Name: \\czdcn-ad-01.dcn.gd.ctc.com
             Locator Flags: 0xe00001fc
             KDC Name: \\czdcn-ad-01.dcn.gd.ctc.com
             Locator Flags: 0xe00001fc
             ......................... ctc.com passed test FsmoCheck

    2009年4月22日 15:46
  • 您好:
     The registry lookup failed to determine the state of the SYSVOL

    日志已经记录SYSVOL异常!我建议您先修复修复Sysvol 文件夹的内容。一个或多个域控制器丢失了 Sysvol 共享,可能会产生此原因!

    如何在域中重新生成 SYSVOL 树及其内容。

    315457 (http://support.microsoft.com/kb/315457/)

    另外日志还记录了其它的错误!我建议您再问问其它人!

    by-陈陈!
    silence-陈陈 双手剑的时代来临!
    2009年4月23日 1:34
  • 根據您提供的log,我看了一下,樓主的日志中有一個最大的問題,兩臺DC的同步異常已經超過60天,應該說已經超過了DC間隔復制的最佳時間,根據我的想法,建議將其中的一臺進行強制降級,然后重新做DC冗余,這個做風險較小,可以快速的處理問題


    Up And Up
    2009年4月23日 2:06
  • 对, DC间的复制已经暂停了超过60天的 墓碑值,发生这种情况的可能性有:

    1. 你曾经offline一台DC超过60天。。
    2. 你使用60天之前的backup恢复了一台DC

    如果你在DC上查看事件日志,你可能会看到Event ID 2042,

    -----------------------------------------------------------------------------
    Event Type:Error
    Event Source:NTDS Replication
    Event Category:Replication
    Event ID:2042
    Date:3/22/2005
    Time:7:28:49 AM
    User:NT AUTHORITY\ANONYMOUS LOGON
    Computer:DC3
    Description:
    It has been too long since this machine last replicated with the
    named source machine. The time between replications with this source
    has exceeded the tombstone lifetime. Replication has been stopped
    with this source.
    The reason that replication is not allowed to continue is that
    the two machine's views of deleted objects may now be different.
    The source machine may still have copies of objects that have
    been deleted (and garbage collected) on this machine. If they
    were allowed to replicate, the source machine might return
    objects which have already been deleted.
    Time of last successful replication:
    2005-01-21 07:16:03
    Invocation ID of source:
    0397f6c8-f6b8-0397-0100-000000000000
    Name of source:
    4a8717eb-8e58-456c-995a-c92e4add7e8e._msdcs.contoso.com
    Tombstone lifetime (days):
    60
    -----------------------------------------------------------------------------

    为了重新的激活复制,你可以参考:

    Event ID 2042: It has been too long since this machine replicated
    http://technet2.microsoft.com/windowsserver/en/library/34c15446-b47f-4d51-8e4a-c14527060f901033.mspx
    2009年4月23日 9:51
  • 因为日志太多,在论坛上也肯定发不全,我想再确定的一个问题是,我的环境中,系统都是打过sp 2的正版的2003的标准版,日志信息中为什么会出现超过60天就不能复制了呢? 未打sp1补丁的默认是60天,打过sp1以上补丁的应该是180天,那日志信息中怎么提示的是60天,而不是180天呢?

    我的环境描述:
    父子域形式,父域中总共6台DC,其中2台在一个网段(10网段)中,另外4台在其他的一个网段(132网段)中,中间用路由器隔开,10网段的2台DC其中一台是为PDC,两台组成一个site,132网段的4台DC从10网段同步复制信息,并在这个4台中设置2台为GC(省中心), 这4台组成一个site,  子域中设置2台DC组成一个站点,这2台DC从132网段的那4台DC中同步信息,但不能直接从10网段的那2台DC去同步信息(路由器隔离了),在子域的2台DC下还有各个地方(省中的各地市),每个地市2台DC组成一个site,每个地市的2台DC去省中心的2台DC同步信息,

    根据以上楼主的建议,如果对132网段的那4台DC采用退域再加入域的方法(各地市的DC也有以上类似的日志报错信息,但是地市的机器众多,不敢考虑把地市的也采取退域再升级额外DC的方法),会不会对各地市的DC产生影响?----------这正是我考虑的风险所在, 忘各位朋友锦囊相助,以上信息可能描述比较晕,还忘版主体谅(这里画不了拓扑图)

    2009年4月23日 12:25
  • 我认为会影响!不过您说了半天,是132网段的4台DC存在复制问题吗?还是其它网段DC也存在问题!
    by-陈陈!
    silence-陈陈 双手剑的时代来临!
    2009年4月23日 13:34
  • 不好意思,饿没有说清楚我的环境(如果在论坛上能画拓扑就好了)。

    132网段的4台DC和地市的DC都存在问题,都有出现如上述日志提示的一些报错信息。

    针对我这种情况,究竟有什么样的根治方法,请教版主以及各位技术专家朋友们。

    2009年4月23日 13:40
  • 不知道你的Event id是否有2042? 2042的处理并没有谈论到降级的问题,是一个注册表的修改!您先参照解决下,如果方便的话,发下所有的event id.(发下主要的数字和Event Source)!

    by-陈陈!


    silence-陈陈 双手剑的时代来临!
    2009年4月23日 14:20
  • 谢谢
    请问您说的注册表的修改,是否指的是:

    [HKEY_Local_Machine\system\CurrentControlSet\Services\NTDS\Parameters]

    "Allow Replication With Divergent and Corrupt Partner"=dword:00000001

     当该值为1时,超过60天没复制的DC就会恢复正常。

    请问是指的这个位置的注册表的修改吗?

    我的这个环境中,总共44台DC,我已经保存了十几台的日志信息了,我是否能直接和版主以及一些微软技术朋友们直接发邮件?
    事件信息发在论坛上太多,能否发邮件到版主的邮箱说明我的问题呢?

    2009年4月23日 15:48
  • 是的。修改132网段的4台,因为下面dc是与132是同步的。
    以上方法只是个建议性的答复。具体还要看修改后的效果。
    另外When you are satisfied that lingering objects have been removed and replication has occurred successfully from the source domain controller, edit the registry to return the value in Allow Replication With Divergent and Corrupt Partner to 0.

    如果复制成功了,还要改回来!

    论坛上一般不留邮箱,除非有人帮你!并不是所有的case大家都能处理,我们只提供一些解决问题的方案!风险要自承担!

    by-陈陈!


    silence-陈陈 双手剑的时代来临!
    2009年4月25日 8:50
  • 谢谢
    环境描述补充: 最顶上为一个根域 ctc.com ,下面为子域gd.ctc.com-----10网段的2台DC和132网段的4台DC在这个域中,第二级子域为dcn.gd.ctc.com-----地市的所有DC属于这个域,

    按照lz的建议,我需要修改132网段的4台DC的注册表键值,那么,地市的那些DC是否也需要同样修改注册表的值?

    以下我摘要132网段中的一台设置为GC的dcdiag的部分信息:(站点命名规则----省公司: gddcnsite,  各地市: gd-xxDCN,示例:GDDCN-AD-01,表示省公司第01DCSZDCN-AD-02,表示深圳分公司第02DC

    Domain Controller Diagnosis
    Performing initial setup:
       * Verifying that the local machine gddcn-oa-04, is a DC.
       * Connecting to directory service on server gddcn-oa-04.
       * Collecting site info.
       * Identifying all servers.
       * Identifying all NC cross-refs.
       * Found 79 DC(s). Testing 1 of them.
       Done gathering initial info.

    Doing initial required tests
      
       Testing server: GD-OADCN\GDDCN-OA-04
          Starting test: Connectivity
             * Active Directory LDAP Services Check
             * Active Directory RPC Services Check
             ......................... GDDCN-OA-04 passed test Connectivity

    Doing primary tests
      
       Testing server: GD-OADCN\GDDCN-OA-04
          Starting test: Replications
             * Replications Check
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDDCN-OA-03 to GDDCN-OA-04
                Naming Context: DC=ForestDnsZones,DC=ctc,DC=com
                The replication generated an error (1256):
                远程系统不可用。有关网络疑难解答,请参阅 Windows 帮助。
                The failure occurred at 2009-04-24 10:50:44.
                The last success occurred at 2009-04-04 12:13:07.
                653 failures have occurred since the last success.
             [GDDCN-OA-03] DsBindWithSpnEx() failed with error -2146893022,
             目标主要名称不正确。.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDDCN-OA-02 to GDDCN-OA-04
                Naming Context: DC=ForestDnsZones,DC=ctc,DC=com
                The replication generated an error (1256):
                远程系统不可用。有关网络疑难解答,请参阅 Windows 帮助。
                The failure occurred at 2009-04-24 10:51:05.
                The last success occurred at 2009-04-04 03:58:12.
                625 failures have occurred since the last success.
             [GDDCN-OA-02] DsBindWithSpnEx() failed with error -2146893022,
             目标主要名称不正确。.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDAD01 to GDDCN-OA-04
                Naming Context: DC=ForestDnsZones,DC=ctc,DC=com
                The replication generated an error (1256):
                远程系统不可用。有关网络疑难解答,请参阅 Windows 帮助。
                The failure occurred at 2009-04-24 11:22:15.
                The last success occurred at (never).
                9035 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDAD02 to GDDCN-OA-04
                Naming Context: DC=ForestDnsZones,DC=ctc,DC=com
                The replication generated an error (8614):
                Active Directory 不能与此服务器复制,因为距上一次与此服务器复制的时间已经超过了 tombstone 生存时间。
                The failure occurred at 2009-04-24 11:23:17.
                The last success occurred at 2009-01-07 09:00:34.
                10297 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDDCN-OA-03 to GDDCN-OA-04
                Naming Context: CN=Schema,CN=Configuration,DC=ctc,DC=com
                The replication generated an error (-2146893022):
                目标主要名称不正确。
                The failure occurred at 2009-04-24 10:51:47.
                The last success occurred at 2009-04-04 12:27:32.
                516 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDDCN-OA-02 to GDDCN-OA-04
                Naming Context: CN=Schema,CN=Configuration,DC=ctc,DC=com
                The replication generated an error (-2146893022):
                目标主要名称不正确。
                The failure occurred at 2009-04-24 10:52:08.
                The last success occurred at 2009-04-04 03:56:51.
                525 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDAD01 to GDDCN-OA-04
                Naming Context: CN=Schema,CN=Configuration,DC=ctc,DC=com
                The replication generated an error (-2146893022):
                目标主要名称不正确。
                The failure occurred at 2009-04-24 11:22:15.
                The last success occurred at (never).
                9041 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDDCN-OA-03 to GDDCN-OA-04
                Naming Context: CN=Configuration,DC=ctc,DC=com
                The replication generated an error (-2146893022):
                目标主要名称不正确。
                The failure occurred at 2009-04-24 11:22:14.
                The last success occurred at 2009-04-04 12:52:24.
                2193 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDAD01 to GDDCN-OA-04
                Naming Context: CN=Configuration,DC=ctc,DC=com
                The replication generated an error (-2146893022):
                目标主要名称不正确。
                The failure occurred at 2009-04-24 11:22:15.
                The last success occurred at (never).
                9043 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDDCN-OA-02 to GDDCN-OA-04
                Naming Context: CN=Configuration,DC=ctc,DC=com
                The replication generated an error (-2146893022):
                目标主要名称不正确。
                The failure occurred at 2009-04-24 11:24:02.
                The last success occurred at 2009-04-04 04:36:50.
                2129 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDDCN-OA-02 to GDDCN-OA-04
                Naming Context: DC=ctc,DC=com
                The replication generated an error (1256):
                远程系统不可用。有关网络疑难解答,请参阅 Windows 帮助。
                The failure occurred at 2009-04-24 10:51:05.
                The last success occurred at 2009-04-04 03:56:51.
                489 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDAD01 to GDDCN-OA-04
                Naming Context: DC=ctc,DC=com
                The replication generated an error (1256):
                远程系统不可用。有关网络疑难解答,请参阅 Windows 帮助。
                The failure occurred at 2009-04-24 11:22:15.
                The last success occurred at (never).
                9033 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDDCN-OA-03 to GDDCN-OA-04
                Naming Context: DC=DomainDnsZones,DC=gd,DC=ctc,DC=com
                The replication generated an error (1256):
                远程系统不可用。有关网络疑难解答,请参阅 Windows 帮助。
                The failure occurred at 2009-04-24 10:50:44.
                The last success occurred at 2009-04-04 11:56:51.
                555 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDDCN-OA-02 to GDDCN-OA-04
                Naming Context: DC=DomainDnsZones,DC=gd,DC=ctc,DC=com
                The replication generated an error (1256):
                远程系统不可用。有关网络疑难解答,请参阅 Windows 帮助。
                The failure occurred at 2009-04-24 10:51:05.
                The last success occurred at 2009-04-04 03:56:51.
                564 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDAD01 to GDDCN-OA-04
                Naming Context: DC=DomainDnsZones,DC=gd,DC=ctc,DC=com
                The replication generated an error (1256):
                远程系统不可用。有关网络疑难解答,请参阅 Windows 帮助。
                The failure occurred at 2009-04-24 11:22:15.
                The last success occurred at (never).
                9034 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDAD02 to GDDCN-OA-04
                Naming Context: DC=DomainDnsZones,DC=gd,DC=ctc,DC=com
                The replication generated an error (8614):
                Active Directory 不能与此服务器复制,因为距上一次与此服务器复制的时间已经超过了 tombstone 生存时间。
                The failure occurred at 2009-04-24 11:23:22.
                The last success occurred at 2009-01-07 09:00:35.
                10296 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDAD02 to GDDCN-OA-04
                Naming Context: DC=gd,DC=ctc,DC=com
                The replication generated an error (8614):
                Active Directory 不能与此服务器复制,因为距上一次与此服务器复制的时间已经超过了 tombstone 生存时间。
                The failure occurred at 2009-04-24 11:23:16.
                The last success occurred at 2009-01-07 09:00:34.
                10297 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDAD01 to GDDCN-OA-04
                Naming Context: DC=gd,DC=ctc,DC=com
                The replication generated an error (-2146893022):
                目标主要名称不正确。
                The failure occurred at 2009-04-24 11:23:22.
                The last success occurred at (never).
                9036 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDDCN-OA-02 to GDDCN-OA-04
                Naming Context: DC=gd,DC=ctc,DC=com
                The replication generated an error (-2146893022):
                目标主要名称不正确。
                The failure occurred at 2009-04-24 11:32:27.
                The last success occurred at 2009-04-04 04:28:25.
                9748 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDDCN-OA-03 to GDDCN-OA-04
                Naming Context: DC=gd,DC=ctc,DC=com
                The replication generated an error (-2146893022):
                目标主要名称不正确。
                The failure occurred at 2009-04-24 11:32:57.
                The last success occurred at 2009-04-04 12:48:15.
                9869 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDDCN-OA-02 to GDDCN-OA-04
                Naming Context: DC=hq,DC=ctc,DC=com
                The replication generated an error (1256):
                远程系统不可用。有关网络疑难解答,请参阅 Windows 帮助。
                The failure occurred at 2009-04-24 10:51:05.
                The last success occurred at 2009-04-04 01:56:52.
                489 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDAD01 to GDDCN-OA-04
                Naming Context: DC=hq,DC=ctc,DC=com
                The replication generated an error (1256):
                远程系统不可用。有关网络疑难解答,请参阅 Windows 帮助。
                The failure occurred at 2009-04-24 11:22:15.
                The last success occurred at (never).
                9032 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDDCN-AD-02 to GDDCN-OA-04
                Naming Context: DC=hq,DC=ctc,DC=com
                The replication generated an error (8464):
                同步尝试失败,因为目标 DC 当前正在等待从源同步新的部分属性。如果最近架构更改修改了部分属性集,此状态正常。目标部分属性集不是源部分属性集的子集。
                The failure occurred at 2009-04-24 11:23:22.
                The last success occurred at 2009-04-04 03:43:31.
                1 failures have occurred since the last success.
                Try synchronizing the Schema partition on all servers in the forest.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDDCN-OA-02 to GDDCN-OA-04
                Naming Context: DC=dcn,DC=gd,DC=ctc,DC=com
                The replication generated an error (1256):
                远程系统不可用。有关网络疑难解答,请参阅 Windows 帮助。
                The failure occurred at 2009-04-24 10:51:05.
                The last success occurred at 2009-04-04 03:56:51.
                697 failures have occurred since the last success.
             [Replications Check,GDDCN-OA-04] A recent replication attempt failed:
                From GDAD01 to GDDCN-OA-04
                Naming Context: DC=dcn,DC=gd,DC=ctc,DC=com
                The replication generated an error (1256):
                远程系统不可用。有关网络疑难解答,请参阅 Windows 帮助。
                The failure occurred at 2009-04-24 11:22:15.
                The last success occurred at (never).
                9032 failures have occurred since the last success.
             * Replication Latency Check
             REPLICATION-RECEIVED LATENCY WARNING
             GDDCN-OA-04:  Current time is 2009-04-24 11:33:05.
                DC=ForestDnsZones,DC=ctc,DC=com
                   Last replication recieved from FSAD01 at 2009-01-07 07:47:05.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from DGAD01 at 2009-01-07 08:46:04.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from MZAD01 at 2009-01-07 08:52:29.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-03 at 2009-04-04 12:13:40.
                   Last replication recieved from QYAD01 at 2009-01-07 07:52:41.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SZAD01 at 2009-01-07 08:48:40.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZJAD01 at 2009-01-07 08:53:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SGAD01 at 2009-01-07 08:55:21.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from CXJAD01 at 2009-01-07 08:53:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HZAD01 at 2009-01-07 08:45:32.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from STAD01 at 2009-01-07 08:50:31.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZHAD01 at 2009-01-07 08:55:21.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JYAD01 at 2009-01-07 07:57:44.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from YJYAD01 at 2009-01-07 08:50:31.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDAD02 at 2009-01-07 09:00:34.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from MMAD01 at 2009-01-07 08:55:21.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZSAD01 at 2009-01-07 08:48:40.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GZAD01 at 2009-01-07 08:55:21.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from AD-02 at 2009-01-07 09:00:34.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZQAD01 at 2009-01-07 07:59:19.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from CZAD01 at 2009-01-07 06:52:44.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from WBJAD01 at 2009-01-07 08:53:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from YJAD01 at 2009-01-07 07:56:11.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMAD01 at 2009-01-07 08:52:08.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from YFAD01 at 2009-01-07 08:52:29.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SJJAD01 at 2009-01-07 07:59:19.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-02 at 2009-04-04 03:58:28.
                   Last replication recieved from AD-03 at 2009-01-07 08:55:21.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HYAD01 at 2009-01-07 06:52:06.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDAD01 at 2009-01-07 08:52:29.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SWAD01 at 2009-01-07 08:46:04.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Latency information for 18 entries in the vector were ignored.
                      18 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC). 
                CN=Schema,CN=Configuration,DC=ctc,DC=com
                   Last replication recieved from SZDCN-AD-01 at 2008-02-23 02:49:35.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-03 at 2009-04-04 12:28:05.
                   Last replication recieved from SZDCN-AD-02 at 2008-02-23 01:53:09.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMDCN-AD-02 at 2009-04-23 17:50:32.
                   Last replication recieved from YFDCN-AD-01 at 2008-12-09 20:51:19.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HYDCN-AD-02 at 2008-11-26 16:58:35.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMDCN-AD-01 at 2009-04-23 17:53:31.
                   Last replication recieved from HYDCN-AD-01 at 2008-11-26 17:52:12.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Latency information for 58 entries in the vector were ignored.
                      33 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  25 had no latency information (Win2K DC). 
                CN=Configuration,DC=ctc,DC=com
                   Last replication recieved from SZDCN-AD-01 at 2008-02-23 02:49:33.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-03 at 2009-04-04 12:52:56.
                   Last replication recieved from SZDCN-AD-02 at 2008-02-23 02:22:18.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMDCN-AD-02 at 2009-04-23 17:51:02.
                   Last replication recieved from YFDCN-AD-01 at 2008-12-09 20:57:06.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HYDCN-AD-02 at 2008-11-26 17:44:09.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMDCN-AD-01 at 2009-04-23 17:52:46.
                   Last replication recieved from HYDCN-AD-01 at 2008-11-26 17:52:09.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Latency information for 34 entries in the vector were ignored.
                      33 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  1 had no latency information (Win2K DC). 
                DC=ctc,DC=com
                   Last replication recieved from AD-02 at 2009-01-07 09:00:35.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from AD-03 at 2009-01-07 08:55:21.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Latency information for 27 entries in the vector were ignored.
                      4 were retired Invocations.  23 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC). 
                DC=DomainDnsZones,DC=gd,DC=ctc,DC=com
                   Last replication recieved from FSAD01 at 2009-01-07 08:59:51.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from DGAD01 at 2009-01-07 08:59:24.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from MZAD01 at 2009-01-07 08:59:59.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-03 at 2009-04-04 11:57:24.
                   Last replication recieved from QYAD01 at 2009-01-07 09:00:06.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SZAD01 at 2009-01-07 09:00:21.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZJAD01 at 2009-01-07 09:00:08.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SGAD01 at 2009-01-07 09:00:12.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from CXJAD01 at 2009-01-07 09:00:04.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HZAD01 at 2009-01-07 08:59:10.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from STAD01 at 2009-01-07 08:59:12.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZHAD01 at 2009-01-07 08:59:26.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JYAD01 at 2009-01-07 08:59:07.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from YJYAD01 at 2009-01-07 08:58:44.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDAD02 at 2009-01-07 09:00:34.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from MMAD01 at 2009-01-07 08:59:27.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZSAD01 at 2009-01-07 09:00:06.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GZAD01 at 2009-01-07 08:59:19.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZQAD01 at 2009-01-07 08:59:48.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from CZAD01 at 2009-01-07 08:59:57.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from WBJAD01 at 2009-01-07 09:00:15.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from YJAD01 at 2009-01-07 08:59:36.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMAD01 at 2009-01-07 09:00:33.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from YFAD01 at 2009-01-07 08:59:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SJJAD01 at 2009-01-07 08:59:24.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-02 at 2009-04-04 03:57:56.
                   Last replication recieved from HYAD01 at 2009-01-07 08:59:51.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDAD01 at 2009-01-07 09:00:27.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SWAD01 at 2009-01-07 08:59:11.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Latency information for 11 entries in the vector were ignored.
                      11 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC). 
                DC=gd,DC=ctc,DC=com
                   Last replication recieved from FSAD01 at 2009-01-07 08:59:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from DGAD01 at 2009-01-07 08:59:33.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from MZAD01 at 2009-01-07 08:59:23.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-03 at 2009-04-04 12:48:47.
                   Last replication recieved from QYAD01 at 2009-01-07 08:59:51.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SZAD01 at 2009-01-07 09:00:10.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZJAD01 at 2009-01-07 08:59:29.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SGAD01 at 2009-01-07 08:59:45.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from CXJAD01 at 2009-01-07 08:59:37.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HZAD01 at 2009-01-07 08:59:19.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from STAD01 at 2009-01-07 08:59:33.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZHAD01 at 2009-01-07 09:00:05.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JYAD01 at 2009-01-07 08:59:17.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from YJYAD01 at 2009-01-07 08:59:36.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDAD02 at 2009-01-07 09:00:25.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from MMAD01 at 2009-01-07 08:59:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZSAD01 at 2009-01-07 08:59:48.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GZAD01 at 2009-01-07 08:59:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from ZQAD01 at 2009-01-07 08:59:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from CZAD01 at 2009-01-07 08:59:45.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from WBJAD01 at 2009-01-07 08:59:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from YJAD01 at 2009-01-07 08:59:42.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMAD01 at 2009-01-07 09:00:20.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from YFAD01 at 2009-01-07 08:59:42.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SJJAD01 at 2009-01-07 08:59:42.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDDCN-OA-02 at 2009-04-04 04:28:44.
                   Last replication recieved from HYAD01 at 2009-01-07 08:59:42.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from GDAD01 at 2009-01-07 09:00:15.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SWAD01 at 2009-01-07 08:59:21.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Latency information for 12 entries in the vector were ignored.
                      12 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC). 
                DC=hq,DC=ctc,DC=com
                   Last replication recieved from HQAD01 at 2008-11-06 17:35:14.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Latency information for 44 entries in the vector were ignored.
                      2 were retired Invocations.  41 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  1 had no latency information (Win2K DC). 
                DC=dcn,DC=gd,DC=ctc,DC=com
                   Last replication recieved from SZDCN-AD-01 at 2008-02-23 02:49:39.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from SZDCN-AD-02 at 2008-02-23 02:46:06.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMDCN-AD-02 at 2009-04-23 17:51:06.
                   Last replication recieved from YFDCN-AD-01 at 2008-12-09 20:51:42.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from HYDCN-AD-02 at 2008-11-26 17:51:56.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Last replication recieved from JMDCN-AD-01 at 2009-04-23 17:54:07.
                   Last replication recieved from HYDCN-AD-01 at 2008-11-26 17:52:14.
                   WARNING:  This latency is over the Tombstone Lifetime of 60 days!
                   Latency information for 6 entries in the vector were ignored.
                      5 were retired Invocations.  1 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC). 
             * Replication Site Latency Check
             REPLICATION-RECEIVED LATENCY WARNING
             Source site:
             CN=NTDS Site Settings,CN=GD-SZDCN,CN=Sites,CN=Configuration,DC=ctc,DC=com
             Current time: 2009-04-24 11:33:05
             Last update time: 2008-02-23 02:22:55
             Check if source site has an elected ISTG running.
             Check replication from source site to this server.
             REPLICATION-RECEIVED LATENCY WARNING
             Source site:
             CN=NTDS Site Settings,CN=GD-HYDCN,CN=Sites,CN=Configuration,DC=ctc,DC=com
             Current time: 2009-04-24 11:33:05
             Last update time: 2008-11-26 17:43:39
             Check if source site has an elected ISTG running.
             Check replication from source site to this server.
             ......................... GDDCN-OA-04 passed test Replications
          Test omitted by user request: Topology
          Test omitted by user request: CutoffServers
          Starting test: NCSecDesc
             * Security Permissions Check for
               DC=DomainDnsZones,DC=gd,DC=ctc,DC=com
                (NDNC,Version 2)
             * Security Permissions Check for
               DC=ForestDnsZones,DC=ctc,DC=com
                (NDNC,Version 2)
             * Security Permissions Check for
               DC=gd,DC=ctc,DC=com
                (Domain,Version 2)
             * Security Permissions Check for
               CN=Schema,CN=Configuration,DC=ctc,DC=com
                (Schema,Version 2)
             * Security Permissions Check for
               CN=Configuration,DC=ctc,DC=com
                (Configuration,Version 2)
             * Security Permissions Check for
               DC=dcn,DC=gd,DC=ctc,DC=com
                (Domain,Version 2)
             * Security Permissions Check for
               DC=hq,DC=ctc,DC=com
                (Domain,Version 1)
             * Security Permissions Check for
               DC=ctc,DC=com
                (Domain,Version 2)
             ......................... GDDCN-OA-04 passed test NCSecDesc
          Starting test: NetLogons
             * Network Logons Privileges Check
             ......................... GDDCN-OA-04 passed test NetLogons
          Starting test: Advertising
             The DC GDDCN-OA-04 is advertising itself as a DC and having a DS.
             The DC GDDCN-OA-04 is advertising as an LDAP server
             The DC GDDCN-OA-04 is advertising as having a writeable directory
             The DC GDDCN-OA-04 is advertising as a Key Distribution Center
             The DC GDDCN-OA-04 is advertising as a time server
             The DS GDDCN-OA-04 is advertising as a GC.
             ......................... GDDCN-OA-04 passed test Advertising
          Starting test: KnowsOfRoleHolders
             Role Schema Owner = CN=NTDS Settings,CN=AD-02,CN=Servers,CN=gdsite,CN=Sites,CN=Configuration,DC=ctc,DC=com
             [AD-02] DsBindWithSpnEx() failed with error 1722,
             RPC 服务器不可用。.
             Printing RPC Extended Error Info:
             Error Record 1, ProcessID is 1240 (DcDiag)        
                System Time is: 4/24/2009 3:33:26:453
                Generating component is 8 (winsock)
                Status is 1722: RPC 服务器不可用。

                Detection location is 323
             Error Record 2, ProcessID is 1240 (DcDiag)        
                System Time is: 4/24/2009 3:33:26:453
                Generating component is 8 (winsock)
                Status is 1237: 操作无法完成。应该重试。

                Detection location is 313
             Error Record 3, ProcessID is 1240 (DcDiag)        
                System Time is: 4/24/2009 3:33:26:453
                Generating component is 8 (winsock)
                Status is 10060: 由于连接方在一段时间后没有正确答复或连接的主机没有反应,连接尝试失败。

                Detection location is 311
                NumberOfParameters is 3
                Long val: 135
                Pointer val: 0
                Pointer val: 0
             Error Record 4, ProcessID is 1240 (DcDiag)        
                System Time is: 4/24/2009 3:33:26:453
                Generating component is 8 (winsock)
                Status is 10060: 由于连接方在一段时间后没有正确答复或连接的主机没有反应,连接尝试失败。

                Detection location is 318
             Warning: AD-02 is the Schema Owner, but is not responding to DS RPC Bind.
             Printing RPC Extended Error Info:
             Error Record 1, ProcessID is 1240 (DcDiag)        
                System Time is: 4/24/2009 3:33:26:453
                Generating component is 8 (winsock)
                Status is 1722: RPC 服务器不可用。

                Detection location is 323
             Error Record 2, ProcessID is 1240 (DcDiag)        
                System Time is: 4/24/2009 3:33:26:453
                Generating component is 8 (winsock)
                Status is 1237: 操作无法完成。应该重试。

                Detection location is 313
             Error Record 3, ProcessID is 1240 (DcDiag)        
                System Time is: 4/24/2009 3:33:26:453
                Generating component is 8 (winsock)
                Status is 10060: 由于连接方在一段时间后没有正确答复或连接的主机没有反应,连接尝试失败。

                Detection location is 311
                NumberOfParameters is 3
                Long val: 135
                Pointer val: 0
                Pointer val: 0
             Error Record 4, ProcessID is 1240 (DcDiag)        
                System Time is: 4/24/2009 3:33:26:453
                Generating component is 8 (winsock)
                Status is 10060: 由于连接方在一段时间后没有正确答复或连接的主机没有反应,连接尝试失败。

                Detection location is 318
             [AD-02] LDAP search failed with error 58,
             指定的服务器无法运行请求的操作。.
             Warning: AD-02 is the Schema Owner, but is not responding to LDAP Bind.
             Role Domain Owner = CN=NTDS Settings,CN=AD-02,CN=Servers,CN=gdsite,CN=Sites,CN=Configuration,DC=ctc,DC=com
             Warning: AD-02 is the Domain Owner, but is not responding to DS RPC Bind.
             RPC Extended Error Info not available. Use group policy on the local machine at "Computer Configuration/Administrative Templates/System/Remote Procedure Call" to enable it.
             Warning: AD-02 is the Domain Owner, but is not responding to LDAP Bind.
             Role PDC Owner = CN=NTDS Settings,CN=GDAD02,CN=Servers,CN=gdsite,CN=Sites,CN=Configuration,DC=ctc,DC=com
             Role Rid Owner = CN=NTDS Settings,CN=GDAD02,CN=Servers,CN=gdsite,CN=Sites,CN=Configuration,DC=ctc,DC=com
             Role Infrastructure Update Owner = CN=NTDS Settings,CN=GDAD02,CN=Servers,CN=gdsite,CN=Sites,CN=Configuration,DC=ctc,DC=com
             ......................... GDDCN-OA-04 failed test KnowsOfRoleHolders
          Starting test: RidManager
             * Available RID Pool for the Domain is 191103 to 1073741823
             * gdad02.gd.ctc.com is the RID Master
             * DsBind with RID Master was successful
             * rIDAllocationPool is 127603 to 128102
             * rIDPreviousAllocationPool is 127603 to 128102
             * rIDNextRID: 127692
             ......................... GDDCN-OA-04 passed test RidManager
          Starting test: MachineAccount
             * SPN found :LDAP/gddcn-oa-04.gd.ctc.com/gd.ctc.com
             * SPN found :LDAP/gddcn-oa-04.gd.ctc.com
             * SPN found :LDAP/GDDCN-OA-04
             * SPN found :LDAP/gddcn-oa-04.gd.ctc.com/GDCTC
             * SPN found :LDAP/d4b507f8-1536-428c-bafd-741af55467c7._msdcs.ctc.com
             * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/d4b507f8-1536-428c-bafd-741af55467c7/gd.ctc.com
             * SPN found :HOST/gddcn-oa-04.gd.ctc.com/gd.ctc.com
             * SPN found :HOST/gddcn-oa-04.gd.ctc.com
             * SPN found :HOST/GDDCN-OA-04
             * SPN found :HOST/gddcn-oa-04.gd.ctc.com/GDCTC
             * SPN found :GC/gddcn-oa-04.gd.ctc.com/ctc.com
             ......................... GDDCN-OA-04 passed test MachineAccount
          Starting test: Services
             * Checking Service: Dnscache
             * Checking Service: NtFrs
             * Checking Service: IsmServ
             * Checking Service: kdc
             * Checking Service: SamSs
             * Checking Service: LanmanServer
             * Checking Service: LanmanWorkstation
             * Checking Service: RpcSs
             * Checking Service: w32time
             * Checking Service: NETLOGON
             ......................... GDDCN-OA-04 passed test Services
          Test omitted by user request: OutboundSecureChannels
          Starting test: ObjectsReplicated
             GDDCN-OA-04 is in domain DC=gd,DC=ctc,DC=com
             Checking for CN=GDDCN-OA-04,OU=Domain Controllers,DC=gd,DC=ctc,DC=com in domain DC=gd,DC=ctc,DC=com on 1 servers
                Object is up-to-date on all servers.
             Checking for CN=NTDS Settings,CN=GDDCN-OA-04,CN=Servers,CN=GD-OADCN,CN=Sites,CN=Configuration,DC=ctc,DC=com in domain CN=Configuration,DC=ctc,DC=com on 1 servers
                Object is up-to-date on all servers.
             ......................... GDDCN-OA-04 passed test ObjectsReplicated
          Starting test: frssysvol
             * The File Replication Service SYSVOL ready test
             File Replication Service's SYSVOL is ready
             ......................... GDDCN-OA-04 passed test frssysvol
         
    以下为摘要132网段中的一台设置为GC的repadmin /showreps部分信息:
    GD-OADCN\GDDCN-OA-04

    DC Options: IS_GC

    Site Options: (none)

    DC object GUID: d4b507f8-1536-428c-bafd-741af55467c7

    DC invocationID: 13e37b09-806e-42c3-af0c-55e6dc682063

    ==== INBOUND NEIGHBORS ======================================

    CN=Configuration,DC=ctc,DC=com

        gdsite\GDAD02 via RPC

            DC object GUID: 5f402b6e-cc85-417e-a26f-05cfaf9730c3

            Last attempt @ 2009-04-24 11:20:29 was successful.

        gddcnsite\GDDCN-AD-02 via RPC

            DC object GUID: f5f21fe2-9004-4d86-9210-002fd97d34b2

            Last attempt @ 2009-04-24 11:20:50 was successful.

        GD-OADCN\GDDCN-OA-01 via RPC

            DC object GUID: d8786ff3-45d1-4994-ac1f-0c8594549901

            Last attempt @ 2009-04-24 11:21:32 was successful.

        GD-OADCN\GDDCN-OA-03 via RPC

            DC object GUID: f50d0e29-f8a7-4dc4-b30c-8c31ae74c568

            Last attempt @ 2009-04-24 11:22:14 failed, result -2146893022 (0x80090322):

                目标主要名称不正确。

            2193 consecutive failure(s).

            Last success @ 2009-04-04 12:52:24.

        gdsite\GDAD01 via RPC

            DC object GUID: 2c1d2f7a-c889-49b6-8a28-a193ccf4dbf0

            Last attempt @ 2009-04-24 11:22:15 failed, result -2146893022 (0x80090322):

                目标主要名称不正确。

            9043 consecutive failure(s).

            Last success @ (never).

        GD-OADCN\GDDCN-OA-02 via RPC

            DC object GUID: 3fb8201f-799d-4432-ba50-d8fc34d2aa4c

            Last attempt @ 2009-04-24 11:24:02 failed, result -2146893022 (0x80090322):

                目标主要名称不正确。

            2129 consecutive failure(s).

            Last success @ 2009-04-04 04:36:50.

      
    如有碰到以上故障日志信息的朋友,请多多帮忙给点建议,谢谢!
     

    2009年4月25日 12:57
  • 您先暂时修改这4台,其它不变!

    by-陈陈!


    silence-陈陈 双手剑的时代来临!
    2009年4月26日 10:33