How to recover EDB database in MS Exchange Server 2010 when you are unable to mount database

Are you facing some sort of problem while trying to access MS Exchange database folder? Such problem can occur if there are some problems with the configuration in Exchange Server settings. You should try to address the settings. If the problem is not resolved, then there is a quite prominent possibility that the EDB (Exchange Database) database file is damaged, which can happen due to various reasons including virus infections, database header corruption, transaction log file corruption, etc. In such cases, appropriate methods should be used to recover corrupt EDB file. If these methods are insufficient, then the use of a third-party EDB recovery software to perform EDB recovery is a must.

Let us discuss a scenario in which you are unable to mount the mailbox database in MS Exchange Server 2010. In such case, the following error message is displayed:

“Failed to mount database ‘Mailbox Database’

Mailbox Database


Exchange is unable to mount the database that you specified. Specified database: d1cdba46-6f79-46f2-ba14-3ae2fa8aad43; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0×80004005,ec=-2147467259).”

In addition, the following report is logged in the Application event log:

“Event ID 9518

Event Type:     Error

Event Source:  MSExchangeIS

Event Category:         General

Event ID:        9518

Date:   date

Time:   time

User:   N/A

Computer:       ServerName

Description: Error 0×80004005 starting Storage Group /DC=com/DC=example/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=335A1087-5131-4D45-BE3E-3C6C7F76F5EC/CN=Administrative Groups/CN=Exchange Administrative Group (FYDIBOHF23SPDLT)/CN=Servers/CN=ServerName/CN=InformationStore/CN=First Storage Group on the Microsoft Exchange Information Store.

MDB failed to start.”


There could be the following reasons for such erroneous situation:

  • The ‘DomainName\Exchange Servers’ group is not assigned the ‘Manage auditing and security log’ user right.
  • The EDB database file is damaged.


To overcome the problem, you can perform either of the following methods:

  • Run Setup /PrepareAD: You should run the ‘Setup /PrepareAD‘ command using the Exchange Server CD. This command restores the original configuration settings of Exchange Server.
  • Add the Exchange Servers group to the “Manage auditing and security log” policy: To do this, you should perform the following steps:

◦         Click Start | Administrative Tools | Domain Controller Security Policy.

◦         Click ‘User Rights Assignment’ in the Default Domain Controller Security Settings Microsoft Management Console (MMC) snap-in.

◦         Double-click ‘Manage auditing and security log’.

◦         Click ‘Add User or Group’ in the ‘Manage auditing and security log Properties’ dialog box.

◦         Enter ‘DomainName\Exchange Servers’ in the ‘User and groups names’ box.

◦         Click OK two times.

◦         Quit Default Domain Controller Security Settings MMC snap-in.

◦         Restart the Microsoft Exchange Information Store service.

If the problem is persisting, then a third-party EDB recovery software is to be used to recover corrupt EDB file. Such EDB recovery tools use fast and sophisticated scanning algorithms to recover EDB file without causing any damage to the original EDB file.

The EDB recovery tool that most of the recovery experts recommend is Stellar Phoenix Exchange Server recovery, which recovers corrupt EDB file created for MS Exchange Server 5.5, 2000, 2003, 2007, and 2010. Well equipped to extract individual PST files for every user mailbox, this EDB recovery software is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

Using EDB recovery software to recover EDB file in MS Exchange Server 2000

Are you getting random error messages while trying to mount Exchange folders? If yes, then there is a prominent probability that the EDB database file is damaged due to any miscellaneous reason. Such corruption can lead to severe damages as important data of several users becomes insecure, which a very undesirable proposition. In such cases, you should use a third-party EDB recovery tool to recover corrupt EDB file if the traditional ways to fix the file fail to do so.

Let us take an instance in which you are unable to mount on an MS Exchange Server 2000 database. The following error message is displayed:

“The database files in this storage are inconsistent

Id no: c1041739”

In addition, the following error is logged in the Application event log for MS Exchange Server 2000:

Event Type: Error

Event Source: ESE98

Event Category: Logging/Recovery

Event ID: 465

Date: Date

Time: Time

User: N/A

Computer: Computer_Name

Description: Information Store (2224) C:\Program Files\Exchsrvr\mdbdata\E00.log. Corruption was detected during soft recovery in logfile 4092:203. The failing checksum record is located at position 4117. Data not matching the log-file fill pattern first appeared in sector %6. This logfile has been damaged and is unusable.”


The root cause of this problem is that either the public store database or the mailbox store database is in an inconsistent state.


To resolve the situations, you should either restore or repair the corrupt EDB file. This could be done using the following methods:

  1. Restore the backup: Restoring the backup can be done by performing the following steps:
    1. Move or rename the E00.log file. By default, it is stored in the Drive:\Program Files\Exchsrvr\MDBDATA folder.
    2. Restore the storage group and the log files from the backup file.
    3. Mount the database when the storage group is restored.
  2. Repair EDB database file: To repair the EDB database file, you need to perform the following steps:
    1. Click Start | Run, and enter ‘cmd’ in the ‘Open’ box.
    2. Press the ‘Enter’ key to open Command Prompt.
    3. Move to the Drive:\Program Files\Exchsrvr\Bin folder.
    4. Type the following command and press the ‘Enter’ key:
    5. eseutil /p “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”

    6. Type the following command and press the ‘Enter’ key to defragment and rebuild the EDB database file:
    7. eseutil /d /t:x “drive:\program files\exchsrvr\mdbdata\database_file_name.edb

    8. Verify the state of the database by using the following command:
    9. eseutil /mh “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”

    10. If the database is consistent, then the following text is displayed:
    11. State: Clean Shutdown

    12. Use the ‘isinteg’ tool with the following switches to repair the logical corruption:
    13. Isinteg –s exchange_server_name –fix –test alltests

    14. Mount the database and check if the error is appearing again or not.

If the problem is still there, then you need to use a third-party EDB recovery software to recover EDB database file. The use of extremely safe scanning algorithms in a highly interactive user interface are some of the striking features of these EDB recovery tools.

Stellar Phoenix Exchange Server Recovery is one the best EDB recovery software that works well on Windows 7, Vista, Server 2003, XP, and 2000. With the ability to recover corrupt EDB files created for MS Exchange 5.5, 2000, 2003, and 2007, this EDB recovery utility extracts distinct PSTs from various user mailboxes.

Download the Most trusted free EDB Recovery Software to recover corrupt EDB file !

download edb recovery

‘1067 The information store terminated abnormally’ error while mounting Exchange Server 2000 and 2003

Microsoft Exchange Server maintains an .edb file which stores all user mailboxes. This .edb file when goes corrupt can give a real headache to server administrators. The reasons behind corruption include abrupt system shutdown, operating system malfunction, hardware failure, power fluctuations and others. As a result, the users are not able to send or receive e-mails. Each and every task related to Exchange server comes to a halt due to server downtime. Since such situations pose a great threat to valuable data, it becomes important to take appropriate steps. Being an administrator, you must opt for an efficient EDB recovery application.

Consider a scenario, wherein, you may come across the following error with your Microsoft Exchange 2000 or 2003 server computer:

The information store won’t start and you may receive the following error:

‘1067 The information store terminated abnormally’

When you go for online defragmentation, the following event is generated in the application log:

Date:      date        Source:   ESE
Time:      time        Category: Database Corruption
Type:      Error       Event ID: 447
User:      N/A
Computer:  Servername

Information Store (nnnn) A bad page link (error -338) has been detected in a
B-Tree (ObjectId: 70950, PgnoRoot: 157120) of database e:\Program
Files\excshsrvr\mdbdata\priv1.edb (157120 => 296404, 296403).

In case of Event ID: 447, you are not able to mount the information store and the crucial .edb files goes inaccessible. To troubleshoot the problem, you must have a thorough understanding of the exact causes. Then only, you can decide upon relevant Recover EDB steps.

The Even ID 447 clearly indicates that the logical structure of the database has become corrupt. The reasons behind corruption could be:

1. The server suffered a crash as disk caching has not committed transactions to the hard disk
2. During a database restoration, incorrect log files were replayed
3. Or if a server has a defective hard disk controller

Also, as seen in the application log, a bad page link error means logical corruption at the Jet level in the database.

In order to troubleshoot the problem, you must consider the following steps:

1.If possible, restore the database using a backup which was created before this error
2.If no backup exists, perform hard repair by using eseutil.exe / p command.
3.After the hard repair, perform an offline defragmentation by running the eseutil.exe / d command
4.Finally run, the isinteg -s servername -fix -test alltests command on the database
5.If you are still not able to mount the database, then grab a third-party EDB recovery software

Such applications, being read-only are absolutely safe to use and perform EDB file recovery in a hassle-free manner.

Stellar Phoenix Mailbox Exchange Recovery is an advanced software which repairs corrupt edb files and recovers mailboxes as separate PSTs which can be directly imported in Outlook. Compatible with Exchange Server 5.5, 2000, 2003, and 2007, the Exchange recovery software also performs recovery of deleted mailboxes.

Recovering corrupted EDB file due to virus infections in Exchange Server 2007

Microsoft Exchange Server is an exchange server that is server-side of the client-server product. It stores all the information of emails, contacts, calendar entries in an EDB (Exchange Information Store Database) file. In addition, you can access Exchange Server using Windows-based mobile devices as well. Sometimes, you are unable to mount the Exchange Server because of EDB file corruption. The reasons that lead to EDB corruption are human errors, database header corruption, virus infections, oversized EDB file. In such cases, you should try to find the cause of corruption and perform appropriate operations to repair corrupt EDB file. If you are unable to do this, then you should use a third-party EDB recovery software to recover EDB file.

Consider a scenario wherein you are unable to mount the Exchange Store in Exchange Server 2007. An error message is displayed, that is:

“An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both.
ID no: c1041724
Exchange System Manager”

In addition, if you check the Application log you may find the following error entry:

“Event Type: Error
Event Source: Antivirus_Program_Name
Event Category: None
Event ID: 5
Description: The description for Event ID ( 5 ) in Source ( Antivirus_Program_Name ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Virus Found! Virus name: W32.Netsky.P@mm!enc in File: E:\Program Files\Exchsrvr\Mailroot\vsi 1\Queue\NTFS_216f566e01c43c76000002af.EML by: Realtime Protection scan. Action: Clean failed : Quarantine failed : Access denied.”


One possible cause of this problematic situation is that an antivirus is deleting or quarantining the existing Exchange log file.


To resolve this error, you should perform the following steps:

1. Check the antivirus configurations: You should check whether the antivirus is configured to scan the Exchange Server directories.
2. Review the log files: You should check whether the log files were deleted or quarantined by the antivirus.
3. Recover the log file: You should attempt to recover the log file.

The problem will be resolved using aforementioned steps and you would be able to mount the database. However, if you are not able to address the situation then you should use a third-party EDB recovery software to do so. Such read-only tools recover EDB files using fast yet sophisticated scanning algorithms.

Stellar Phoenix Mailbox Exchange Recovery is an Exchange recovery software that repairs corrupt EDB file by converting it into different PST files. It is designed to support EDB file recovery for MS Exchange Server 2007, 2003, 2000, and 5.5. This EDB recovery tool is compatible with Windows 7, Vista, Server 2003, XP, and 2000.