Ldifde import error

Im try to import users using LDIFDE. Below is from the error log any help would be great

Entry DN: OU=Offices,DC=dcorporate,DC=com
changetype: add
Attribute 0) objectClass:top organizationalUnit
Attribute 1) ou:Offices
Attribute 2) distinguishedName:OU=Offices,DC=dcorporate,DC=com
Attribute 3) instanceType:4
Attribute 4) whenCreated:20060516154057.0Z
Attribute 5) whenChanged:20101201164754.0Z
Attribute 6) uSNCreated:54398
Attribute 7) uSNChanged:54398
Attribute name:Offices
Attribute 9) objectCategory:CN=Organizational-Unit,CN=Schema,CN=Configuration,DC=dcorporate,DC=com
Attribute 10) dSCorePropagationData:20110518135038.0Z 20110505174148.0Z 16010101000416.0Z

1: Entry already exists, entry skipped

Entry DN: CN=00728,OU=Offices,DC=dcorporate,DC=com
changetype: add
Attribute 0) objectClass:top person organizationalPerson user
Attribute 1) cn:00728
Attribute 2) c:IND
Attribute 3) l:Mumbai, India
Attribute 4) st: UNPRINTABLE BINARY(1)
Attribute 5) street:#225, 2nd. Floor, CTS 4207 (PT) Trace Centre, BKC Bandra E
Attribute 6) description:Mumbai, India
Attribute 7) postalCode:400051
Attribute telephoneNumber:91 22 42170400
Attribute 9) facsimileTelephoneNumber: UNPRINTABLE BINARY(1)
Attribute 10) distinguishedName:CN=00728,OU=Offices,DC=dcorporate,DC=com
Attribute 11) instanceType:4
Attribute 12) whenCreated:20070524025615.0Z
Attribute 13) whenChanged:20110322081430.0Z
Attribute 14) displayName:Office 00728
Attribute 15) uSNCreated:463425
Attribute 16) info:OFFICE_OBJECT
Attribute 17) uSNChanged:20391507
Attribute 18) co:IND
Attribute 19) company:TEK
Attribute 20) streetAddress:#225, 2nd. Floor, CTS 4207 (PT) Trace Centre, BKC Bandra E
Attribute 21) extensionAttribute3:OFFICE_OBJECT
Attribute 22) mailNickname:00728
Attribute 23) name:00728
Attribute 24) userAccountControl:546
Attribute 25) codePage:0
Attribute 26) countryCode:0
Attribute 27) accountExpires:0
Attribute 28) sAMAccountName:00728
Attribute 29) showInAddressBook:CN=Default Global Address List,CN=All Global Address Lists,CN=Address Lists Container,CN=dcorporate,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=dcorporate,DC=com CN=All Users,CN=All Address Lists,CN=Address Lists Container,CN=dcorporate,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=dcorporate,DC=com
Attribute 30) userPrincipalName:00728@dcorporate.com
Attribute 31) objectCategory:CN=Person,CN=Schema,CN=Configuration,DC=dcorporate,DC=com
Attribute 32) dSCorePropagationData:20110505174148.0Z 16010101000001.0Z
Attribute 33) uid:00728
Attribute 34) textEncodedORAddress:c=US;a= ;p=dcorporate;o=Exchange;s=00728;
Attribute 35) mail:00728@dcorporate.com
Attribute 36) msExchALObjectVersion:53
Attribute 37) msExchPoliciesIncluded:{0CE3CC4B-8E7E-4E0E-85EA-4EFDACE073FF},{26491CFC-9E50-4857-861B-0CB8DF22B5D7}

Add error on entry starting on line 19: No Such Attribute

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.

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.

• This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
  By continuing to use this site, you are consenting to our use of cookies.