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
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.
Thank you ! You resolved my problem !
Thank you so much!
I installed successs after to apply your recommendation!
Thank you soo much!! man you helped me a lot 🙂
Wow, it’s worked for me
Oh, my! I’ve been trying to solve this problem for two days. Thank you so much, it works!
Wow! That worked for me as well. Glad I saw this
Thanks man!
i found the soltion, it is an inactive domain controller, i deleted it from the directory and it to work
Wow! That worked for me as well. Glad I saw this
Thanks man!
Hello, I am trying to install Exchange 2016 on Server 2012 R2, however, i always get the following error:
The following error was generated when “$error.Clear();
install-ExchangeSchema -LdapFileName ($roleInstallPath +
“Setup\Data\”+$RoleSchemaPrefix + “schema0.ldf”)
” was run:
“Microsoft.Exchange.Configuration.Tasks.TaskException: There was an error while
running ‘ldifde.exe’ to import the schema file
‘C:\Windows\Temp\ExchangeSetup\Setup\Data\PostWindows2003_schema0.ldf’. The
error code is: 8224. More details can be found in the error file:
‘C:\Users\tochukwuo\AppData\Local\Temp\ldif.err’
at
Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception,
ErrorCategory errorCategory, Object target, String helpUrl)
at
Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.ImportSchemaFile(
String
schemaMasterServer, String schemaFilePath, String macroName, String macroValue,
WriteVerboseDelegate writeVerbose)
at
Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.InternalProcessRe
cord()
at Microsoft.Exchange.Configuration.Tasks.Task.b__91_1()
at
Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String
funcName, Action func, Boolean terminatePipelineIfFailed)”.
The Exchange Server setup operation didn’t complete. More details can be found
in ExchangeSetup.log located in the :\ExchangeSetupLogs folder.
exactly the same problem, did you find the solution
We had the exact problem. Here is what we did the fix the problem:
1) checked AD sites and services and removed an old DC
2) Installed AD Replication Status Tool 1.0 (Microsoft tool)
3) Ran the tool and found there was a Replication error:
– Replication error -2146893022 The target principal name is incorrect
4) Ran through KB2090913
– Stop KDC Services
– Ran the command ” Repadmin /replicate DC1.contoso.com DC2.contoso.com “DC=contoso,DC=com” ”
– Started the KDC service back up
Note: You may need to run the Repadmin command a few times as we also had an issue with “CN=Configuration,DC=contoso,DC=com”
I’d have a read through KB2090913 before running the above commands. Hope this sorts you out.
I also got this error when sites and services were not configured properly. There would have been a latency of 70ms or so between the domain controllers.
Hi, same error comes if you just leave your Windows firewall on, Disable FW (not the service) and things work fine again and schema extension works! Worth trying in any case…
Oh, my! I’ve been trying to solve this problem for two days. Thank you so much, it works!
Thank you soo much!! man you helped me a lot 🙂
Thank you!
It was the solution for my situation!