Код ошибки 8224 exchange


admin ~
Modified: 16-10-2017 ~ Exchange Server ~ 4 Minutes Reading

Summary:- Most of the time users have encountered the exchange server error 8224 and fail to the load’s Schema when trying to update or upgrade Exchange server version from lower versions to 2010, 2013 and 2016. The article highlights the cause of the connection cannot be established the error code is 8224 and explains the quick tips to fix exchange server error code 8224 precisely.

fix exchange server error code 8224

Brief Introduction About Exchange Server EDB Database

Exchange Server is the simply the email and calendaring server developed by the Microsoft Inc.
It runs on the top of the Windows Server and follows the client server architecture. It created EDB file in the back end to save the of clients into it. Due to its comprehensive security features which make it feasible to server the large as the well small organization to meet their internal communication needs.
Location of Exchange Server Database File in Different Versions.

The location of EDB file according to Versions of Exchange Server.
For Exchange Server Version 2000 & 2003
C:Program FilesExchsrvrmbdpriv.edb ( Private Folder)
C:Program FilesExchsrvrmbdpub1.edb ( Public Folder)
For Exchange Server Version 2007
C:Program FilesMicrosoftExchange ServerMailboxFirst Storage GroupMailbox Database.edb
C:ProgramFilesMicrosoftExchange ServerMailboxFirst Storage GroupPublic Folder Database.edb
For Exchange Server Version 2010
C:Program FilesMicrosoftExchange ServerV14Mailbox DatabaseMailbox Database.edb
C:Program FilesMicrosoftExchange ServerV14Public Folder DatabasePublic Folder Database.edb
For Exchange Server Version 2013
C:Program FilesMicrosoftExchange ServerV15MailboxMailbox database NameMailbox database Name.edb
For Exchange Server Version 2016
C:Program FilesMicrosoftExchange ServerV15MailboxMailbox Database Name.edb

The Possible Reasons For Exchange Server Error Code 8224

There might be many reasons for the Error there was an error while running ‘ldifde.exe’ to import the schema file exchange 2013/2010. Some of them are explained below:-
1. There might be the possibility that some corruption or damage occurs in the files of exchange server in the default installation location on Windows Server while upgrading or updating the Exchange server.
2. Domain Controller is in Offline state or decommissioned incorrectly causing replica issues
3. The Corrupted File System will also cause for error, the connection cannot be established the error code is 8224
4. Abnormal deletion of files
5. Incomplete installation or uninstallation
6. Malicious software or virus attack can also cause the exchange server error 8224

The Solution to Fix the Exchange Server Error Code 8224 -Ldifde.exe Failed to Import Schema  

There are two ways to fix there was an error while running ‘ldifde.exe’ to import the schema file exchange 2013/2010.
1. Manual Solution
2. Professional Solution

The Manual Method to Fix Exchange Server 8224 Error While Running ‘ldifde.exe’ to Import The Schema File Exchange

  1. Locate FMSO Server on the network
  2. Put the Exchange DVD in the schema master or use it from the network and make sure it is available to connect with Schema Master Server
  3. By using the command line, change the directory of DVD in the same directory in which exchange files are installed.
  4. Run the Command X:Setup /PrepareSchema.
  5. Then after running this command X:Setup /PrepareAD

The Professional or the Alternative approach to fix Exchange Server Error Code 8224

  1. Delete the Domain Controllers which are not in use or in stale conditions.
  2. Then Run the AD Metadata clean up
  3. Delete State Domain Controllers from the Active directory sites and services
  4. After they delete the unused or stale domain name servers using the DNS properties
  5. Restart or reboot all the Domain controllers in the site and run the setup /PrepareAD /OrganizationName: XXX
  6. After completion of above setup run setup/preparealldomains

Note if above methods pop any error message then you need to specify the organization name and run X:Setup /PrepareAD /OrganizationName:” Your Organization Name”

The steps to Restore the Exchange Server after the completion of above methods
  1. Logged into your system using the Admin accounts
  2. Then after go to start >> All Programs >> System Tools >> System Restore
  3. Select Restore my computer to the earlier state and then click on next.
  4. Choose the most recent system restore points from the system restore
  5. Then click on the confirmation window and reboot the system
The Bottom Line  

As far, we have discussed the common tips and tricks to fix exchange server 8224 error while running ‘ldifde.exe’ to import the schema file exchange. But the uncertainty always exists with the manual methods. This may cause the corruption issues in exchange database file. So make sure that you have the recent backup of exchange server database file. If any how exchange server database file gets corrupt then you can use Exchange EDB Repair tool for the same. It has the ability to fix all the issues related to exchange database file in quick time.

Источник
  • Remove From My Forums

  • Question

  • Hi, here is a problem I have been bashing my head with for about a week. I am transitioning to Exchange 2010 from 2003. I have two DC’s running Windows Server 2003 Sp2, one of which is the Exchange 2003 server. I have just brought online a windows 2008R2
    member server, which I am attempting to install exchange 2010 on. I get the following error message during installation.

    Organization Preparation
    Failed

    Error:
    The following error was generated when «$error.Clear(); install-ExchangeSchema -LdapFileName ($roleInstallPath + «SetupData»+$RoleSchemaPrefix + «schema1.ldf»)» was run: «There was an error while running ‘ldifde.exe’ to
    import the schema file ‘C:WindowsTempExchangeSetupSetupDataPostExchange2003_schema1.ldf’. The error code is: 8224. More details can be found in the error file: ‘C:Usersadministrator.CFNAppDataLocalTemp2ldif.err'».

    There was an error while running ‘ldifde.exe’ to import the schema file ‘C:WindowsTempExchangeSetupSetupDataPostExchange2003_schema1.ldf’. The error code is: 8224. More details can be found in the error file: ‘C:Usersadministrator.CFNAppDataLocalTemp2ldif.err’

    Elapsed Time: 00:00:22

    And from the ldif.err:

    The connection cannot be established

    The error code is 8224

    ——

    Now I have checked dns, all is good. I can resolve the DC without issue.

    I have done dcdiag and netdiag and passes all tests. I have even written a hosts file, all this to no avail.

    Any help would be appreciated.

    Thanks

    B

Answers

    • Marked as answer by

      Friday, June 25, 2010 10:33 AM

  • Hi Friends,

    I was stuck with the very same issue for last 2 days. To fix this,

    1)deleted all the stale Domain Controllers

    2) initiated AD metadata cleanup

    3) deleted state DC’s from AD Sites and Services

    4)deleted stale Name Servers from DNS properties

    5) Reboot all DC’s in the site

    6) Run setup/PrepareAD /OrganizationName:XXX   after completion   setup/preparealldomains

    DONE! Works like a charm……. Try it out and let me know.

    • Edited by
      Binoj Baburaj
      Friday, June 29, 2012 10:38 AM
    • Proposed as answer by
      Liaqat Bashir
      Thursday, July 12, 2012 8:12 PM
    • Marked as answer by
      Gavin-Zhang
      Friday, July 13, 2012 2:11 AM

Источник
  • Remove From My Forums

  • Общие обсуждения

  • This error, on installation, is directly correlated to the Windows Firewall.

    Error 8224 is easily resolved by checking the Windows Firewall Profile and either, A. Disable Domain Profile firewall as well as Private and Public Profles.  B.  Disable or turn off Windows Firewall and change the state of the service to Manual.

    Once this action has been taken on ALL DC’s, and then Each rebooted, validate your domain replication and netlogin services are available by starting at the root DC and validate if you can reach the other DC’s via browser
    \DC1… You should then see a minimum of two folders; NETLOGON and SYSVOL.. there may be other folders depending on your environment; but you MUST see these two folders from EVERY DC that is in your plan to launch or install Exchange
    2013 on.

    Cross validate on ALL DC’s you can see all shares and this error will be a thing of the past.

    • Изменен тип

      9 ноября 2012 г. 2:13
      sharing

Источник

Error Code 8224 While Running Ldifde.exe to Import Schema File

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.

About the Author

Paul is a former Microsoft MVP for Office Apps and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul no longer writes for Practical365.com.

Источник

Уважаемые друзья, помогите пожалуйста разобраться. Моя проблема не нова, но весь материал который я находил по ней не приводил к ее решению ни как у меня ни у просящих помощи на форумах.

Есть сервер Exchange 2010 — sh2010, контроллер домена — win2008.

Возникла задача обновить sh2010 до SP3, но при установке обновления выскакивает следующая ошибка:

Подготовка организации
Ошибка

Ошибка:
При выполнении «$error.Clear();
 install-ExchangeSchema -LdapFileName ($roleInstallPath + «SetupData»+$RoleSchemaPrefix + «schema53.ldf»)

» произошла следующая ошибка: «Произошла ошибка при выполнении ‘ldifde.exe’ для импорта файла схемы ‘C:WindowsTempExchangeSetupSetupDataPostExchange2003_schema53.ldf’. Код ошибки: 8245. Дополнительные сведения см. в файле
ошибок: ‘C:UsersexchAppDataLocalTempldif.err’».

Произошла ошибка при выполнении ‘ldifde.exe’ для импорта файла схемы ‘C:WindowsTempExchangeSetupSetupDataPostExchange2003_schema53.ldf’. Код ошибки: 8245. Дополнительные сведения см. в файле ошибок: ‘C:UsersexchAppDataLocalTempldif.err’
Нажмите здесь для получения справки…

Прошло времени: 00:01:05

‘C:UsersexchAppDataLocalTempldif.err’:

Entry DN: CN=ms-Exch-Excluded-Mailbox-Databases,CN=Schema,CN=Configuration,DC=domain,DC=ru
  ,    200:  

   : 0x20bb  :  OID.

  ::

000020BB: SvcErr: DSID-032603C0, problem 5003 (WILL_NOT_PERFORM), data 8379

ldif.log:

  «win2008.domain.ru»

       SSPI

    «C:WindowsTempExchangeSetupSetupDataPostExchange2003_schema53.ldf»

 
1: (null)
Entry DN: (null)
  .

2: CN=ms-Exch-Exchange-Assistance,CN=Schema,CN=Configuration,DC=domain,DC=ru
Entry DN: CN=ms-Exch-Exchange-Assistance,CN=Schema,CN=Configuration,DC=domain,DC=ru
  .

3: (null)
Entry DN: (null)
  .

4: CN=Mail-Recipient,CN=Schema,CN=Configuration,DC=domain,DC=ru
Entry DN: CN=Mail-Recipient,CN=Schema,CN=Configuration,DC=domain,DC=ru
  .

5: CN=Mail-Recipient,CN=Schema,CN=Configuration,DC=domain,DC=ru
Entry DN: CN=Mail-Recipient,CN=Schema,CN=Configuration,DC=domain,DC=ru
  .

6: CN=Mail-Recipient,CN=Schema,CN=Configuration,DC=domain,DC=ru
Entry DN: CN=Mail-Recipient,CN=Schema,CN=Configuration,DC=domain,DC=ru
  .

7: CN=ms-Exch-Exchange-Server,CN=Schema,CN=Configuration,DC=domain,DC=ru
Entry DN: CN=ms-Exch-Exchange-Server,CN=Schema,CN=Configuration,DC=domain,DC=ru
  .

8: CN=ms-Exch-Organization-Container,CN=Schema,CN=Configuration,DC=domain,DC=ru
Entry DN: CN=ms-Exch-Organization-Container,CN=Schema,CN=Configuration,DC=domain,DC=ru
  .

9: (null)
Entry DN: (null)
  .

10: CN=ms-Exch-Organization-Summary,CN=Schema,CN=Configuration,DC=domain,DC=ru
Entry DN: CN=ms-Exch-Organization-Summary,CN=Schema,CN=Configuration,DC=domain,DC=ru
  .

11: (null)
Entry DN: (null)
  .

12: CN=ms-Exch-Organization-Container,CN=Schema,CN=Configuration,DC=domain,DC=ru
Entry DN: CN=ms-Exch-Organization-Container,CN=Schema,CN=Configuration,DC=domain,DC=ru
  .

13: (null)
Entry DN: (null)
  .

14: CN=ms-Exch-External-Sync-State,CN=Schema,CN=Configuration,DC=domain,DC=ru
Entry DN: CN=ms-Exch-External-Sync-State,CN=Schema,CN=Configuration,DC=domain,DC=ru
  .

15: CN=ms-Exch-Partner-Id,CN=Schema,CN=Configuration,DC=domain,DC=ru
Entry DN: CN=ms-Exch-Partner-Id,CN=Schema,CN=Configuration,DC=domain,DC=ru
  .

16: (null)
Entry DN: (null)
  .

17: CN=Mail-Recipient,CN=Schema,CN=Configuration,DC=domain,DC=ru
Entry DN: CN=Mail-Recipient,CN=Schema,CN=Configuration,DC=domain,DC=ru
  .

18: CN=ms-Exch-OWA-Mailbox-Policy,CN=Schema,CN=Configuration,DC=domain,DC=ru
Entry DN: CN=ms-Exch-OWA-Mailbox-Policy,CN=Schema,CN=Configuration,DC=domain,DC=ru
  .

19: CN=Site,CN=Schema,CN=Configuration,DC=domain,DC=ru
Entry DN: CN=Site,CN=Schema,CN=Configuration,DC=domain,DC=ru
  .

20: (null)
Entry DN: (null)
  .

21: CN=ms-Exch-Excluded-Mailbox-Databases,CN=Schema,CN=Configuration,DC=domain,DC=ru
Entry DN: CN=ms-Exch-Excluded-Mailbox-Databases,CN=Schema,CN=Configuration,DC=domain,DC=ru
  ,    200:  

   : 0x20bb  :  OID.

  ::

000020BB: SvcErr: DSID-032603C0, problem 5003 (WILL_NOT_PERFORM), data 8379

На форумах говорят что ошибка учетной записи, что нет прав. Я создал отдельную учетную запись exch и назначил ей нужные права, но не помогло. Уже не знаю что и делать, начинаю задумываться поднять новый сервер и перенести на него
базы со старого. Подскажите что можно попробывать и куда посмотреть. 


admin ~
Modified: 16-10-2017 ~ Exchange Server ~ 4 Minutes Reading

Summary:- Most of the time users have encountered the exchange server error 8224 and fail to the load’s Schema when trying to update or upgrade Exchange server version from lower versions to 2010, 2013 and 2016. The article highlights the cause of the connection cannot be established the error code is 8224 and explains the quick tips to fix exchange server error code 8224 precisely.

fix exchange server error code 8224

Brief Introduction About Exchange Server EDB Database

Exchange Server is the simply the email and calendaring server developed by the Microsoft Inc.
It runs on the top of the Windows Server and follows the client server architecture. It created EDB file in the back end to save the of clients into it. Due to its comprehensive security features which make it feasible to server the large as the well small organization to meet their internal communication needs.
Location of Exchange Server Database File in Different Versions.

The location of EDB file according to Versions of Exchange Server.
For Exchange Server Version 2000 & 2003
C:Program FilesExchsrvrmbdpriv.edb ( Private Folder)
C:Program FilesExchsrvrmbdpub1.edb ( Public Folder)
For Exchange Server Version 2007
C:Program FilesMicrosoftExchange ServerMailboxFirst Storage GroupMailbox Database.edb
C:ProgramFilesMicrosoftExchange ServerMailboxFirst Storage GroupPublic Folder Database.edb
For Exchange Server Version 2010
C:Program FilesMicrosoftExchange ServerV14Mailbox DatabaseMailbox Database.edb
C:Program FilesMicrosoftExchange ServerV14Public Folder DatabasePublic Folder Database.edb
For Exchange Server Version 2013
C:Program FilesMicrosoftExchange ServerV15MailboxMailbox database NameMailbox database Name.edb
For Exchange Server Version 2016
C:Program FilesMicrosoftExchange ServerV15MailboxMailbox Database Name.edb

The Possible Reasons For Exchange Server Error Code 8224

There might be many reasons for the Error there was an error while running ‘ldifde.exe’ to import the schema file exchange 2013/2010. Some of them are explained below:-
1. There might be the possibility that some corruption or damage occurs in the files of exchange server in the default installation location on Windows Server while upgrading or updating the Exchange server.
2. Domain Controller is in Offline state or decommissioned incorrectly causing replica issues
3. The Corrupted File System will also cause for error, the connection cannot be established the error code is 8224
4. Abnormal deletion of files
5. Incomplete installation or uninstallation
6. Malicious software or virus attack can also cause the exchange server error 8224

The Solution to Fix the Exchange Server Error Code 8224 -Ldifde.exe Failed to Import Schema  

There are two ways to fix there was an error while running ‘ldifde.exe’ to import the schema file exchange 2013/2010.
1. Manual Solution
2. Professional Solution

The Manual Method to Fix Exchange Server 8224 Error While Running ‘ldifde.exe’ to Import The Schema File Exchange

  1. Locate FMSO Server on the network
  2. Put the Exchange DVD in the schema master or use it from the network and make sure it is available to connect with Schema Master Server
  3. By using the command line, change the directory of DVD in the same directory in which exchange files are installed.
  4. Run the Command X:Setup /PrepareSchema.
  5. Then after running this command X:Setup /PrepareAD

The Professional or the Alternative approach to fix Exchange Server Error Code 8224

  1. Delete the Domain Controllers which are not in use or in stale conditions.
  2. Then Run the AD Metadata clean up
  3. Delete State Domain Controllers from the Active directory sites and services
  4. After they delete the unused or stale domain name servers using the DNS properties
  5. Restart or reboot all the Domain controllers in the site and run the setup /PrepareAD /OrganizationName: XXX
  6. After completion of above setup run setup/preparealldomains

Note if above methods pop any error message then you need to specify the organization name and run X:Setup /PrepareAD /OrganizationName:” Your Organization Name”

The steps to Restore the Exchange Server after the completion of above methods
  1. Logged into your system using the Admin accounts
  2. Then after go to start >> All Programs >> System Tools >> System Restore
  3. Select Restore my computer to the earlier state and then click on next.
  4. Choose the most recent system restore points from the system restore
  5. Then click on the confirmation window and reboot the system
The Bottom Line  

As far, we have discussed the common tips and tricks to fix exchange server 8224 error while running ‘ldifde.exe’ to import the schema file exchange. But the uncertainty always exists with the manual methods. This may cause the corruption issues in exchange database file. So make sure that you have the recent backup of exchange server database file. If any how exchange server database file gets corrupt then you can use Exchange EDB Repair tool for the same. It has the ability to fix all the issues related to exchange database file in quick time.

Источник

Понравилась статья? Поделить с друзьями:

Не пропустите эти материалы по теме:

  • Яндекс еда ошибка привязки карты
  • Код ошибки 803 симс
  • Код ошибки 80280100
  • Код ошибки 8024afff
  • Код ошибки 8024a008

    • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии