While running Exchange Server 2013 setup to install or upgrade a server you may encounter the following error.

There was an error while running ‘ldifde.exe’ to import the schema file ‘C:WindowsTempExchangeSetupSetupDataPostExchange2003_schema0.ldf’. The error code is: 8224.

Exchange Server 2013 installs and upgrades usually involve an update to the Active Directory schema. This error message indicates that the import of schema changes failed.

On the Schema Master in your forest you may notice the following event logged in the Directory Service log.

Log Name: Directory Service Source: Microsoft-Windows-ActiveDirectory_DomainService Date: 4/09/2014 2:08:06 PM Event ID: 2092 Task Category: Replication Level: Warning Keywords: Classic User: ESPNETadministrator Computer: S1DC1.exchangeserverpro.net Description: This server is the owner of the following FSMO role, but does not consider it valid. For the partition which contains the FSMO, this server has not replicated successfully with any of its partners since this server has been restarted. Replication errors are preventing validation of this role. Operations which require contacting a FSMO operation master will fail until this condition is corrected. FSMO Role: CN=Schema,CN=Configuration,DC=exchangeserverpro,DC=net 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Log Name : Directory Service Source : Microsoft - Windows - ActiveDirectory_DomainService Date : 4 / 09 / 2014 2 : 08 : 06 PM Event ID : 2092 Task Category : Replication Level : Warning Keywords : Classic User : ESPNETadministrator Computer : S1DC1 . exchangeserverpro . net Description : This server is the owner of the following FSMO role , but does not consider it valid . For the partition which contains the FSMO , this server has not replicated successfully with any of its partners since this server has been restarted . Replication errors are preventing validation of this role . Operations which require contacting a FSMO operation master will fail until this condition is corrected . FSMO Role : CN = Schema , CN = Configuration , DC = exchangeserverpro , DC = net

The root cause is a replication issue with the domain controllers in the environment. In my experience this is usually due to a domain controller being offline, either due to a fault or due to it being decommissioned incorrectly.

After you have resolved any domain controller replication issues Exchange setup should be able to apply the schema updates without error.

C:Adminex2013cu6>setup /preparead /iacceptexchangeserverlicenseterms Welcome to Microsoft Exchange Server 2013 Cumulative Update 6 Unattended Setup Copying Files... File copy complete. Setup will now collect additional information needed for installation. Performing Microsoft Exchange Server Prerequisite Check Prerequisite Analysis COMPLETED Configuring Microsoft Exchange Server Organization Preparation COMPLETED The Exchange Server setup operation completed successfully. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 C : Adminex2013cu6 & gt ; setup / preparead / iacceptexchangeserverlicenseterms Welcome to Microsoft Exchange Server 2013 Cumulative Update 6 Unattended Setup Copying Files . . . File copy complete . Setup will now collect additional information needed for installation . Performing Microsoft Exchange Server Prerequisite Check Prerequisite Analysis COMPLETED Configuring Microsoft Exchange Server Organization Preparation COMPLETED The Exchange Server setup operation completed successfully .