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
Error:
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=0x80004005,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 0x80004005 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.”

Cause:
There could be the following reasons for such erroneous situation:
A) The 'DomainName\Exchange Servers' group is not assigned the 'Manage auditing and security log' user right.
B) The EDB database file is damaged.

Resolution:
To overcome the problem, you can perform either of the following methods:
A) 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.
B) Add the Exchange Servers group to the "Manage auditing and security log" policy: To do this, you should perform the following steps:
   i)    Click Start | Administrative Tools | Domain Controller Security Policy.
  ii)    Click 'User Rights Assignment' in the Default Domain Controller Security Settings Microsoft Management Console (MMC) snap-in.
 iii)    Double-click 'Manage auditing and security log'.
  iv)   Click 'Add User or Group' in the 'Manage auditing and security log Properties' dialog box.
   v)   Enter 'DomainName\Exchange Servers' in the 'User and groups names' box.
  vi)   Click OK two times.
 vii)   Quit Default Domain Controller Security Settings MMC snap-in.
viii)    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.

Solving Jet Error - "JET_errRecordNotFound,the key was not found" in Exchange Server

When EDB file get corrupted, you can't mount the Exchange database and also unable to access your emails & other items from Exchange server. These situations may occur due to various reasons like suddenly exiting the Exchange Server,corruption in the database header, virus infections and hardware related issues etc.

Such problems can be handled by using in-built eseutil.exe utility. However when edb file is badly corrupted, you may receive Error "JET_errRecordNotFound". In this case the inbuilt utility may fails to perform the expected tasks which makes the database inaccessible and leads to data loss.

In order to solve this problem you need to install the latest service pack of the MS Exchange server. If it does not resolves the issue then it is necessary to use the third-party Exchange Recovery software such as Stellar Phoenix Mailbox Exchange Recovery tool to repair and restore the damaged exchange database (EDB) files.

Download the most trusted free EDB repair Software for MS Exchange Server 5.5, 2000, 2003, 2007 and 2010 from http://exchange.stellarservertools.com/

EDB Recovery to Fix Transport Database Corruption

Are you facing fatal errors while accessing your Microsoft Exchange Server 2007 database? Is your EDB (Exchange Server Database) file is inaccessible? The fatal error in Exchange server aborts the application and thus makes it unusable. This behavior of MS Exchange Server renders all your valuable data inaccessible and cause critical data loss situations. In order to get your precious data recovered in such situations, you need to repair and restore the damaged EDB file, using an EDB Recovery solutions.

As an example, MS Exchange Server 2007 Management Pack for Operations Manager supervises the MS Windows Application Event log on systems, which are running MS Exchange Server 2007 and returns the below event:

“Product Name: Exchange
Product Version: 8.0 (Exchange Server 2007)
Event ID: 17003
Event Source: MSExchangeTransport
Alert Type: Critical Error
Description: A Transport database operation has encountered a fatal error. The database may be corrupted. The Microsoft Exchange Transport service is shutting down. Manual database recovery or repair may be required.”

After the above error, Microsoft Exchange Server does not let you access your database. At this point, you have to verify the cause of this problem and perform EDB File Recovery by resolving it.

Cause:

The error message below indicates that specified ESE (Extensible Storage Engine) database is damaged. It is preventing MS Exchange Server services from starting.

- ESE, also called JET Blue, is an ISAM (Indexed Sequential Access Method) data storage technology intended by Microsoft. The ESE is particularly used as a key component of the Microsoft Exchange Server and the Active Directory.

How to Fix ESE Corruption:

You can carry out following things to sort out this issue-

1. 
   
   Delete the defined database and corresponding transaction logs. You must not remove the database if you have significant data in the database.
2. 
   
   Repair the damaged database using Isinteg.exe tool or restore it from backup.

However, if none of the above methods helps you to work around the problem, EDB Recovery Tool is the only option to go for. They carry out in-depth scan of entire EDB file using high-end scanning techniques and restore all database objects such as emails, notes, contacts, tasks, and more.

The software enable you to recover corrupt EDB file in a quick and easy way as they are incorporated with simple and self-descriptive graphical user interface. The integrity of your database is always preserved by these tools.

EDB Recovery Software is the most preferred recover EDB solution to repair and restore EDB files in all cases of corruption. The EDB Recovery is designed for Microsoft Exchange Server 2007, 2003, 2000, and 5.5.

Checksum Errors on Exchange Server Database Pages

A corrupted or damaged Exchange Server database exhibits abrupt behavior while normal database operations. However, you can deduce the root cause of the issue and sometimes, solution to the problem by application log entries. You should restore the corrupted database from the last backup, if is available and valid. In case of database issues, you are recommended to use EDB Recovery Software to recover the damaged database.
For example, consider you use Exchange Server 2003 or Exchange Server 2000. You use Exchange online backup to backup your Information Store database and fail to do so. When you view the application log in Event Viewer, you encounter the below error message:

“Information Store (2240) The database page read from the file "E:\program files\exchsrvr\mdbdata\priv1.edb" at offset 204275712 (0x000000000c2d0000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 303571876 (0x121823a4) and the actual checksum was 303571940 (0x121823e4). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup.” 

This error is logged with event ID 474.

Cause

Error 1018 indicates JET_errReadVerifyFailure error. It results because of checksum errors on database pages. The prominent reason for this error to occur is Exchange database corruption due to file system errors. If the disk subsystem is suffering from issues, like defective disk drivers, faulty controller or outdated or incompatible firmware, this could result into Exchange database corruption.  

Solution

You can solve these problems by these methods:

1.Try to perform backup using different storage group located on a different server disk. 2.Diagnose and troubleshoot your Exchange Server running system for possible hardware issues 
3.Update your system with the latest firmware and drivers updates available 
4.If a clean data backup is available, restore your database 
5.Perform hard repair of the database using Eseutil /p in case no suitable backup is present 6.Eseutil /p is a destructive repair operation that could delete the corrupted database pages. To prevent the consequences, you should use safe EDB Recovery utilities. 

EDB Recovery Software are powerful tools to examine, repair and restore damaged Exchange databases using efficient scanning algorithms. These tools provide you graphically rich user interface and advanced features that result complete database repair.


Stellar Phoenix Mailbox Exchange Recovery is a fully-competent EDB Recovery Software to systematically repair damaged Exchange databases created with Exchange Server 5.5, 2000 and 2003. It provides safe EDB Repair and extracts all user mailboxes by converting them into Outlook usable .pst files. The tool can recover all email messages, notes, journals, tasks and other objects.

Checksum Errors on Exchange Server Database Pages

A corrupted or damaged Exchange Server database exhibits abrupt behavior while normal database operations. However, you can deduce the root cause of the issue and sometimes, solution to the problem by application log entries. You should restore the corrupted database from the last backup, if is available and valid. In case of database issues, you are recommended to use EDB Recovery Software to repair the damaged database.

For example, consider you use Exchange Server 2003 or Exchange Server 2000. You use Exchange online backup to backup your Information Store database and fail to do so. When you view the application log in Event Viewer, you encounter the below error message:  

“Information Store (2240) The database page read from the file "E:\program files\exchsrvr\mdbdata\priv1.edb" at offset 204275712 (0x000000000c2d0000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 303571876 (0x121823a4) and the actual checksum was 303571940 (0x121823e4). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup.”

This error is logged with event ID 474.  

Cause

Error 1018 indicates JET_errReadVerifyFailure error.

It results because of checksum errors on database pages. The prominent reason for this error to occur is Exchange database corruption due to file system errors. If the disk subsystem is suffering from issues, like defective disk drivers, faulty controller or outdated or incompatible firmware, this could result into Exchange database corruption.  

Solution

You can solve these problems by these methods:
1.Try to perform backup using different storage group located on a different server disk.
2.Diagnose and troubleshoot your Exchange Server running system for possible hardware issues
3.Update your system with the latest firmware and drivers updates available
4.If a clean data backup is available, restore your database
5.Perform hard repair of the database using Eseutil /p in case no suitable backup is present
6.Eseutil /p is a destructive repair operation that could delete the corrupted database pages.

To prevent the consequences, you should use safe EDB Recovery utilities. EDB Recovery Software are powerful tools to examine, repair and restore damaged Exchange databases using efficient scanning algorithms. These tools provide you graphically rich user interface and advanced features that result complete database repair.

Stellar Phoenix Mailbox Exchange Recovery is a fully-competent EDB Recovery Tool to systematically repair damaged Exchange databases created with Exchange Server 5.5, 2000 and 2003. It provides safe EDB Repair and extracts all user mailboxes by converting them into Outlook usable .pst files. The tool can recover all email messages, notes, journals, tasks and other objects.