Announcement

Collapse
No announcement yet.

Is replication broken?

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

  • Is replication broken?

    I've got two Server 2008r2 DCs in one site and one another site. I'm trying to install Exchange 2010 and running into some issues. At the moment, I'm troubleshooting what appears to be a Schema problem.</p>

    I ran "setup /PrepareSchema", while logged in as our highest-rights account. The process reported that it completed and there are no errors in the Exchange setup log. However, when I browse the ADSI Edit to cn=OrganizationName,cn=microsoft exchange,cn=services,cn=configuration,dc=servicema gic,dc=com and select properties -> objectVersion, I see 6903 which is Exchange 2003 SP2.

    Next, I opened the AD Schema MMC plug-in and right-clicked on Active Directory Schema -> Change Active Directory Domain Controller. I see all three DCs, but the one that holds all the FSMO roles lists "Unavailble" as its status. That's odd because I have an RDP session to, and ran the schema update from, that DC.

    Finally, I ran repadmin /showrepl and got back something that looks like this:
    Repadmin: running command /showrepl against full DC localhost

    site1\dc1

    DSA Options: IS_GC

    Site Options: (none)

    DSA object GUID: bc5f3a5d-9509-4dd5-97f3-cea86f0134cb

    DSA invocationID: b102a18d-87f1-4d3d-be53-f5a65b3e8c16

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

    DC=company,DC=com

    site1\dc2 via RPC

    DSA object GUID: 08f46052-afd0-4843-920b-90fd210fd4ac

    Last attempt @ 2011-10-28 12:48:30 was successful.

    site2\dc3 via RPC

    DSA object GUID: 49e473eb-2509-4acb-b22d-377c152d5e3b

    Last attempt @ 2011-10-28 13:03:29 was delayed for a normal reason, result 8418 (0x20e2):

    The replication operation failed because of a schema mismatch between the servers involved.

    Last success @ 2011-10-28 12:48:30.

    CN=Configuration,DC=company,DC=com

    site1\dc2 via RPC

    DSA object GUID: 08f46052-afd0-4843-920b-90fd210fd4ac

    Last attempt @ 2011-10-28 12:48:30 was successful.

    site2\dc3 via RPC

    DSA object GUID: 49e473eb-2509-4acb-b22d-377c152d5e3b

    Last attempt @ 2011-10-28 13:03:29 was delayed for a normal reason, result 8418 (0x20e2):

    The replication operation failed because of a schema mismatch between the servers involved.

    Last success @ 2011-10-28 12:48:30.



    CN=Schema,CN=Configuration,DC=company,DC=com

    site1\dc2 via RPC

    DSA object GUID: 08f46052-afd0-4843-920b-90fd210fd4ac

    Last attempt @ 2011-10-28 12:52:14 was successful.

    site2\dc3 via RPC

    DSA object GUID: 49e473eb-2509-4acb-b22d-377c152d5e3b

    Last attempt @ 2011-10-28 13:03:29 was successful.



    DC=ForestDnsZones,DC=company,DC=com

    site1\dc2 via RPC

    DSA object GUID: 08f46052-afd0-4843-920b-90fd210fd4ac

    Last attempt @ 2011-10-28 12:48:30 was successful.

    site2\dc3 via RPC

    DSA object GUID: 49e473eb-2509-4acb-b22d-377c152d5e3b

    Last attempt @ 2011-10-28 13:03:29 was delayed for a normal reason, result 8418 (0x20e2):

    The replication operation failed because of a schema mismatch between the servers involved.

    Last success @ 2011-10-28 12:48:30.



    DC=DomainDnsZones,DC=company,DC=com

    site1\dc2 via RPC

    DSA object GUID: 08f46052-afd0-4843-920b-90fd210fd4ac

    Last attempt @ 2011-10-28 12:53:31 was successful.

    site2\dc3 via RPC

    DSA object GUID: 49e473eb-2509-4acb-b22d-377c152d5e3b

    Last attempt @ 2011-10-28 13:03:29 was delayed for a normal reason, result 8418 (0x20e2):

    The replication operation failed because of a schema mismatch between the servers involved.

    Last success @ 2011-10-28 12:48:30.
    Looking through the event log, I don't see any replication-related events under Application, System, DFS Replication, Directory Service, or File Replication Service.

  • #2
    Re: Is replication broken?

    Did you run the ADPREP on the Schema Master?

    Are you in a position to demote two of the DCs temporarily and then re-promote them so you know replication is in a good state?
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: Is replication broken?

      just throwin this out there

      could you run the schema update on the servers that don't have the right schema, or would that not work ?
      Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

      Comment


      • #4
        Re: Is replication broken?

        Has to be on schema master doesnt it?
        Tom Jones
        MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
        PhD, MSc, FIAP, MIITT
        IT Trainer / Consultant
        Ossian Ltd
        Scotland

        ** Remember to give credit where credit is due and leave reputation points where appropriate **

        Comment


        • #5
          Re: Is replication broken?

          yea, but it should also scream and prevent you from doin it.. so either it was run on a non-schema-master, or the masdter wasn't replicating properly
          Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

          Comment

          Working...
          X