How to resolve 8418 schema mismatch

Lim Chong Sun 531 Reputation points
2021-02-17T01:15:39.627+00:00

Before the schema upgrade, the replication is already not working.

After I did a schema upgrade on the root AD. The replication is still not working because of tombstone period exceeded. I extended the tombstone period attribute. It still cannot replicate and give an 8414 schema mismatch.

What can I do to get back the replication?

Can I upgrade the schema using CD on the child AD?

Windows for business | Windows Client for IT Pros | Directory services | Active Directory
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Vicky Wang 2,741 Reputation points
    2021-02-17T09:14:46.07+00:00

    In order to resolve an issue where schema mismatch is cited, it is critical to understand the scenario in which the is error is being raised as it may influence the data collected. The common scenarios are:

    Recent Schema Update
    DC Promotion
    Normal Replication
    As stated previously, in the case of a recent schema update it is common for some DC's to report the schema mismatch as a normal part of processing the update. This state should only be investigated if it persists for an extended period Schema Mismatch during promotion of a DC is almost always a persistent issue that cannot be overcome without investigation and remedial steps being taken.

    Initial Data Collection

    The aim of the initial data collection is to try to capture information sufficient to identify if a known issue is being experienced or if other issues are contributing to the failure.

    Collecting replication data for all DC's in the forest is advised particularly in the case where a schema mismatch has been noted after a recent Schema Update or during normal replication monitoring. Collecting this data helps identify any pockets of replication failure on which to focus.

    Repadmin showrepl * /csv > allrepl.csv

    Once all the DC's experiencing replication failures, of ANY form, have been identified from the repadmin /showrepl data focus cam move to specific DC's.

    In the case where DCpromo fails with a schema mismatch the following data should be collected:

    DCpromo and DCpromoUI logs
    NTDS Diagnostic Event Logging on both the source and destination DC as described below in "Data Collection Phase 2"
    Ldifde Export of the Schema partition as described below in the "Schema Review"

    reference:https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/replication-error-8418

    Best wishes
    Vicky

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.