none
Problema com replicação RRS feed

  • Pergunta

  • Senhores estou com problema para replicar entre os dc's.
    segue alguns log's.



    NETDIAG:


        Computer Name: HLD-S-AD02
        DNS Host Name: hld-s-ad02.glibra.corp
        System info : Microsoft Windows Server 2003 R2 (Build 3790)
        Processor : x86 Family 6 Model 23 Stepping 6, GenuineIntel
        List of installed hotfixes :
            KB924667-v2
            KB925398_WMP64
            KB925876
            KB925902
            KB926122
            KB927891
            KB929123
            KB930178
            KB932168
            KB933729
            KB933854
            KB935839
            KB935840
            KB936357
            KB936782
            KB938127
            KB938127-IE7
            KB938464
            KB938759-v4
            KB941569
            KB942830
            KB942831
            KB943055
            KB943460
            KB943485
            KB943729
            KB944338-v2
            KB944653
            KB945553
            KB946026
            KB948496
            KB948590
            KB948745
            KB949014
            KB950762
            KB950974
            KB951066
            KB951072-v2
            KB951698
            KB951746
            KB951748
            KB952069
            KB952954
            KB954211
            KB954550-v5
            KB954600
            KB955069
            KB955839
            KB956390
            KB956390-IE7
            KB956391
            KB956802
            KB956803
            KB956841
            KB957095
            KB957097
            KB958215-IE7
            KB958644
            KB958687
            KB960714-IE7
            KB960715
            KB961118
            KB961260-IE7
            KB967715
            Q147222


    Netcard queries test . . . . . . . : Passed

     

    Per interface results:

        Adapter : Local Area Connection

            Netcard queries test . . . : Passed


    Global results:


    Domain membership test . . . . . . : Passed


    NetBT transports test. . . . . . . : Passed
        List of NetBt transports currently configured:
            NetBT_Tcpip_{21581095-68FA-4DA0-AA83-B9267B40861B}
        1 NetBt transport currently configured.


    DNS test . . . . . . . . . . . . . : Passed
        PASS - All the DNS entries for DC are registered on DNS server '172.17.160.104' and other DCs also have some of the names registered.
           [WARNING] The DNS entries for this DC cannot be verified right now on DNS server 172.17.160.105, ERROR_TIMEOUT.
        PASS - All the DNS entries for DC are registered on DNS server '172.17.16.3' and other DCs also have some of the names registered.


    The command completed successfully























    Caching GUIDs.

    ..

    05cdd662-09e2-45aa-8a0e-e42af12080d6 @ USN     12361 @ Time 2007-05-02 12:32:15

    bd04ec08-9170-4e63-9c1b-c4ebec04c609 @ USN     19155 @ Time 2007-05-04 17:13:53

    3280f6a1-64cc-4b37-b2f9-37c0128be887 @ USN     12514 @ Time 2007-05-04 17:36:36

    8d648620-1639-4dfc-85a7-fe3f953b1b15 @ USN     41427 @ Time 2008-01-28 21:31:33

    0b6b622d-457b-4cbf-9a84-8146948c4c38 @ USN    611910 @ Time 2008-01-29 02:55:00

    9e1548ec-143c-4b3b-ab93-d4cc3970f44f @ USN    609540 @ Time 2008-01-29 12:00:31

    b984bd62-088a-404e-a3f6-0c5762b44d58 @ USN    679978 @ Time 2008-02-29 21:03:53

    44e615ef-0333-4208-853c-daaa90d5afaf @ USN    247695 @ Time 2008-03-25 08:06:22

    d93feab8-4e9b-4627-8cea-04b4ba006164 @ USN     32782 @ Time 2008-06-22 11:20:26

    2ba7d79b-f0dc-43b6-800d-c13bec2f49f5 @ USN     24671 @ Time 2008-06-22 11:59:46

    beba7347-42c7-4921-9d04-c18aae89b5fe @ USN    981709 @ Time 2008-06-25 13:52:26

    9bc5c1a7-9a8e-4f05-bf58-290a3d892144 @ USN     16531 @ Time 2008-07-04 11:36:34

    328e9840-8163-44d5-8fba-2098bfab7d27 @ USN     16501 @ Time 2008-07-05 17:06:25

    c5d9a541-5cda-4173-9764-12bbed5da244 @ USN   3474515 @ Time 2008-08-17 10:56:25

    ac125922-b645-496a-9a3d-760bfe7c314f @ USN    362304 @ Time 2008-12-16 20:23:07

    cf7d74bc-6036-4ebb-9091-aeccc44a73d0 @ USN   1706385 @ Time 2009-01-07 15:10:47

    9346b913-f735-4e22-9ca3-9b0d12207a8f @ USN   2539512 @ Time 2009-02-18 12:14:09

    T37\T37-S-DC-1 (retired)             @ USN   2155942 @ Time 2009-03-14 15:57:27

    7ea588f3-1cb6-4ad7-9920-374fd3733b43 @ USN     40963 @ Time 2009-05-19 14:14:48

    4d349173-2ac3-4ced-8385-7d095ec7573d @ USN     28712 @ Time 2009-05-19 16:32:45

    8d8014a9-fa42-444c-8bd4-db5143b327ad @ USN     28794 @ Time 2009-05-19 16:46:18

    bee867cf-b444-4782-afa6-e0df5a58e686 @ USN     49200 @ Time 2009-06-01 15:18:48

    b3af5c63-0b84-4eab-b433-64c04791d619 @ USN     32790 @ Time 2009-06-02 10:41:16

    6ae09960-c182-434d-9d88-10409f6b2d02 @ USN     33003 @ Time 2009-06-09 14:46:10

    0db1e75b-8ba1-41ef-a497-254fe2d401dd @ USN    189979 @ Time 2009-07-07 16:26:06

    83cca608-8986-4951-a945-d687950a3afc @ USN     43071 @ Time 2009-10-13 22:56:02

    CBT\LTM-S-003001                     @ USN 122532921 @ Time 2009-11-13 14:13:00

    CBT\LBCBTDC02                        @ USN  29062236 @ Time 2009-11-14 09:53:06

    T1R\T1R-S-DC-1                       @ USN   5797600 @ Time 2009-11-14 09:53:52

    CBT\LBCBTDC01                        @ USN  20569307 @ Time 2009-11-14 09:53:56

    T1R\T1R-S-DC-2                       @ USN   5224451 @ Time 2009-11-14 09:53:56

    T37\T37-S-DC-2                       @ USN  50087828 @ Time 2009-11-14 09:57:36

    T37\T37-S-DC-1                       @ USN  42341270 @ Time 2009-11-14 09:58:04

    228d3b0e-72c9-4f23-a9c5-33514cc1c2bf @ USN   1103009 @ Time 2010-01-18 08:41:39

    TVAL\TEVAL-S-DC-2                    @ USN     41319 @ Time 2010-01-18 13:47:21

    TVAL\TEVAL-S-DC-1                    @ USN   1214975 @ Time 2010-01-18 13:48:22

    3266d18b-cf6e-406d-913f-a715d9f9d967 @ USN  19772224 @ Time 2010-01-20 14:56:43

    CAD\CAD-S-DC-1                       @ USN    621199 @ Time 2010-01-20 15:19:59

    29a8e9b5-1a81-43a9-a544-a2c157d45f8b @ USN     28786 @ Time 2010-01-20 15:59:23

    HLD\HLD-S-AD01                       @ USN   5562938 @ Time 2010-01-20 16:17:50

    HLD\HLD-S-AD02                       @ USN   3850893 @ Time 2010-01-20 16:18:26






















    HLD\HLD-S-AD02

    DC Options: IS_GC

    Site Options: IS_INTER_SITE_AUTO_TOPOLOGY_DISABLED

    DC object GUID: 61f7f5a7-2718-4f56-a709-dadc05f1ce7c

    DC invocationID: 216b5cbc-0f1e-498a-8e9d-ac2decb6838b

     

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

     

    DC=glibra,DC=corp

        T37\T37-S-DC-1 via RPC

            DC object GUID: 7a54f232-5a2c-4ebc-8973-95ae9e6aab27

            Last attempt @ 2010-01-20 16:34:54 failed, result -2146893022 (0x80090322):

                Can't retrieve message string -2146893022 (0x80090322), error 1815.

            833 consecutive failure(s).

            Last success @ 2009-11-14 09:58:06.

        HLD\HLD-S-AD01 via RPC

            DC object GUID: f362316b-ca5f-4e51-9a96-599a45bb0003

            Last attempt @ 2010-01-20 16:35:24 was successful.

     

    CN=Configuration,DC=glibra,DC=corp

        T37\T37-S-DC-1 via RPC

            DC object GUID: 7a54f232-5a2c-4ebc-8973-95ae9e6aab27

            Last attempt @ 2010-01-20 16:34:54 failed, result -2146893022 (0x80090322):

                Can't retrieve message string -2146893022 (0x80090322), error 1815.

            415 consecutive failure(s).

            Last success @ 2009-12-17 12:48:34.

        HLD\HLD-S-AD01 via RPC

            DC object GUID: f362316b-ca5f-4e51-9a96-599a45bb0003

            Last attempt @ 2010-01-20 16:35:29 was successful.

     

    CN=Schema,CN=Configuration,DC=glibra,DC=corp

        HLD\HLD-S-AD01 via RPC

            DC object GUID: f362316b-ca5f-4e51-9a96-599a45bb0003

            Last attempt @ 2010-01-20 16:34:06 was successful.

        T37\T37-S-DC-1 via RPC

            DC object GUID: 7a54f232-5a2c-4ebc-8973-95ae9e6aab27

            Last attempt @ 2010-01-20 16:34:54 failed, result -2146893022 (0x80090322):

                Can't retrieve message string -2146893022 (0x80090322), error 1815.

            415 consecutive failure(s).

            Last success @ 2009-12-17 12:48:34.

     

    DC=DomainDnsZones,DC=glibra,DC=corp

        HLD\HLD-S-AD01 via RPC

            DC object GUID: f362316b-ca5f-4e51-9a96-599a45bb0003

            Last attempt @ 2010-01-20 16:34:06 was successful.

        T37\T37-S-DC-1 via RPC

            DC object GUID: 7a54f232-5a2c-4ebc-8973-95ae9e6aab27

            Last attempt @ 2010-01-20 16:34:54 failed, result -2146893022 (0x80090322):

                Can't retrieve message string -2146893022 (0x80090322), error 1815.

            500 consecutive failure(s).

            Last success @ 2009-12-10 10:58:04.

     

    DC=ForestDnsZones,DC=glibra,DC=corp

        HLD\HLD-S-AD01 via RPC

            DC object GUID: f362316b-ca5f-4e51-9a96-599a45bb0003

            Last attempt @ 2010-01-20 16:34:06 was successful.

        T37\T37-S-DC-1 via RPC

            DC object GUID: 7a54f232-5a2c-4ebc-8973-95ae9e6aab27

            Last attempt @ 2010-01-20 16:34:55 failed, result -2146893022 (0x80090322):

                Can't retrieve message string -2146893022 (0x80090322), error 1815.

            500 consecutive failure(s).

            Last success @ 2009-12-10 10:59:38.

     

    Source: T37\T37-S-DC-1

    ******* 831 CONSECUTIVE FAILURES since 2009-12-17 12:48:34

    Last error: -2146893022 (0x80090322):

                Can't retrieve message string -2146893022 (0x80090322), error 1815.



















    Guardian
    quarta-feira, 20 de janeiro de 2010 18:58

Respostas

  • Execute o comando repadmin /replsummary /sort:delta afim de verificar o delta de replicação de todos os dc's da sua rede (executar uma vez por floresta);

    Execute o dcdiag /test:dns /s:(servidor) afim de verificar a configuracao do serviço de DNS (executar uma vez por DNS server);

    Verifique se os registros cname GUID._msdcs.dominio são resolvidos a partir de cada DC, estes registros são utilizados para resolver o nome do parceiro de replicação;

    Execute o dnslint /ad ip-dc /s ip-dns afim de verificar se algum registro importante esta faltando no DNS server (executar uma vez por floresta);

    Caso nao encontre nenhum problema nos comandos acima, execute o dcdiag /v /s:(dc) em cada DC e verifique o output do mesmo (executar uma vez por DC);

    []'s
    • Marcado como Resposta Richard Juhasz quinta-feira, 28 de janeiro de 2010 15:13
    terça-feira, 26 de janeiro de 2010 01:32
  • Cara, seu servidor esta com Lingering Object. Com isto ele para de replicar. Você pode usar o artigo abaixo para remover seu lingering object.

    http://technet.microsoft.com/en-us/library/cc785298(WS.10).aspx

    Qualquer duvida no procedimento posta aqui.
    Weslley Valadares
    • Marcado como Resposta Richard Juhasz quinta-feira, 28 de janeiro de 2010 15:13
    terça-feira, 26 de janeiro de 2010 10:56

Todas as Respostas

  • eventview





    Event Type: Error
    Event Source: NTDS Replication
    Event Category: Replication
    Event ID: 1864
    Date:  20/1/2010
    Time:  02:17:42
    User:  NT AUTHORITY\ANONYMOUS LOGON
    Computer: HLD-S-AD02
    Description:
    This is the replication status for the following directory partition on the local domain controller.
     
    Directory partition:
    CN=Schema,CN=Configuration,DC=glibra,DC=corp
     
    The local domain controller has not recently received replication information from a number of domain controllers.   The count of domain controllers is shown, divided into the following intervals.
     
    More than 24 hours:
    9
    More than a week:
    7
    More than one month:
    1
    More than two months:
    1
    More than a tombstone lifetime:
    0
    Tombstone lifetime (days):
    180
     Domain controllers that do not replicate in a timely manner may encounter errors. It may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects, and may be automatically blocked from future replication until it is reconciled.
     
    To identify the domain controllers by name, install the support tools included on the installation  CD and run dcdiag.exe.
    You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest.   The command is "repadmin /showvector /latency <partition-dn>".

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.



    Guardian
    quarta-feira, 20 de janeiro de 2010 18:59
  • Boa noite,

    Vamos por partes,


    Quantos AD você tem, e quais que não replicam?

    E quem é 172.17.16.3?
    quinta-feira, 21 de janeiro de 2010 00:53
  • Execute o comando repadmin /replsummary /sort:delta afim de verificar o delta de replicação de todos os dc's da sua rede (executar uma vez por floresta);

    Execute o dcdiag /test:dns /s:(servidor) afim de verificar a configuracao do serviço de DNS (executar uma vez por DNS server);

    Verifique se os registros cname GUID._msdcs.dominio são resolvidos a partir de cada DC, estes registros são utilizados para resolver o nome do parceiro de replicação;

    Execute o dnslint /ad ip-dc /s ip-dns afim de verificar se algum registro importante esta faltando no DNS server (executar uma vez por floresta);

    Caso nao encontre nenhum problema nos comandos acima, execute o dcdiag /v /s:(dc) em cada DC e verifique o output do mesmo (executar uma vez por DC);

    []'s
    • Marcado como Resposta Richard Juhasz quinta-feira, 28 de janeiro de 2010 15:13
    terça-feira, 26 de janeiro de 2010 01:32
  • Cara, seu servidor esta com Lingering Object. Com isto ele para de replicar. Você pode usar o artigo abaixo para remover seu lingering object.

    http://technet.microsoft.com/en-us/library/cc785298(WS.10).aspx

    Qualquer duvida no procedimento posta aqui.
    Weslley Valadares
    • Marcado como Resposta Richard Juhasz quinta-feira, 28 de janeiro de 2010 15:13
    terça-feira, 26 de janeiro de 2010 10:56