Announcement

Collapse
No announcement yet.

Replication status

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Replication status

    I have 2 DC in the org.
    I done adprep /forestprep and adprep /domainprep on the DC1 server. All was successful.
    When i dorepadmin /showreps /v , it showed error below:
    C:\>repadmin /showreps /v
    Default-First-Site-Name\MAIL1
    DC Options: IS_GC
    Site Options: (none)
    DC object GUID: ddbfd81e-d8ed-43e4-b3e9-04dd8f65b866
    DC invocationID: efe830ba-3fa8-4b18-b280-c38a6e401527

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

    DC=pstechno,DC=com,DC=my
    Default-First-Site-Name\MAIL via RPC
    DC object GUID: 757cce0a-b702-446f-9dd5-02fcb352cd57
    Address: 757cce0a-b702-446f-9dd5-02fcb352cd57._msdcs.pstechno.com.my
    DC invocationID: 757cce0a-b702-446f-9dd5-02fcb352cd57
    SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
    USNs: 40524093/OU, 40524093/PU
    Last attempt @ 2013-11-18 11:45:13 failed, result 8418 (0x20e2):
    The replication operation failed because of a schema mismatch betwee
    n the servers involved.
    89 consecutive failure(s).
    Last success @ 2013-11-14 15:48:01.

    CN=Configuration,DC=pstechno,DC=com,DC=my
    Default-First-Site-Name\MAIL via RPC
    DC object GUID: 757cce0a-b702-446f-9dd5-02fcb352cd57
    Address: 757cce0a-b702-446f-9dd5-02fcb352cd57._msdcs.pstechno.com.my
    DC invocationID: 757cce0a-b702-446f-9dd5-02fcb352cd57
    SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
    USNs: 40524117/OU, 40524117/PU
    Last attempt @ 2013-11-18 11:45:14 failed, result 8418 (0x20e2):
    The replication operation failed because of a schema mismatch betwee
    n the servers involved.
    89 consecutive failure(s).
    Last success @ 2013-11-14 15:48:02.

    CN=Schema,CN=Configuration,DC=pstechno,DC=com,DC=m y
    Default-First-Site-Name\MAIL via RPC
    DC object GUID: 757cce0a-b702-446f-9dd5-02fcb352cd57
    Address: 757cce0a-b702-446f-9dd5-02fcb352cd57._msdcs.pstechno.com.my
    DC invocationID: 757cce0a-b702-446f-9dd5-02fcb352cd57
    SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
    USNs: 40530109/OU, 40530109/PU
    Last attempt @ 2013-11-18 11:45:14 was successful.

    DC=DomainDnsZones,DC=pstechno,DC=com,DC=my
    Default-First-Site-Name\MAIL via RPC
    DC object GUID: 757cce0a-b702-446f-9dd5-02fcb352cd57
    Address: 757cce0a-b702-446f-9dd5-02fcb352cd57._msdcs.pstechno.com.my
    DC invocationID: 757cce0a-b702-446f-9dd5-02fcb352cd57
    SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
    USNs: 40524094/OU, 40524094/PU
    Last attempt @ 2013-11-18 11:45:14 failed, result 8418 (0x20e2):
    The replication operation failed because of a schema mismatch betwee
    n the servers involved.
    89 consecutive failure(s).
    Last success @ 2013-11-14 15:48:02.

    DC=ForestDnsZones,DC=pstechno,DC=com,DC=my
    Default-First-Site-Name\MAIL via RPC
    DC object GUID: 757cce0a-b702-446f-9dd5-02fcb352cd57
    Address: 757cce0a-b702-446f-9dd5-02fcb352cd57._msdcs.pstechno.com.my
    DC invocationID: 757cce0a-b702-446f-9dd5-02fcb352cd57
    SYNC_ON_STARTUP DO_SCHEDULED_SYNCS WRITEABLE
    USNs: 40524094/OU, 40524094/PU
    Last attempt @ 2013-11-18 11:45:14 failed, result 8418 (0x20e2):
    The replication operation failed because of a schema mismatch betwee
    n the servers involved.
    89 consecutive failure(s).
    Last success @ 2013-11-14 15:48:02.

    Source: Default-First-Site-Name\MAIL
    ******* 89 CONSECUTIVE FAILURES since 2013-11-14 15:48:02
    Last error: 8418 (0x20e2):
    The replication operation failed because of a schema mismatch betwee
    n the servers involved.

    C:\>repadmin /syncall
    CALLBACK MESSAGE: The following replication is in progress:
    From: 757cce0a-b702-446f-9dd5-02fcb352cd57._msdcs.pstechno.com.my
    To : ddbfd81e-d8ed-43e4-b3e9-04dd8f65b866._msdcs.pstechno.com.my
    CALLBACK MESSAGE: Error issuing replication: 8418 (0x20e2):
    The replication operation failed because of a schema mismatch between the se
    rvers involved.
    From: 757cce0a-b702-446f-9dd5-02fcb352cd57._msdcs.pstechno.com.my
    To : ddbfd81e-d8ed-43e4-b3e9-04dd8f65b866._msdcs.pstechno.com.my
    CALLBACK MESSAGE: SyncAll Finished.

    SyncAll reported the following errors:
    Error issuing replication: 8418 (0x20e2):
    The replication operation failed because of a schema mismatch between the se
    rvers involved.
    From: 757cce0a-b702-446f-9dd5-02fcb352cd57._msdcs.pstechno.com.my
    To : ddbfd81e-d8ed-43e4-b3e9-04dd8f65b866._msdcs.pstechno.com.my

    What could it be wrong, and how to resolve?

  • #2
    Re: Replication status

    How long ago did you run the forest and domain prep?
    Regards,
    Jeremy

    Network Consultant/Engineer
    Baltimore - Washington area and beyond
    www.gma-cpa.com

    Comment


    • #3
      Re: Replication status

      Just yesterday.
      Today( after troubleshooting - DSRM, defrag and integrity success)

      still got error?

      At DC1
      C:\>repadmin /syncall
      CALLBACK MESSAGE: The following replication is in progress:
      From: 757cce0a-b702-446f-9dd5-02fcb352cd57._msdcs.pstechno.com.my
      To : ddbfd81e-d8ed-43e4-b3e9-04dd8f65b866._msdcs.pstechno.com.my
      CALLBACK MESSAGE: Error issuing replication: 8418 (0x20e2):
      The replication operation failed because of a schema mismatch between the servers involved.
      From: 757cce0a-b702-446f-9dd5-02fcb352cd57._msdcs.pstechno.com.my
      To : ddbfd81e-d8ed-43e4-b3e9-04dd8f65b866._msdcs.pstechno.com.my
      CALLBACK MESSAGE: SyncAll Finished.

      SyncAll reported the following errors:
      Error issuing replication: 8418 (0x20e2):
      The replication operation failed because of a schema mismatch between the servers involved.
      From: 757cce0a-b702-446f-9dd5-02fcb352cd57._msdcs.pstechno.com.my
      To : ddbfd81e-d8ed-43e4-b3e9-04dd8f65b866._msdcs.pstechno.com.my
      ==============================
      At DC2
      C:\>repadmin /syncall
      CALLBACK MESSAGE: Error contacting server 757cce0a-b702-446f-9dd5-02fcb352cd57._msdcs.pstechno.com.my (network error): -2146893022 (0x80090322):
      The target principal name is incorrect.
      CALLBACK MESSAGE: Error contacting server ddbfd81e-d8ed-43e4-b3e9-04dd8f65b866._msdcs.pstechno.com.my (network error): -2146893022 (0x80090322):
      The target principal name is incorrect.

      SyncAll exited with fatal Win32 error: 8440 (0x20f:
      The naming context specified for this replication operation is invalid.

      Comment


      • #4
        Re: Replication status

        Have you taken a look at this article?

        http://support.microsoft.com/kb/2734946
        Rules of life:
        1. Never do anything that requires thinking after 2:30 PM
        2. Simplicity is godliness
        3. Scale with extreme prejudice


        I occasionally post using a savantphone, so please don't laugh too hard at the typos...

        Comment


        • #5
          Re: Replication status

          yes i have look into it.

          DC1 schema ver : 47
          DC2 schema ver : 31

          Already increase the log diagnostic at DC1 to value 5.

          help please?

          Comment


          • #6
            Re: Replication status

            On DC2, please go through the event logs for DFS Replication, File Replication Service, Directory Services, and DNS Server and look for warnings and errors.

            Post back with the info.
            Regards,
            Jeremy

            Network Consultant/Engineer
            Baltimore - Washington area and beyond
            www.gma-cpa.com

            Comment


            • #7
              Re: Replication status

              attached capture screen of event viewer url:http://sdrv.ms/HYs5D1

              Comment


              • #8
                Re: Replication status

                Did you read through the warnings and errors? Do they say what the issue is?
                Regards,
                Jeremy

                Network Consultant/Engineer
                Baltimore - Washington area and beyond
                www.gma-cpa.com

                Comment


                • #9
                  Re: Replication status

                  Odd that the schema partition is replicated but everything else is complaining about the schema mismatch.

                  What does your topology look like? What sites and links are involved here?
                  Rules of life:
                  1. Never do anything that requires thinking after 2:30 PM
                  2. Simplicity is godliness
                  3. Scale with extreme prejudice


                  I occasionally post using a savantphone, so please don't laugh too hard at the typos...

                  Comment


                  • #10
                    Re: Replication status

                    Hi there,

                    You should resolve DNS issue on DC2 first ; as the repadmin output indicates GUID resolution failing.
                    It can be network connectivity (firewall ... use portQry to troubleshoot).
                    Make sure in the IPStack of DC2, that the primary DNS server is DC1.
                    Do some nslookup tests on the GUID to make sure its working.

                    Then when DNS is okay on DC2, the schema should replicate on DC2, then replication would start again to work.

                    Since replication is "pulling", DC2 needs to pull the schema update, but he can't because of the DNS issue (it doesnt find his partner with his guid).


                    LL

                    Comment


                    • #11
                      Re: Replication status

                      Hi all,

                      I already rectified the DNS problem. Thanks.

                      Comment


                      • #12
                        Re: Replication status

                        Hello,

                        Do you mean your replication issue is solved now ?


                        LL

                        Comment

                        Working...
                        X