Microsoft Exchange Recovery Tool

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.

Microsoft Exchange Server offers multilingual environment support to its users. You can easily access of your emails, contacts, tasks and other items in any language, which is included in its database. Every language in Microsoft Exchange Server has a unique Locale ID (LCID). This is quite helpful feature to provide access of Exchange Server in native language. But in some situations, this might might prove harmful and cause database index corruption. The situation might occur due to a number of reasons and eventually cause critical database corruption and data loss situations. Such cases require Exchange Server Recovery to be sorted out.

In a practical scenario of index and Exchange Server database corruption, when you move the Exchange Server 2000 database to a server, which does not have same LCID and then you attempt to defragment the database, index corruption is reported. However, when load correct Local ID on new server and then attempt to defragment Exchange Server database, it doesn’t corruption the index corruption.

• The LCID is a 32-bit value, which is defined by Microsoft Windows operation system that has a sort ID, language ID and reserved bits to identify the particular language. For instance, the Locate ID for English is 1033.

In these situations of index corruption, you can not access data from the Exchange Server database as the database become inaccessible or corrupt. Thus, it becomes essential to find out the cause of this issue and go for Microsoft Exchange Recovery by resolving it.

Grounds of the issue

When you move the database between computers where LCID is different, there is possibility of silent index corruption. For instance:

1. If an LCID, which is reinstalled that was previously uninstalled (or vice versa), there is the possibility of index corruption.

2. When you backup and restore database, which is generated by the computer that has LCID installed to a system without LCID installed, you might come across index corruption.

3. If you copy a database to another computer, defragment it and then copy back to original system, silent index corruption occurs.

Resolution

In order to retrieve data from damaged Exchange Server database, go for Exchange Server Recovery using third party applications. These tools use high-end scanning techniques to methodically scan the affected database and retrieve data from it. The Exchange Server Repair applications are complete safe and easy to use.

Stellar Phoenix Mailbox Exchange Recovery is the best ever made and the most advanced Exchange Server Software to ensure absolute recovery. It works well with Microsoft Exchange Server 2003, 2000 and 5.5. This software is compatible with Microsoft Windows 2003, XP and 2000.

Viruses have become very big threats to our precious and mission critical files, applications, system software and Exchange Server database. In case of Exchange Server database, when the virus infected mail spreads to user’s mailbox, it might damage whole mailbox or sometimes entire Exchange Server Database (EDB file). In these circumstances, all of the valuable data stored in the EDB file becomes inaccessible and results into data loss. At this point, to retrieve your precious and critical data, you need to go for Exchange Recovery solution using appropriate tools.

The recovery process in such cases may include deletion of the emails from all the mailboxes on Exchange Server. For this purpose, you could use ExMerge.exe (Exchange Mailbox Merge) application that is included Exchange Server CD.

The exchange Server database administrators generally use ExMerge.exe utility for backing up the mailbox data or to migrate the mailbox from one mailbox to another. The ExMerge tool is designed for copying mailbox data in the PST (Personal Storage File), which you can import to another mailbox. The ExMerge can also be used to extract particular messages from the mailbox store to the PST file and then remove PST files instead of importing the file in new mailbox store.

You can extract data from virus-infected Exchange Server mailbox using the ExMerge tool and carry out Exchange Repair by following the underwritten steps:

1. Setup ExMerge tool and start ExMerge wizard.

2. On Procedure Selection page, select Extract or Import and click Next.

3. On Two Step Procedure page, select Step 1 and Next.

4. On Source Server page, select Options and then User messages and folders on Data tab in Data Selection Criteria page.

5. In backs up the emails in the form of PST file and allow you to easily import them to mailboxes.

Although, this method works in a number of situations, but can not help you to retrieve data from damaged EDB file in all situations of corruption. In such cases, you need to use advanced and powerful third party Exchange Server Recovery applications to effective repair and restore corrupt EDB file and extract all of the data from it.

These applications use efficient scanning mechanisms to thoroughly scan whole database and retrieve as much data as possible from it. These tools come equipped with interactive and simple graphical user interface and thus let you carry out Exchange Server Recovery on your own.

Stellar Phoenix Mailbox Exchange Recovery is the most effective and successful Exchange Server Recovery tool to easily handle most of the EDB corruption scenarios with Microsoft Exchange Server 2003, 2000 and 5.5. This software is designed for Microsoft Windows 2003, XP and 2000.

OWA (Outlook Web Access), also known as EWC (Exchange Web Connect) is a remote webmail service of Microsoft Exchange Server5.0 and older versions. The interface of Outlook Web Access corresponds interface in MS Outlook. In OWA you can access all of your Outlook data from any remote system using web browser without configuring any profile on it. But in some situations, when you attempt to access emails using OWA, the process may not complete due to corruption to the Exchange Server database (EDB file). It results into critical data loss situations and require Exchange Server Recovery to be resolved.

In a practical scenario, when you attempt to access data from Exchange Server either using OWA or Microsoft Outlook, you might come across the below given error message:
“HTTP 500 – Internal Server error.”

At the same time, the following Event is logged into the Application Even Log of Microsoft Exchange Server:
Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: General
Event ID: 2050
Date: Date
Time: Time
User: N/A
Computer: Computer_Name
Description: Process Process_Name (PID=Process_ID). The shared memory heap could not be created.
After this behavior of Microsoft Exchange Server, the entire database become inaccessible and you come across critical dataloss situations. In such cases, you need to find out the cause of this issue and carry out Exchange Server Repair by sorting out this issue.

Root of the issue

You might come across this problem when  the ExchangeApplicationPool property has wrong values or  Exchange Server Virtual Directory is not running in correct identity.

Resolution

In order to sort out this issue, you need to ensure that the Exchange, the Exadmin, the Exchweb\Bin, the Exchweb, the Exchweb\Bin\Auth, the Public Virtual Directories, and the Microsoft Server ActiveSync are running in Microsoft Exchange Application Pool and not in the Default Application Pool. In case of corruption to the Exchange Server Database, you are required to carry out Exchange Server Recovery.

This is best possible with the help of third party applications. These tools are capable of scanning damaged EDB file and extracting all of its objects. They use advanced scanning algorithms to achieve absolute and quick Exchange Server Repair.

With self-descriptive and interactive user interface, these programs are quite easy to use and thus do not demand sound and prior technical skills.

Stellar Phoenix Mailbox Exchange Recovery is the most effective Microsoft Exchange Recovery solution to easily handle most of the EDB corruption scenarios. It works well with Microsoft Exchange Server 2003, 2000 and 5.5. This software is designed for Microsoft Windows 2003, XP and 2000. With read-only conduct, it always performs safe recovery.

In Microsoft Exchange Server, the Esefile is an inbuilt utility that is used to copy files and test checksum. Different switches are used to perform specific task using this tool. This utility can be used on Microsoft Exchange Server 2000 and 5.5. In some situations, this utility may cause checksum errors and database corruption if you use incorrect switches. In such cases, all of your critical data becomes inaccessible and serious data loss situations occur. At this point, to retrieve your valuable data, you are required to opt for Exchange Server Recovery.

The command line format of Esefile tool is as follows:

Esefile [/c source destination] [/x file] [/s file] [/d file page number]

/c Copy source files to destination
/x Test Edb.dll format checksum
/s Test Ese.dll format checksum
/d Dumps a page from file

When you test checksum using this tool, it verifies page-level integrity of the database. It tests at speed of about 1 GB per minute.

In case if you use /s switch on EDB format database and /x switch on ESE format database by mistake, checksum error is logged on every page. The utility may report that the database has incorrect checksum and possibly the database corruption may occur.

After testing checksum using incorrect switches with Esefile utility, when you attempt to start Information Store of Microsoft Exchange Server, it might not start and the following error messages is logged in Application Event Log:

Event ID 5000 Source MSExchangeIS
Unable to initialize the Microsoft Exchange Information Store service.
Error Non-database files or corrupted database.

At this point, you are required to resolve the database corruption as quickly as possible by carrying out Exchange Repair.

How to fix checksum errors in Exchange Server?

In order to sort out the above error and gain access of your database, you need to repair and restore the damaged database. This is best possible with the help of powerful and advanced Exchange Recovery software.

These programs are particularly designed to systematically scan entire Exchange Server database, repair and restore it. Advanced and effective scanning methods are used by these Exchange Server Recovery applications to achieve absolute recovery. With interactive and simple graphical user interface, these tools are completely easy to use.

Stellar Phoenix Mailbox Exchange Recovery is the most excellent solution to effectively handle EDB file corruption situations. It is designed for Microsoft Windows 2003, XP and 2000. This Exchange Server Software repairs and restores EDB file of Exchange Server 2003, 2000 and 5.5. This is a non-destructive recovery tool.

After you restore an Exchange Server database from one server to another, you might experience serious issues. When you attempt to mount the database in such situations, “c1041724” error occurs. In such situations, all of the critical data becomes inaccessible and serious data loss situations occur. At this point, you are required to go for Exchange Recovery to repair and restore the damaged database and access data from it.

After replacing the Exchange Server database, when you attempt to mount the newly configured server, you might find the following entries in Application Event Log:

Event Type: Error

Event Source: MSExchangeSA

Event Category: MAPI Session

Event ID: 9175

Date:  7/14/2007

Time:  10:50:04 PM

User:  N/A

Computer: EXCHANGE

Description:

The MAPI call ‘OpenMsgStore’ failed with the following error:

The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.

The MAPI provider failed.

Microsoft Exchange Server Information Store

ID no: 8004011d-0526-00000000

Such behavior of Microsoft Exchange Server renders all of your mission critical data inaccessible and you need to find out the cause of the issue to perform Exchange Repair by sorting it out.

Grounds of the issue

This issue generally occurs due to corruption to the Exchange Server database. Due to corruption, the Exchange Server database becomes inconsistent and thus it can not be mounted.

Resolution

Before mounting the database, check “Do not mount the database” and then attempt to start Information Store Service. Rename the old database folder and then run Eseutil on affected database. Now try to mount the database.

This method works in a number of cases, but sometimes when you try this solution, following error may occur in Event Log:

Event Type: Error

Event Source: ESE

Event Category: Logging/Recovery

Event ID: 619

Date:  7/14/2007

Time:  10:50:23 PM

User:  N/A

Computer: EXCHANGE

Description:

Information Store (3552) First Storage Group: Attempted to attach database ‘C: \Program Files\Exchsrvr\mdbdata\pub1.edb’ but it is a database restored from a backup set on which hard recovery was not started or did not complete successfully.

In such cases, the data can not be retrieved and you need to use Exchange Recovery software. These software uses effective scanning mechanisms to retrieve as much data as possible from the affected database. These applications are completely easy and safe to use.

Stellar Phoenix Mailbox Exchange Recovery is the most advanced and easy to use Exchange Recovery tool that handles most of the EDB corruption situations. It works well with Exchange Server 6.0, 5.5, 5.01 and 5.0. This software is compatible with Microsoft Windows 2003, XP and 2000.