Wednesday, February 24, 2010

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.

Monday, February 15, 2010

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.

Exchange Database Corruption after Installing SP2

Microsoft Exchange Server 2003 SP2 offers new features, more reliability and easier administration over its earlier counterparts. SP2 is a cumulative update that improves the Exchange messaging environment by including improvements in mobile messaging, mailbox and protection against spam. Before you upgrade your servers to Exchange Server SP2, it is recommended that you make complete backup of system state, file system and most importantly, Exchange databases. This assures of data availability in case the installation goes wrong in any way. But cases occur when your Exchange databases get corrupt when no clean backup is present. In such situations, you should use a powerful Exchange Server Repair product that can use safe scanning algorithms to repair a corrupted Exchange database.  

For instance, you can consider a scenario describes below:

1. You run Exchange Server 2003 SP1 or an earlier version
2. You decide to upgrade to Exchange Server 2003 SP2. During the installation of SP2, the setup failed to stop ExIFS (Exchange Installable File System) service but continues with no notice
3. After this, when you try to mount Information Store, it fails and events 470, 9519, 9518 and 104 are logged in the application log.

Cause 

The above symtoms suggest that Exchange database may have got corrupted due to installation of SP2. It can also occur if an antivirus software is scanning the Exchange databases. Solution Before making any database restoration attempts, you should make sure that Exchange databases are excluded from any antivirus scanning.

If databases appear as corrupted, you should consider these suggestions:

1.Try repairing the corrupted database by running eseutil /r command

2. If it fails, restore the database from the last backup you have

3. When no clean backup is available, you should use a Exchange Repair software.

Exchange Server Repair products are highly competent utilities with powerful scanning algorithms to repair a corrupted Exchange database. These software are infallible solutions to any issue of database inconsistencies. Equipped with graphically rich interface and options, such software provide guide you through easy to implement procedure of repairing the database.

Exchange Repair is an advanced and safe Exchange Repair utility that employs powerful scanning algorithms to repair a damaged Exchange Server database. It is compatible with Exchange Server 5.5, 2000 and 2003. It is a safe Exchange Server Repair utility with impressive set of features. The tool extracts user mailboxes in individual .pst file format files.

Wednesday, February 3, 2010

How to Solve Table Index Corruption in Exchange Server?

The main repository of mailbox data in Exchange Server is the .edb file that is primarily composed of b-trees. Since a b-tree is allowed to have a considerable depth, b-trees deploy indexes to permit quick data access. In Exchange EDB, there are few ancillary trees that hold table indexes to work with the main tree. If these indexes go corrupted, the entire table and sometimes, the whole database become unusable. This is what we refer as logical database corruption. In critical situations, when this type of corruption is not limited to index page corruption, you need to implement Exchange Server Repair solutions.

To understand such potential problems with Exchange database further, consider the discussed scenario and error. When using Exchange Server 2007, you can encounter event 467 logging in the application log. Additionally, on viewing the description section of the same event, you receive an error that reads similar to below:

Information Store (number) Index [index name] of table [table name] is corrupted.

This error typically indicates a corrupted index in the Exchange store. As symptoms, you might observe access violations and repeated crashes. Also, this type of corruption might go undetected for long without any symptoms. Even the Exchange-aware backup may fail to detect this corruption. Event 467 suggests logical corruption at Database (JET database engine) level and is exhibited when JET engine touches this location in the database while reporting it as event 447. For specific root causes, one needs to view the application and system log cautiously as these errors can damage your data badly.

Solution

Following suggestions can help you isolate the depicted problem:

1. If corruption is limited to index leaf pages and not with the database pages, running Eseutil /d (offline defragmentation) alone can perform Exchange Server Repair.

2. In critical problems, you may need to use ExMerge utility to move the mailboxes to a new, blank Information Store.

3. The Exchange Server might be affected from page or database level corruption together with index page corruption. In such cases, you can execute Eseutil /p and then Isinteg -fix commands as Eseutil /d command may not work. You can further use ExMerge tool to put the database again in use.

4. To avoid data loss problems due to Eseutil /p utility, it is however, recommended to opt for a safe third-party Exchange Repair utility.


The Exchange Repair is a professional utility that repairs corrupted Exchange EDB file and restores the mailboxes in separate *.pst files. The EDB Repair product is easy to use with its self-explanatory interface. Designed for Exchange Server 5.5, 2000, 2003, and 2007, the tool is also competent to recover deleted mailboxes.