Monday, November 9, 2015

Fix Error Code 8224: Ldifde Exchange 2010 Failed to Import Schema File

While running the setup on Exchange Server to install or upgrade it, got the following error message.

“There was an error while running ‘ldifde.exe’ to import the schema file ‘C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema0.ldf’. The error code is: 8224.”

An update to Active Directory is involved while installing ldifde Exchange 2010 and it failed to import schema file on Exchange Server.

What is Error Code 8224 in Exchange Server?

It is a codename given by Windows software & drivers vendors to categorize the error from other errors faced during installation or upgrading ldifde Exchange 2010 and it failed to import schema file on  Exchange Server.
It contains technical description and is of hexadecimal format. This error indicates the location in the memory where the error occurred at the time of loading the instruction. The error may contain some added parameters, which describe the syntax and schematics of the error code.

Reasons for Error Code 8224

  • It may occur due to damage caused to the files in the Windows, which are responsible for installing or upgrading Exchange Server.
  • Corrupted system files can lead to this error.
  • Improper deletion of files, incomplete installation/uninstallation or a virus attack can cause the following error.

All these activities may lead to corruption of the system files and give rise to wrong or missing information, which leads to improper installation of the application.

Challenges Faced by Users

  • Not able to complete the installation or upgrade the Exchange Server.
  • Ldifde.exe failed to load schema file.
  • Can’t configure organization name, AD & schema.


The error can be fixed manually or by using an application.

Manual Methods

1. Locate FSMO Servers on the network.

2. Put the Exchange DVD in the schema master (Or share it over the network and connect to it from the schema master server).

3. In command line, change DVD Drive/Directory having Exchange setup files in it.

4. If you are using Exchange 2003 then follow this step.

Run the following command, (If Exchange 2003 not present, skip to the next step).

X:\Setup /PrepareLegacyExchangePermissions (Where "X" is CD ROM drive letter)

5. Run the following command:
X:\Setup /PrepareSchema

6. Run the following command:
X:\Setup /PrepareAD

Alternative Method

1. First of all, delete the stale Domain Controllers.

2. Then initiate AD metadata cleanup.

3. Delete state DC's from AD Sites and Services.

4. Then delete stale Name Servers from DNS properties.

5. Reboot all DC's in the site and Run setup/PrepareAD /OrganizationName:XXX   after completion   setup/preparealldomains

If Exchange organization name is required then specify an organization name and use the /organizationName parameter.
If that is the case, then run the following command:
X:\Setup /PrepareAD /OrganizationName:"Your required org name"

Restore Method

1. Start your computer by logging in as an administrator.

2. Click the Start button then select All Programs, Accessories, System Tools, and then click on System Restore.

3. Select Restore My Computer to An Earlier Time in the new window and then click Next.

4. Click on the most recent system restore point from the system restore point by selecting it from the system restore list.

5. Click Next on the confirmation window and restart the computer when the restoration wizard is finished.


You need to look at the existing EDB file of the Exchange Server while upgrading.

This error can give you headache if you are installing or doing upgrade on Exchange Server. I hope the above steps will guide the user to fix this error.

For any query or suggestions, do comment.


Post a Comment

Post a reply