MS Exchange Repair Tool

An Exchange Server database can get corrupt for several reasons, the most common being ‘Dirty Shutdown’. This leads page-level, ESE-level, or application-level corruption. Many times corruption remains undetected during normal database operations and is reflected when the user tries to backup the database. In such situations, the user needs to apply Exchange Repair methods to extract the data.

For instance, consider a situation when an Exchange Server administrator, runs a backup program to take backup of a storage group. The backup task fails and the below error message pops up:

 “Error, Unable to open \ because it is currently being backed up by another process.”

The error statement further suggests that database or database element is corrupt and does not let you backup the storage group.

Cause

The error indicates that Exchange storage group is in use by some other application or process. This can occur due to one of the following reasons:

1. Another backup program is simultaneously trying to backup the Exchange Information store. Since the database file(s) are open, the backup application take them as corrupted.

2. An antivirus application has been configured that is scanning the Exchange database files

3. You are using a backup utility that is not Exchange-aware

4. The Exchange database is corrupt and backup utility cannot read it

Solution

Following are the corresponding solutions that can help you recover from such problems:

1. Deselect the Exchange Server components, that are to be backed up by another backup utility running on the computer

2. Disable the antivirus program to scan Exchange Server files

3. Try using a different, Exchange-aware utility

4. Restore the problem Exchange database using the last available backup or repair it using Eseutil commands.

Running Eseutil commands for corrupted Exchange database is not safe as the resultant database can be out of some important data. For safe MS Exchange Repair, it is however, recommended to use a commercial application. These Exchange Repair software can scan and restore the affected database without harming the original integrity of database.

Exchange Server Repair Tool is an advanced EDB Repair utility that repairs corrupted Exchange databases and restores the mailboxes in separate *.pst files. The MS Exchange Repair tool supports Exchange Server 2007, 2003, 2000, and 5.5. With deleted mailbox feature, the tool can also recover the STM file data in the body of an e-mail message.

One of the most important objects of Microsoft Exchange that saves all the database files and transaction logs is ‘Information Store’. This component, once corrupted, results in inaccessibility of all the data/information saved in database. Few most common reasons for the information store corruption are improper database shutdown, log file damage, and anti-virus scanning. An easy way to access the information store after its corruption is by using a complete backup. However, if the backup is unavailable or corrupted, then you need to search for an effective third-party Exchange Server Repair software.

As a practical case, you receive the underneath error messages while trying take a backup of your database files, using Veritas software:

 “Information Store - is a corrupt file. This file cannot verify.”

On viewing the event log of your Exchange Server, you view the below error message:

“Source : ESE
Category : Database Page Cache
Event Id : 474
Description :
Information Store (2712) First Storage Group: The database page read from the file “E:\Exchange\mdbdata\priv1.edb” at offset 409464832 (0×000000001867f000) (database page 99966 (0×1867E)) for 4096 (0×00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 3567500155055337822 (0×31824e7d5639715e) and the actual checksum
was 3711585678364162506 (0×338233827852b9ca). The read operation will fail with error -1018 (0xfffffc06). If this condition persists then please restore the database from a previous backup. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance
diagnosing the problem.”

Resolution:

For complete resolution of the above error message and to access data, follow the below mentioned steps:

• Firstly, take a copy of your raw database and run ‘eseutil /p’ to perform repair.

• Now, take a backup of your repaired database and run ‘eseutil /d’ to defragment your database.

• Next, take a backup of your defragmented database and run ‘Isinteg -fix -test alltests’ to check the integrity.

• In case, you do not receive any error integrity checking, then run ntbackup on exchange server.

• Lastly, try complete backup information store using the Veritas software.

However, if the information store remains corrupted even after following the above steps and you are still not above to perform database backup, then you need to repair the information store by using an effective Exchange Server Repair. An Exchange Server Repair software incorporates high-end scanning methods to repair corrupt Exchange EDB file.

Exchange Repair Software is an efficient Exchange Repair application that repairs corrupt Exchange EDB file(s) created with Exchange Server 5.5, 2000, 2003, and 2007. With recovery of deleted mailboxes, the read-only software saves repaired files in a .PST file format.

New Microsoft Exchange Server Resources:

Exchange 2007 Recovery: Exchange 2007 Recovery software recovers e-mails and other related items from the corrupted or damaged EDB and STM database of MS Exchange Server and restores mailboxes in distinct *.pst files.

Exchange 2003 Recovery: Exchange 2003 Recovery tool is an advanced Exchange database recovery utility and can recover all of the objects of EDB file in each and every case of corruption.

Exchange Mailbox Recovery: Exchange Mailbox Recovery software repairs corrupt .edb and .stm files of MS Exchange Server and recover user mailboxes with their respective emails and related items.

Exchange Database Recovery: Exchange Database Recovery software is designed and developed to recover emails from corrupted or damaged database files of MS Exchange Server.This tool restores individual mailboxes in Outlook-usable PST files.

Exchange User Profile Recovery: Recover Exchange User Profile with this amazing Exchange Recovery software

Information Store is one ost vital components of Microsoft Exchange Server that stores transaction logs and database files. Unlike any other database corruption, Information Store databases can also get corrupted due to dirty database shutdown, anti-virus scanning, and log file corruption. In most of these situations, you encounter an error message that suggests database corruption. To easily overcome such database corruption scenarios, you need to restore the data from an online backup. But in case of online backup unavailability, you will need to opt for advanced Exchange Server Repair solutions.

To illustrate the above case, consider a scenario where you attempt to take a backup from Veritas software and you encounter the below error message:

 “Access Denied to Database Mailbox Store (Server Name) - Warning mailbox Store (Server Name) is a corrupt file. This file cannot verify”

After the above error message pops up, the database backup process stops. On viewing the application error log, you view event id 217. The description section for the same event is mentioned underneath:

 “Information Store (2320) 8d59bacd-96a8-4d3a-b1cd-0f31dc7be0b8: Error (-613)
during backup of a database (file D:\ProgramFiles\Exchsrvr\mdbdata\priv1.stm). The database will be unable to restore. Information Store (3272) The streaming page read from the file “D:\ProgramFiles\Exchsrvr\mdbdata\priv1.stm” at offset 5598494720 (0×000000014db24000) for 4096 (0×00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 3969232578 (0xec95aec2) and the actual checksum was 4119053255 (0xf583c3c7). The read operation will fail with error -613 (0xfffffd9b). If this condition persists then please restore the database from a previous backup.”

Cause:

The fundamental cause for the above error message is corruption of database.

Resolution:

To resolve the above error message, you need to:

1. Restore the data from an updated backup, as suggested in the error log.

2. Run Eseutil/d (offline defragmentation) to resolve minor corruptions in Microsoft Exchange database.

3. Run Eseutil /p and then run Isinteg -fix to fix corruption on a database backup.

However, if the problem still persists, then you need to go for an advanced Exchange Repair to extract user mailboxes from the corrupted database. Such Exchange Server Repair solutions can be easily downloaded from the Internet and used even by a novice user.

Stellar Phoenix Mailbox Exchange Recovery is a advanced repair application that repairs corrupt Exchange EDB file, irrespective of its cause of corruption. The repaired mailboxes can be saved in separate *.pst files. With recovery of deleted mailboxes, the Exchange Repair software supports Exchange Server 5.5, 2000, 2003, and 2007.

Exchange Information Store service is the most critical component, without which the server is of no use. The Information Store is comprised of different storage groups and if these groups go corrupted, it results into data inaccessibility. Further, the Information Store service also stops. In critical situations, when you cannot restore from the backup or repair it using standard utilities, an Exchange Server Repair tool is required to be used.

For example, when using Exchange Server, you might observe one or more of the following symptoms:

• You attempt to start Information Store service, but cannot do so with the following error:

“Windows could not start the microsoft exchange information store on local computer.”

• When you try to start the Exchange event service, this also fails and the following error occurs:

 “Could not start the microsoft exchange event service on local computer.
Error 1068:The dependency service or group failed to start.”

• On viewing the event viewer, you see event IDs 7001 and/or 7024 logging that suggest that Information Store service has failed to start or has terminated

Cause

The general reasons of Information Store not starting are:

• Permission issues related to file system, registry etc.

• The message store or log files could not find the required disk space

• Corrupt message store

Event 7024 generally occurs when the Exchange computer account doesn’t has sufficient rights to access the Information Store. This can also occur if Exchange Enterprise Servers group that root from the parent domain doesn’t consist the required Exchange Domain Servers group from child domain.

Solution

In order to solve the above problem, you need solutions such as:

• Check for sufficient permissions required to access the file system, registry and other components

• Check for required disk space for log files and message store

• Run setup.exe /domainprep for Information Store permission related issues

• Add the required group to the Exchange Enterprise Servers group in the parent domain

• Repair the corrupted message store using eseutil /r and/or eseutil /p command or restore from backup

Backup is the safest option to restore the database as the eseutil utilities can cause irrecoverable data loss. However, if backup is absent, you are suggested to use an Exchange Repair utility. The EDB Repair tools use powerful and safe scanning algorithms to repair and restore the corrupted Exchange database.

Exchange Repair Software is an advanced and safe tool that repairs Exchange databases and extracts the mailboxes as *.pst files. The Exchange Repair tool supports Exchange Server 5.5, 2000, 2003, and 2007. The software is applicable in each instance of database corruption and provides an interactive design and look .

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 Exchange Server 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.

When you perform operations like an online backup or defragmentation, the system reads each database page for writing or other processes. To do so, it first undergoes checksum test and check if it is correct. For any reason, if the page checksum mismatch with that has been calculated by database engine, it reports an error and the operation is halted. Such errors usually root from physical database corruption and compel you to restore the database from backup or apply some Exchange Repair measures to fix database corruption.

As an example of such problems, with Exchange Server 2007, you might exhibit the following symptoms:

1. The client computer cannot start Microsoft Outlook

2. Users fail to send/receive e-mails

3. Online backups and defragmentation fail with a -1018 checksum mismatch error

4. The application event log in Exchange Server reports an error as below:

 “Database recovery and restore failed with an unexpected error.”

Cause

The above symptoms suggest that Exchange Server has failed to read database page due to checksum mismatch and the page is corrupt. However, the same issues can also occur due to firmware malfunction or problem in RAM. For the specific reason, you are suggested to view error code that is listed in the event description.

Solution

You need to apply these measures to solve the given problem:

1. If the error listed in event description is -515, the transaction log file(s) might be missing. Determine the missing logs and move them back to the log directory and/or restore the database from backup.

2. Check the system for hardware issues and solve them or migrate to a different hardware

3. Consider upgrading the BIOS and firmware

4. Perform Exchange Server Repair with eseutil /P command, followed by eseutil /D and isinteg -fix. Make sure you backup the database first as running this repair can cause important database pages to delete.

For safer MS Exchange Repair, consider using solutions like an Exchange Server recovery software. These commercial applications are built with advanced technology to run effective scan for a corrupted database and extract the valuable data out of it.

Exchange Repair Software is a professional utility that repairs corrupted Exchange Server databases. The Exchange Server Repair tool recovers all the mailboxes in individual *.pst files and also allows to select them as required. The tool supports Exchange Server 5.5, 2000, 2003, and 2007. The software can also recover deleted mailboxes.

Stellar Information Systems Limited, 22-Jan-2010, Gurgaon, the pioneer data recovery company providing advanced EDB recovery solutions and services, today announced the launch of a new, updated version of its Exchange server repair solution- Stellar Phoenix Mailbox Exchange Recovery v3.0. With various end-user innovations, the upgraded Version 3.0 now repairs MS Exchange Server 2007 databases and also provides full native support for repairing Unicode EDB files. This release introduces a new deleted mailbox recovery feature and added capabilities that reduce costs and enhance the overall user experience.

Stellar Phoenix Mailbox Exchange Recovery v3.0 recovers STM data in e-mail body itself, which is a considerable improvement over its previous releases that used to recover it as an e-mail attachment. Also, the exchange recovery software now allows users to manually select the root Exchange Server version at ‘Select EDB File’ dialog-box with the added ‘Select Server Type’ option. The free demo version of the exchange server recovery product is available for download from company’s website that lists the mailbox(es) it can recover.

“Stellar Phoenix Mailbox Exchange Recovery v3.0 is the unified package that delivers full versions’ compatibility, accidental deleted mailbox recovery, and multilingual data recovery support . Together with several conforming features, the update helps administrators to achieve long-term database control.”said Sunil Chandna, CEO of Stellar Information Systems Limited. “This release provides organizations a way to lessen the operational losses while Exchange database corruption. With several reworked features, Exchange Recovery v3.0 is designed as a cost-effective and time-saving solution”

New Features of Mailbox Exchange Server Recovery v3.0:

1. Supports MS Exchange Server 2007

2. Recovers deleted mailboxes

3. Supports Unicode-formatted EDB files

4. Recovers STM data as e-mail body for Exchange Server 2003, 2000, and 5.5

5. Allows to select Exchange Server type- a new ‘Select Server Type’ option

Pricing

Stellar Phoenix Mailbox Exchange Recovery v3.0 is an affordable Exchange Repair solution, available in three different license options- Administrator, Technician, and Academic. The product range starts at $499 for Academic License.

Stellar Information Systems

Stellar Information Systems Limited is industry’s leader in providing data recovery software, e-mail recovery tools, database repair solutions, file repair utilities, data safety products, and data recovery services. Certified with ISO 9001:2000 standard, Stellar has more than 1,100, 000 satisfied customers worldwide.

Contact Information

For more information and product purchase options:

Call : +1-866-554-2512 (TOLL FREE)
Mailto: orders[at]stellarinfo.com.
Web Address- http://www.ms-exchange-server-repair.com/

For the reason that Microsoft Exchange Server mainly acts as a mailbox server, backing up the database regularly is the key to deal with disaster recovery needs. Microsoft recommends using an Exchange-aware backup utility such as Windows Server 2003 backup or any third-party application. These utilities require access of .pat file (discussed in ’cause’ section) and Exchange Server to be free from any hardware-related errors to successfully backup the database. At times, these hardware-related concerns also bring corruption to the database, which makes it obligatory either to restore from the last backup or perform Exchange Server Repair to repair EDB file of MS Exchange Server.

To apprehend such situations better, consider a scenario when you try to perform an Exchange-aware backup of the Exchange database. But due to some causes, the operation fails and you get an error message mentioned below:

“An error occurred during backup of an Exchange store database - the cause and resolution for the online backup failure depends on the error listed in the Description of the event.”

This error is generated by ESE (Extensible Storage Engine) and is associated with event ID 217. The error statement further mentions another error in its description section that actually determines the root cause of failure.

Cause

General reasons causing the above behavior to occur are:

• ESE cannot access the database .pat file exclusively. Exchange Server uses this file while backup is running to keep a record of updated pages, separately for both private and public stores. This is the patch file that ensures backing up of pages modified while backup is running.

• If the description section of error reports -1018 error, this might be because of some hardware-related issues.

• In case of description section mentioning -613 error, the cause could be checksum error in .stm (SLV) file. Another possibility is some hardware-related concerns.

Solution

You need to apply these measures to solve the described problem:

• Another program might be accessing the .pat file, so either stop the software or wait till it finishes.

• In case of -1018 error, find and solve the issue behind and restore the database from the last online backup if available. If you are using Enterprise edition, you can also use Exmerge. In other cases, you can perform EDB Repair using eseutil /p, followed by isinteg -fix commands, but the data loss is likely.

• Follow the same steps as for -1018 error in case of -613 error. You need to repair .stm file along with the associated .edb file.

Since eseutil /p causes database pages to delete, it is more suggested to opt for third-party Exchange Server Repair utilities.

MS Exchange Repair Software is an advanced and reliable tool that repairs Exchange databases and restores the mailboxes as *.pst file. The Exchange Repair tool supports MS Exchange Server 5.5, 2000, and 2003. The software is valid to use in each instance of database corruption with an interactive design and look .

Laptop Memory

A dirty shutdown in Microsoft Exchange Server generally leaves your Information Store in inconsistent state. This occurs when the Information Store(s) have not been closed properly, generally because of power outage or power surges. In most of such cases, you cannot mount the EDB databases. The dirty shutdown doesn’t always indicate the database corruption, but the fact that the database files have not been detached from the log files’ stream in a proper fashion. The automatic recovery procedure starts the next time when you start the Exchange Server. But if the procedure fails, you need to recover the database files manually. This can be done either by using Exchange Server built-in repair utilities or with the aid of Exchange Repair tools.

For example, consider a situation when you experience dirty shutdown with your Exchange Server. The next time when you start the server, it displays the following error:

“JET_errDatabaseCorruptedNoRepair -1224”

The database might be inaccessible.

Cause

The error indicates that the database is corrupted but for some reasons, repair is not allowed.

Solution

You can try implementing the following measures to solve the given problem:

1. Check if an online backup is available that can be used to restore the database.

2. If no backup is present, you can repair the database manually using eseutil tool as follows:

a) Run eseutil /mh command to check the database file header

b) If the above command reports ‘Dirty Shutdown’ state, make sure that all the present transaction log files from the checkpoint forward are present. If not, you can run eseutil /p, command to make the database consistent.

c) After this, you should run eseutil /d command to defragment the database. This discards and later rebuilds the indexes and space of the Exchange databases.

Running eseutil /p command can cause catastrophic data loss, so you are suggested to opt for safer database recovery solutions. There are several EDB Repair Software available that use effective and safe scanning algorithms to analyze and repair corrupted Exchange databases. The MS Exchange Repair applications are easy to install and use with no prior requirement of having any technical knowledge.

This Exchange Repair Software is a powerful and user-friendly tool that repairs corrupted Exchange Server databases and extracts the mailboxes in individual *.pst files. The Exchange Server Repair Software supports MS Exchange Server 5.5, 2000, and 2003. It is a feature-rich utility that is compatible with Windows 7, Vista, XP, 2003, and 2000.

Microsoft Exchange Server database engine splits a column into several parts, when it finds it too large and thus, the Long-values (LVs) are created. These structures are stored in a different B-Tree (binary tree) of the associated table, each with a unique long-value ID. Each of these LVs has a specific header, called LVROOT, consisting of information, like reference count and length of LV. In some cases, this LVROOT can get overwritten (usually because of a defective B-split operation), which eventually results into corruption of LV. This can cause Information Store to stop, errors accessing LV and/or database corruption. To repair the database, you should restore from a suitable backup. If no valid backup is present, you need to apply an Exchange Server Repair solution.

To illustrate such problems, suppose you attempt to perform offline defragmentation of an Exchange database. But the operation fails with an error message as below:

“Operation terminated with error -1526 (JET_errLVCorrupted, Corruption encountered in long-value tree) after <n> seconds”

Further, when you execute eseutil /g command to check the integrity of the database, it reports the database as corrupted.

Cause

The above error occurs due to corruption in LV tree. This can exist in conjunction with orphaned LVs.

Solution

You should first check for the backup. If present and valid, restore from it. In other case, you need to implement the given sequence of steps to solve this issue:

1. Run eseutil /g with /v and /x parameters for detailed output and examine it for the cause (error, orphaned or corrupted)
2. If the LVs are corrupted, you can run eseutil /p command. But make sure you backup the database first as this causes corrupted data to delete
3. If the LVs are corrupted and orphaned both, you should execute eseutil /d to perform database defragmentation after the repair.

Eseutil /p is a hard command. So, for safe EDB Repair, you need to use a third-party database repair tool. An MS Exchange Repair Software uses intensive, yet safe, scanning algorithms to repair and restore a corrupted Exchange database, while providing an interactive user interface.

Stellar Phoenix Mailbox Exchange Recovery is an effective solution that repairs a corrupted Exchange database and restores it to a user-specified location. The safe Exchange Repair solution extracts all user mailboxes as individual .pst files. The tool supports Exchange Server 5.5, 2000, and 2003. It is compatible with Windows 7, Vista, XP, 2003, and 2000.

Ost to Pst  Recover Outlook

Exchange Server mailbox store is composed of user mailboxes and system mailboxes. Each mailbox store is made of two files : Priv.edb and Priv.stm. When a disaster occurs to any mailbox store, the EDB file is considered to be the most vital component of recovery, for the reason that it contains all email messages, headers and text attachments of users’ email messages. There are various Exchange Server Repair software available that can repair a corrupted Exchange database, in case when you don’t have any valid database backup to restore.

For instance, consider a scenario when you try to mount your Exchange Server mailbox store. The mount operation might fail logging the events 9175 and 455 in application event log.

Cause

There can several possible reasons that can cause the described issue:

1. An antivirus software is running that has deleted the Exchange log files

2. You have performed soft recovery for database using eseutil /r with incorrect logfile base name

3. Mailbox store is corrupted

Solution

To solve this issue, you need to try these fixes:

1. You should ensure that antivirus software doesn’t scan Exchange Server directories. It can even corrupt the database files. If the log files have been deleted, you should restore the database from backup and play through the log files. In case when no good backup is available, you need to run Exchange repair utilities for bringing the database to consistent state.

2. You need to perform soft recovery using correct log file base name, such as e00, e01, e02 or e03 .

3. If the entire mailbox store is corrupted, you should run Eseutil /r to repair it or restore from backup. However, you can also run Eseutil /p as hard recovery operation, but this causes the dirty pages to delete. So, it is recommended to use commercial Exchange Server Repair tools that can safely repair a corrupted Exchange database.

Exchange Repair software are powerful tools that use exclusive repair algorithms, while providing graphically rich user interface.

Stellar Phoenix Mailbox Exchange Recovery is a fully-featured and non-destructive tool to perform systematic repair of damaged Exchange databases created with Exchange Server 5.5, 2000 and 2003. It is a complete Exchange Repair tool that extracts all user mailboxes by converting them into individual Outlook usable .pst files. The tool can recover all email messages, notes, journals, tasks and other objects.

Microsoft Exchange Mailbox Merge tool or Exmerge.exe allows you to extract mailboxes’ data from an Exchange running computer and then merge it into same mailboxes stored on a different computer running Exchange Server. The tool copies the required data from the root server into .pst files and then merges it in the personal folders into mailboxes stored on the target server. At times, you cannot open the .pst files after using Exmerge.exe to extract the data to another Exchange Server database. This can occur due to incompatibility issues, new format of Outlook for PST, incorrect .pst file privileges or database corruption. As a result, the database becomes corrupt and you need Exchange Repair solution.

For example, when you try to run Exmerge.exe to move data from an Exchange Server computer to another, you may receive the below error for various users:

“Error configuring message service (MSPST MS) (MAPI_E_EXTENDED_ERROR) (CmapiSession::CreateEMSPSTProfile).

Error opening message store (MSEMS). Verify that the Microsoft Exchange Information Store service is running and that you have the correct permissions to log on. (0×8004011d).”

You cannot open the related .pst files.

Cause

The Exchange database is corrupted due to incomplete or improper merge operation. This can also occur due to insufficient .pst file permissions.

The database corruption can also result because of unexpected shutdown and virus issues.

Solution

You should make sure that you use the latest version of Exmerge utility and the .pst files are not marked as read-only. For removing the read-only attribute from .pst file, you need to click its Properties and clear the associated check box.

To restore the lost data for damaged database, you need to use your last backup. If this is absent or seems to be invalid, you need a third-party mailbox extraction tool. Termed as Exchange Repair software, these tools can repair and rebuild a corrupted Exchange database well while maintaining its integrity.

The Exchange Repair Software is highly competent to extract database mailboxes by using powerful scanning algorithms. Also, these tools are easy-to-use products with a graphically rich user interface.

Stellar Phoenix Mailbox Exchange Recovery is an advanced and non-destructive 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 comprehensive Exchange Server Repair solution with impressive set of features and options. The tool extracts user mailboxes in individual .pst file format files.

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.

Stellar Phoenix Mailbox Exchange Recovery 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 Repairutility with impressive set of features. The tool extracts user mailboxes in individual .pst file format files.

Circular logging is a Exchange Server feature that implements recycling of logs. Microsoft Exchange Server writes the data to be committed to the database in transaction logs before actually writing it. If circular logging is enabled and four logs have been filled, it assumes that the first log as committed and thus, recycles the logs in order to save disk space. But it comes with a major flaw that prevents disaster recovery. If the database is corrupted while the feature is enabled, Exchange can only restore as far as the last backup is available. In case a suitable backup is unavailable, you are suggested to opt for Exchange Repair solutions that are powerful and safe too at repairing a corrupted Exchange database.

For example, you observe an unexpected shutdown with an Exchange database. After this, when you try to start it, an ‘JET_errFileNotFound’ error is displayed with a numerical value, such as 4294965485, -1811 or 0xfffff8ed. When you view the application event log, it shows events 1120 and 5000.

Cause

Events 1120 and 5000 generally show database inconsistency that prevent the database to start. You should see their description for the exact reason.

One probable cause could be that circular logging is enabled and error lies in checkpoint file, usually Edb.chk file. Since the circular logging is enabled, Exchange deletes the log files immediately after writing the data to the database, for which the information is traced out by Edb.chk file. Now, if a process blocks the Edb.chk file for a considerable period of time and prevents Exchange to update it, the file may get deleted before it could be updated. Thus, the checkpoint gets lost if the database suffers an unexpected stop. When you restart the server, the Edb.chk file points to a log file that doesn’t exit anymore and hence, the database doesn’t start.

Solution

If the exact cause is known and the errors are occurring only because of Edb.chk file, delete it and database service. But if the cause is different, the database might get damaged.

To achieve recovery, you should not use eseutil /r command without /is or /ds switches. This is because at this point, a new Edb.log file can get created and Exchange may try to repair using incorrect set of log files. Though you can delete the Edb.chk file, but the database remains corrupted.

For getting successful results from a corrupted Exchange database, it is suggested to use Exchange Recovery products in case if no good backup is there. Exchange Server Repair tools are high-end and safe database repair utilities that can repair and restore a corrupted Exchange database.

Stellar Phoenix Mailbox Exchange Recovery is a fully-competent tool to perform systematic database repair of damaged Exchange files created with Exchange Server 5.5, 2000 and 2003. It is a reliable Exchange Server Repair tool that extracts all user mailboxes by converting them into individual Outlook usable .pst files. The tool can recover all email messages, notes, journals, tasks and other objects.

An Exchange Server Information Store might get corrupted due to several errors, including unexpected shutdown and network errors. Corruption might involve any database files, called .edb files, that reside in Exchsrvr\Mdbdata folder. While Information Store corruption, you might observe server behaving slowly, Information Store Service not starting or not stopping, email delivery issues and several errors showing that the database is inconsistent. You should use your backup to restore such corrupted database or run ESEUTIL utility to repair it. However, if none of the solutions works, you should use Exchange Repair Software that could repair and restore a damaged Exchange database.

For an instance, consider that you run ESEUTIL /D utility to defragment your database and the process fails. When you view the Windows NT Application log of Event Viewer, you come across the below error message:

“Operation terminated with error -327 (JET_errBadPageLink, Database corrupted) after <n> seconds.”

Additionally, you might also observe Exchange Server being slow or unresponsive while normal database operations.

Cause

Exchange Server ‘Bad Page Link’ errors generally indicate logical database corruption. If the internal database structure is not correct because of corrupted or misaligned pointers, you might receive such errors.

Solution

You should apply these measures to isolate the given problem:

• If available, use online backup to restore the damaged Exchange Server database

• Use Administrator tool ‘Move Mailbox’ in order to move users’ mailboxes from the affected Exchange Server to a healthy one

• Run ESEUTIL /P against the database while making sure that the database store is not mounted. Next, execute ESEUTIL /K to check the database for consistency

• If the problem persists, use a powerful Exchange Database Repair tool to efficiently repair the damaged database

Exchange Repair Tools are safe and comprehensive repair applications that can safely repair a logically crashed Exchange database. These tools employ high-end algorithms to examine the database and restore it at a safe location. The software provide you self-descriptive interface and hence you can use the tools without any prior technical understanding. Embedded with advanced options, the software serve as most suitable tools to repair the damaged database.

Stellar Phoenix Mailbox Exchange Recovery is a fully-competent Exchange Repair 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 is capable of recovering all email messages, notes, journals, tasks and other objects.