Microsoft Exchange Recovery Tool

Is your Microsoft Exchange Server’s Information Store damaged and does not start? Are you unable to retrieve information from EDB (Exchange Server Database) file? The information store corruption is due to numerous reasons, such as improper system shutdown, faulty hardware, virus infection, or application malfunction. In such situations, you need to opt for Exchange Server Recovery to access your database.

To recover Microsoft Windows Store that doesn’t start, use the below methods:

• Check Application Event Log of Windows NT Event Viewer for MSExchangePub, MSExchangePriv, EDB, and MSExchangeIS messages. The messages may provide you information about actual cause of the problem.
• Shut down all the MS exchange Server services, and then restart Exchange Server. When information store service restarts, it attempts to recover automatically and return database to consistent state.
• Create an absolute backup of Microsoft Exchange Server Information Store. It must include all the EDB and Log files.
• Restore database from last complete online backup. Make sure that you don’t click to choose ‘Start Service after Restore’ option. Restore incremental backups of Information Store. Only click selecting ‘Start Service after Restore’ option while restoring current incremental backup. Do not select ‘Erase all existing data’ option.
• If the above method can not help you start information store, check Event Log and review logged messages for EDB.
• If the above method doesn’t work, restore online backup of information store. Select ‘Start Service after Restore’ and ‘Erase all existing data’ options.
• Remove all the Log and EDB files from Mdbdata folder and then restore copies of Pub.edb and Priv.edb databases from backup.
• If none of the above methods work, you need to wipe the information store as last resort.
• If wiping does not work, you need to remove the Information store. However, it causes data loss. The easiest and safest way to retrieve data in such situations is Microsoft Exchange Recovery.

Recovery is possible using powerful and advanced third-party applications, known as Exchange Recovery Software. The applications are able to handle all EDB corruption situations, irrespective of the cause of corruption.

The Exchange Recovery Tool employ efficient database scanning techniques to methodically scan whole EDB file and extract damaged objects from it. With simple graphical user interface and read-only conduct, the applications are easy and totally safe to use.

Exchange Recovery software is the most advanced utility to recover your Exchange Server database from corruption. It works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. The software restores all EDB file objects such as emails, notes, contacts, tasks, appointments, attachments, and more.

Microsoft Exchange Server’s most fundamental component is transaction log, and Exchange Server writes all the transactions to these log files and applies these written changes to the database, when the system permits. On starting Exchange server, when the Information Store comes online, ESE checks the consistency of the database, and in case of detection of inconsistencies, ESE replays the transaction log files to locate those transactions that have not been applied to the database. In Exchange Server terminology, this process is termed as ‘Soft Recovery’. There can be many situations when a soft recovery is being done and database is damaged. To determine if this problem actually exists or not, you can view the application event log and perform Microsoft Exchange Recovery procedures accordingly.

As an instance of such Exchange Server problems, suppose you try to restore the Information Store database, but it cannot be completed. Additionally on viewing the application event log, you receive the following event ID:

Event Type: Information
Event Source: ESE
Event Category:
Event ID: 301
Date: date
Time: time
User: N/A
Computer: server_name
Description:
<process name> (<process id>) <number> The database engine has begun replaying logfile [path]\[logfile name].
For more information, click http://search.support.microsoft.com/search/?adv=1.

It can be observed with both, Exchange-aware restore and offline restore of Information Store database. This event ID suggests that Exchange Server database engine has started replaying the log files indicated by [path]\[logfile name], where ‘path’ is the full path and ‘logfile name’ is the name of logfile being replayed. Not always, but event 301 many a times indicates that the Exchange Server database is corrupt.

Resolving Event 301

Generally, you need not take any action to isolate the issue. But you should check the application event log to determine more issues that are possible when starting the database. Check the log report for damaged or missing log files, if any and hence know the root of failure.

If you find any event that indicates database corruption, the further attempts should be done to restore the database. You can either restore it from the last backup available or repair the database by Exchange repair utilities or use a third-party Exchange Recovery Tool.

A Microsoft Exchange Recovery software can scan a corrupted Exchange database and restore its contents at a safe location. With their interactive design, you can find these utilities easy to run and use.

Exchange Server Recovery software is a professional tool that can repair a corrupted Exchange Server database and restore individual mailboxes as PST files. This is an all-inclusive Exchange Recovery Tool that allows selective mailbox recovery along with deleted mailbox recovery. It supports MS Exchange Server 2007, 2003, 2000, and 5.5.

In Microsoft Exchange Server, you need to mount mailbox store for accessing stored mailboxes. After mounting the mailbox store, you can easily modify the mailbox and access its contents. However, under some circumstances, the mailbox store or public store refuses to mount. This behavior of Microsoft Exchange Server renders all your valuable data inaccessible and leads to critical data loss. To get your valuable data back, you need to opt for Exchange Recovery software, if the backup is not updated.

As a practical example of this problem, you may come across the below error message when you attempt to mount mailbox store or public store on Microsoft Exchange Server 2007, 2003, and 2000:

“ID no: c1041724
Exchange System Manager”

When you click Mailboxes or Logons under the Mailbox Store in the Exchange System Manager, you may receive further error message stating:

“ID no: 00000476-0000-00000000
ID no: c1050476
Exchange System Manager”

Furthermore, the events might be logged into Application Event Log with the following descriptions:

1. Information Store (1608) First Storage Group: An attempt to open the file “C:\Program Files\Exchsrvr\MDBDATA\priv1.edb” for read / write access failed with system error 5 (0×00000005): “Access is denied. “. The open file operation will fail with error -1032 (0xfffffbf8).
2. Information Store (5120) First Storage Group: An attempt to open the file “E:\EXCHSRVR\MDBDATA\priv1.edb” for read only access failed with system error 5 (0×00000005): “Access is denied.” The open file operation will fail with error -1032 (0xfffffbf8).

This behavior of Microsoft Exchange Server may occur if you do not have appropriate permissions to access the Mailbox Store. It can also be caused by damaged EDB (Exchange Database) file. In both the cases, you lose access of your mission critical data and need Exchange Server Recovery to sort out the problem.

Microsoft Exchange Recovery is best possible using powerful and advanced third-party utilities, known as Exchange Recovery Tool. The applications are capable of methodically scanning entire EDB file and extracting all the damaged mailboxes from it. They are totally.

Exchange Server Recovery software, with non-destructive nature and simple user interface, repairs and restores damaged EDB file in all cases of corruption. The software is safe and easy to use, and is designed for edb recovery from Microsoft Exchange Server 2007, 2003, 2000, and 5.5. It restores all the damaged objects of EDB file, such as emails, notes, tasks, contacts, attachments, and more.

Microsoft Exchange Server transaction log files are very crucial when it comes to working of the server. This application assigns and follows a particular sequence to name its log files. However, if the log file naming approaches 0xfffff, for instance Edbfffff.log, serious problems can occur. Information Store may stop working and database(s) may fail to mount. To prevent such events from occurring, you should reset the naming sequence periodically, otherwise you will have to use Exchange Server Recovery tools.

For better understanding of the subject, consider, you as an Exchange Server administrator, are not aware of the fact that resetting the log sequence is necessary, and, you suddenly observe that the Information Store has stopped functioning or is not working correctly for no apparent reason. Additionally, when you view the application log, you receive the below mentioned log:

Event ID: 125
Event Source: ESE97
Event Type: Error
Description:
MSExchangeIS () Unable to create the log. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -519.

Further, when you try to start the Information Store, the following event entry is received in the application log:

Event ID: 7024
Event Source: Service Control Manager
Event Type: Error
Description:
The Microsoft Exchange Information Store service terminated with service-specific error 4294966786.

Thus Information Store is not accessible by any means.

Cause

As mentioned earlier, the above behavior can result if the log file name sequence of Information Store transaction logs has reached the maximum value of Edbfffff.log.

Solution

You can implement any of the applicable methods to isolate the given issue:

1. Check for an offline backup. If present, use it to restore affected Information Store databases
2. If no suitable backup is available, perform hard repair on databases. For this, you need to run eseutil /p, eseutil /d, and isinteg utilities. But keep in mind to backup your database first, as hard repair can delete important pages from your databases.
3. Use a third-party Exchange Recovery Software to repair and restore corrupted Information Store databases. These Exchange Server Recovery software are more effective and safe than Exchange Server repair utilities.

Exchange Recovery Tool is a reliable utility that repairs corrupted Exchange Server databases and restores their mailboxes as PST files to a secure location, which is specified by the user. This Exchange Recovery software supports MS Exchange Server 2007, 2003, 2000, and 5.5.

Microsoft Exchange Server is a well-known application that is used to create collaborative messaging environment. It is installed on server and can be accessed from client computer using Microsoft Outlook. Exchange Server 2003 and Exchange Server 2000 use MS IIS (Microsoft Internet Information Services) to provide Exchange-related services. All configuration settings of the IIS are stored in IIS metabase. The formation of metabase contains various settings of properties of different nodes. However, in some situations the metabase may get damaged and cause critical EDB (Exchange Database) corruption scenarios. To sort out this problem, you need to opt for Exchange Server Recovery, in case of unavailability of backup.

Corruption of IIS metabase and Exchange Server database is a very serious concern. It can cause several Exchange Server vulnerabilities and make Exchange-related services unusable. In case of metabase corruption, you may encounter the below error message:

“[15:52:34] – The Internet Information Server metabase appears to be corrupt. Please uninstall and reinstall Internet Information Server. — ID:62145 –
[15:52:34] Prerequisites for Microsoft Exchange Messaging and Collaboration Services failed: The component ‘Microsoft Exchange Messaging and Collaboration Services’ cannot be assigned the action ‘Upgrade’ because:- The Internet Information Server metabase appears to be corrupt. Please uninstall and reinstall Internet Information Server.”

The above error, in particular, occurs due to missing metabase entries. If various users perform transactions after metabase corruption, the EDB file may encounter several inconsistency issues. In such situations, to bring your Exchange Server in working state, you need to fix this behavior using Microsoft Exchange Recovery Tool.

Resolution

You can use Adsutil.vbs, an inbuilt utility of Microsoft Exchange Server, to locate metabase objects. However, if you encounter the following error while using Adsutil.vbs tool, you have to reinstall Internet Information Service and Microsoft Exchange Server:

“-2147221020 (0×800401e4)
Error trying to enum the object (GetObject failed)”

Although, reinstalling the Exchange Server and IIS may fix this problem, but it can not repair the corrupted Exchange Server database. In order to repair and restore the damaged EDB file, you need to use third-party Exchange Recovery Software.

The applications are particularly designed to carry out systematic scan of entire EDB file (using advanced scanning mechanisms) and to extract all damaged and inaccessible objects. They enable you to perform Exchange Recovery on your own, as they have simple and self-descriptive graphical user interface.

Exchange Mailbox Recovery software repairs damaged EDB file and restores all user mailboxes as individual PST files. The Exchange Database Recovery software works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. It restores all EDB file objects, such as emails, notes, contacts, tasks, journals, appointments, and attachments.

An Exchange Server backup software issues a backup routine that calls the operating system to read 4 KB database pages (that are saved on the hard disk), and then to write data on the backup tape. This routine also includes a process to read the checksum value of each database page header, before writing data to tape. This checksum value is then compared with the corresponding value returned while reading the page. If for some reasons, like database corruption, these values do not match each other, Microsoft Jet Database Engine reports backup failure and prompts some error message. Such situations require that the administrator applies Exchange Server Recovery measures.

Such problems will be more clear with the further scenario. An Exchange administrator runs a backup process for its Exchange Server Information Store database. It observes that the backup could not be completed. Further, when it views the application log, it encounters the below error written in the description section of event logged:

“Information Store (3732) 23aca049-4dfa-4e45-b2f8-64c5414a947a: The backup has been stopped because it was halted by the client or the connection with the client failed.”

The associated event ID can be 215 or 447.

Cause

Some possible reasons for the above error to occur are:

• You have installed a third-party event sink that is incompatible or being problematic
• You are using a backup application that is incompatible or being problematic
• The hard disk or hard disk controller is faulty
• You are trying to backup a corrupted Exchange database

Solution

The suggested measures to solve the above problem are:

• Uninstall the third-party event sink.
• Try to use a different backup application, preferably suggested by Microsoft like, NTBackup or try to reinstall the existing backup program.
• Check the system log for probable hard disk and hard disk controller issues. Based on the issue, perform operations like repairing hard disk by running chkdsk and installing the recent driver and firmware updates.
• Repair the corrupted database using ‘Eseutil’ hard repair commands on a backup of database. If the resultant database has some important data missing, use a third-party, safe Exchange Recovery utility. A Microsoft Exchange Recovery software can scan and repair corrupted Exchange database using effective scanning algorithms.

Exchange Mailbox Recovery is a professional utility that repairs corrupted Exchange database and extracts the mailboxes as separate *.pst files. Incorporated with deleted mailbox recovery feature, this Microsoft Exchange Recovery utility supports MS Exchange Server 2007, 2003, 2000, and 5.5.

An Exchange Server database is susceptible to different corruption problems, such as dirty database shutdown, antivirus scanning, log file issues, and others. Thus an administrator might require different Microsoft Exchange Recovery tools to solve such problems and to continue working the e-mailing environment.

Further is a scenario that depicts a similar situation of Exchange Server database corruption. As an Exchange Server administrator, you may observe one or more of the below symptoms:

1. You cannot start and/or Information Store service
2. Exchange clients lose the ability to send or receive e-mails. You cannot solve this issue by restarting the server
3. You restore the database from an offline backup but the database is still inconsistent. On running Isinteg utility (database integrity check), it gives the below error message on screen:

“Error 4294966746: JET_errDatabaseInconsistent”

Cause

Information Store is corrupt. Either both or one of public store and private store is corrupted.

Solution

Before trying the below steps, you are recommended to take the backup of the entire Information Store to prevent any post-crash consequences. Use the below steps in order to solve the above problem:

1. Analyze all the error message and events of application event log that Exchange reports on attempting to start the Information Store

2. Run eseutil /mh command to check the integrity of Exchange databases (Priv.edb and Pub.edb). An inconsistent database shows ‘Dirty Shutdown’ state but is not always corrupt. This state can also occur if all the transaction logs have not been committed yet.

3. Replay all the transaction log by performing soft database recovery. For this, execute eseutil /r command for the affected database(s).

4. Run hard database repair in case soft recovery doesn’t work. Run eseutil/ p command and delete all the .chk and .log files

5. Check if the previously occurring symptoms go away. If you can successfully work with the database(s), they are repaired. Next, run eseutil /d and isinteg -pri -fix -test alltests commands in sequence to defragment and fix database issues respectively.

6. In case, the problem remains the same, use a third-party Exchange Server Recovery tool to diagnose and repair the database more effectively. A Microsoft Exchange Recovery utility uses safe, yet powerful, scanning procedures and allows for easy database repair.

Exchange Server Recovery Tool is a professional utility that repairs corrupted Exchange database and extracts the mailboxes in individual *.pst files for Exchange Server 2007, 2003, 2000, and 5.5. The tool provides advanced Exchange Server Recovery features and is easy to use. It can also recover deleted mailboxes and inaccessible STM data.

New Features of Exchange Server Recovery Software:

Exchange 2007 Recovery

Exchange 2003 Recovery

Exchange Server Information Store databases support transaction logging i.e. before committing any data to the database, it is first written to transaction logs. If your database is ever forced to perform recovery, these transaction logs replay and restore the database to a working state. When an Exchange Server Information Store database corrupts, it marks an event indicating the root cause of the issue. You can deduce the problem and thus, take corrective measures to solve it. In cases, when no backup is available to replace the damaged database and ESEUTIL utility also fails to repair, you need to use an effective Exchange Recovery Software that could repair and restore the damaged database.

For an instance, you might receive the below event ID in Application log of Event Viewer:

Date: date Source: ESE
Time: time Category: Logging/Recovery
Type: Error Event ID: 454
User: N/A
Computer: Servername
Description: Information Store (2184) Database recovery/restore failed with unexpected error -501

Cause

Event 454 generally indicates database corruption that occurs while restore or recovery operation. Error -501 corresponds to hexadecimal value 0xFFFFFE0B. It represents JET_errLogFileCorrupt error and shows that the recovery operation has failed because of log file corruption.

Solution

You need to solve the given issue by following these steps:

Check if all database files are consistent. If they are, you can move all corrupted log files that are contained in Exchsrvr\Mdbdata folder and then try to mount the Information Store
If applying the above step doesn’t solve the issue as databases are not consistent, you need to restore the corrupted databases from backup.
In case, no suitable backup is present, you can execute eseutil /p command to repair the damaged databases

If the error stil persists, use a powerful and safe third-party Exchange Recovery Tool to scan and repair the damaged database. Microsoft Exchange Recovery software are non-destructive tools designed with advanced technology to repair the corrupted database. These tools provide you self-explanatory interface and provide advanced set of features. In addition, you can use these products in any case of logical database corruption.

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

Exchange Server database failure or corruption is a very common situation, which could occur to any system at any point of time. In case of failure, a complete backup works as the best remedy to cure this problem. But in some situations, when you restore the Exchange Server Database (EDB) file from an online backup and try to mount database, the database could not be mounted and it remains in corrupted state. These situations might cause critical data loss situations and require Exchange Server Recovery to be sorted out.

In a practical scenario, after restoring Exchange Server database from the online backup, when you try to mount the Exchange Server database with the help of Exchange System Manager, you might come across the below given error message:

“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”

Along with above error message, you might also find the following events in the Application Even Log of Exchange Server:

Event Type:     Error

Event Source:        ESE98

Event Category:      Logging/Recovery

Event ID:    619

Description: Information Store (Information Store name) Attempted to attach database

'D:\Exchsrvr\MyStorageGroup\MyDatabase.edb' but it is a database

restored from a backup set on which hard recovery was not started

or did not complete successfully.

For more information, click http://search.support.microsoft.com/search/?adv=1. 

This behavior of Microsoft Exchange Server renders all of your mission critical data inaccessible and cause data loss issues. In such circumstances, it becomes essential to find out the cause of this problem and go for Exchange Server Repair by sorting it out.

Root of the issue

You might come across this situation, if any of the below situations are true:

1. The Exchange Server database has got damaged due to virus infection, file system consequences, improper system shutdown and other similar causes.

2. When you restored the backup, Last Backup Set check box wasn’t selected, thus hard drive wasn’t run.

Resolution

If the problem is due to incomplete hard drive, you must complete it. You can manually run the hard recovery with below command:

Eseutil /cc [path to directory containing Restore.env]

In case of database corruption, you are required to go for Exchange Server Recovery software to effectively scan the damaged EDB file and extract as much data as possible from it. The Exchange Server Repair software are quite safe and easy to use.

Stellar Phoenix Mailbox Exchange Recovery is the most advanced application to handle all sorts of EDB corruption situations. This software works well with Exchange Server 2003, 2000 and 5.5. It is compatible with Microsoft Windows 2003, XP and 2000.

Logical corruption in Microsoft Exchange Server database (EDB) is very problematic and quite difficult to identify and repair than physical damage. The administrators and users are generally unaware of logical corruption to EDB file. Microsoft Exchange Server does not include any inbuilt tool to diagnose and warn you about the logical database corruption. There are no specific symptoms to recognize such kind of corruption. In case of logical corruption, entire database becomes inaccessible and you come across critical data loss situations. In order to overcome logical database corruption, you are required to go for Exchange Recovery solutions.

In a practical scenario, when you attempt to access data from Microsoft Exchange Server, you might find the following entries in Application Event Log:

Event ID: 42
Source: EDB
Type: Warning
Category: General
Description: MSExchangeIS ((###)) The database engine found a bad page.

The above event shows that the inner structure of the database has got damaged, because the internal references (pointers) are misaligned or corrupted. The Exchange Server might become unusually unresponsive, sluggish or slow.

Cause

The logical corruption of Exchange Server Database might take place if you replay the wrong transaction log files, after restoring the database. The logical corruption is indicated by the “bad page link” or JET_errBadPageLink errors. In such cases, you need to go for Exchange Repair to get your valuable data back.

Resolution

In order to sort out this issue, go through the underwritten steps:

1. Restore Exchange Server database (EDB) from recent backup. It is important that only log file, which are restored from backup get replayed, not any existing log file that might available on Exchange Server hard drive.

2. Use exmerge.exe (Microsoft Exchange Mailbox Merge) tool to export data, then important into new priv.edb file.

3. Use “Move Mailbox” feature in Exchange Administrator program for moving users from damaged Exchange Server to another one. Recreate priv.edb file on original server and then move users back to original server.

When all else fails, repair and restore corrupted EDB file with the help of third party Exchange Recovery tools. These applications used advanced scanning mechanisms to methodically scan the entire EDB file and extract all of the user mailboxes from it. These programs are very easy to use and allow you to have Do It Yourself Exchange Repair.

Stellar Phoenix Mailbox Exchange Recovery is the most advanced and effective Exchange Server Software to retrieve data from EDB files of Exchange Server 2003, 2000 and 5.5. This software is designed to work with Microsoft Windows 2003, XP and 2000. With read-only and non-destructive conduct, this software is completely safe to use.