Discussion Locked

Repl fails indicating schema mismatch.

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

After a customer upgraded Exchange 5.5 to 2000 on his Win2k network, active dir replication fails indicating that there is a
schema mismatch between the servers. I could
find nothing about this at support.ms.

Anyone have a fix?

BJ

7 replies

by jrubinstein

Exchange 2000 will alter the schema for a domain. If the customer has deployed the application in one domain, that domain will now effectively be in a different forest to the others. As far as I know there shouldn't be a problem within the one domain.

The problem may well be a little complicated to sort out. Assuming that the customer is trying to reestablish communication between domains, there are two routes, he or she could upgrade all domains with Exchange 2000. Alternatively they will need to clean up the active directory entries from each side so that they no longer think they know about the other domains existing within their own forest, use ADSI edit for this, its in the support tools or resource kit tools. Then, when the two forests are properly cleaned up, the user can establish external trusts between the two forests.

by bjackson

The customer has only one domain. This condition is preventing him from managing the directory from any server except the 'dominant' server, or so it appears. How can I correct this "schema mismatch"?

by jrubinstein

Okay so there's only one domain, my next question is, was Exchange 2000 upgrade focussed on the schema master. For each domain forest there can only be one schema master and this is the only machine on which the schema can be altered. Is is possible that the upgrade was done on a machine which had been isolated from the network and if so is it possible that someone told it to seize the schema master role?.

The way to find out which machine has Schema master role is to launch and MMC and add the schema console, right click the active directory schema and choose operations master.

It's possible that there is a schema master in the domain and that the machine on which Exchange was first installed both think they are schema masters.If this is the problem the answer may be to reinstall Exchange 2000 on the schema master itself. This machine does not need to be in constant contact with the domain, so it could be done offline. I don't know but I would suspect you would need to take out and reinstall active directory on the domain controller on which the first attempt to upgrade took place.

by jrubinstein

Okay so there's only one domain, my next question is, was Exchange 2000 upgrade focussed on the schema master. For each domain forest there can only be one schema master and this is the only machine on which the schema can be altered. Is it possible that the upgrade was done on a machine which had been isolated from the network and if so is it possible that someone told it to seize the schema master role?.

The way to find out which machine has Schema master role is to launch an MMC and addthe schema console, right click the active directory schema and choose operations master.

It's possible that there is a schema master in the domain and that the machine on which Exchange was first installed also thinks that it is now a schema masters.

If this is the problem, the answer may be to reinstall Exchange 2000 on the schema master itself. This machine does not need to be in constant contact with the domain, so it could be done offline. I don't know but I would suspect you wouldneed to take out and reinstall active directory on the domain controller on which the first attempt to upgrade took place.

by bjackson

While some of what you say may be true, the problem is a symptom of a problem with the Exchange 5.5 -> 2000 upgrade. Microsoft is aware and there is a pre-SP2 hotfix for it.

Thanks for your efforts jrubenstein

This discussion is closed to new replies.