Upgraded Stellar Phoenix Exchange Server Recovery released with Quick and Extensive Scan features

Gurgaon, Haryana, <01-Feb-2011> Stellar Information Systems Ltd, the leading providers of data recovery software and services today releases the update version of the Stellar Phoenix Exchange Server Recovery v4.1. The new release of the software incorporates much advanced scanning mechanism that facilitates quick and easy repair of corrupt or damaged .edb file of Microsoft Exchange database.

With support to repair EDB files from MS Exchange 2010 the software also recovers all accidentally deleted mailboxes. The most helpful feature in the new launch is the option of ‘Quick Scan’ or ‘Extensive Scan’. The ‘Quick Scan’ feature runs a fast scanning method to quickly repair damaged EDB files in most of the scenarios of EDB corruption. However, ‘Extensive Scan’ is much helpful in case of severe damage of the EDB file. It usually takes a longer time, but produces far better recovery result.

“With the inclusion of the Quick and Extensive Scan mechanism, the recent upgrade launch of Stellar Phoenix Exchange Recovery 4.1 is targeted to offer a smooth EDB repair experience to both the general as well as technical users. It has been a need for long to ease both the users. We strongly believe that the recent launch of the Exchange Recovery software definitely meets the expectation in this regard.” said Sunil Chandna, CEO, Stellar Information Systems Ltd.

Key Features – Stellar Phoenix Mailbox Exchange Recovery 4.1

  • Repairs corrupt, damaged, or inaccessible EDB files in all cases of Exchange Database corruption
  • Repairs corrupt .edb files from MS Exchange 2010, 2007, 2003, 2000, and 5.5
  • Useful feature for Quick and Extensive Scan of the selected database
  • Recovers all the accidentally deleted mailboxes
  • Recovers Unicode-formatted EDB files
  • Enables selective recovery of mailboxes
  • Provides perfect solution to Convert edb to pst file
  • Compatible with Windows 2000 / XP / 2003 / Vista / Windows 7

Pricing And Availability

Stellar Phoenix Mailbox Exchange Recovery 4.1 is available in the Administrator, Technician and Academic Licenses. The software is available with a starting price of priced of $ 499 for the Academic license.

About Stellar Information:

Stellar Information Systems Limited (established since 1993) is the creators and providers of advanced data recovery software and data recovery services. Holding direct presence in the USA, Europe and Asia, Stellar is a name that is trusted for efficient solutions to recover lost, deleted, and inaccessible data.

Contact Information
For more information and product purchase options:

Voice : +1-877-778-6083 (TOLL FREE)
Mailto: orders@stellarinfo.com.
Web Address- http://www.stellarexchangeserverrecovery.com/

New version of Stellar Phoenix Mailbox Exchange Recovery now offers support for Exchange 2010

Stellar Information Systems Ltd,<01-09-10>Gurgaon, a leading name in data recovery industry, today declares the launch of Stellar Phoenix Mailbox Exchange Recovery 4.0, a more robust software which repairs corrupt EDB files of Microsoft Exchange Server 2010 in addition to 5.5, 2000, 2003 and 2007 versions.

Developed specifically to address the needs of affected MS Exchange Server administrators, this powerful Exchange recovery application offers to repair corrupt or inaccessible mailboxes and recovers them as individual PSTs. The newly-revived software now incorporates the capability of recovering selective mailboxes.

MS Exchange Server administrators can bank upon this application to derive accurate results in all failure scenarios including corrupt database header, improper database backups, hardware issues, dirty shutdown and others. The free Demo version of the EDB recovery software now has the provision of providing preview of the recoverable mailboxes.

“Version 4.0 of Stellar Phoenix Mailbox Exchange Recovery software comprises unparalleled recovery capabilities with added support for MS Exchange Server 2010. The Mailbox Exchange Recovery upgrade provides tremendous power in the hands of Exchange database administrators with its ability to recover mailboxes in almost all EDB database corruption instances, “ said Sunil Chandna, CEO, Stellar Information Systems Ltd.

“We are sure that the upgrade launch of the EDB recovery software will meet the growing needs and challenges that the MS Exchange database administrators are facing day to day” he concluded.

Key Features Stellar Phoenix MailBox Exchange Recovery 4.0

  • Supports Microsoft Exchange 2010, 2007, 2003, 2000 and 5.5
  • Repairs and recovers corrupt EDB databases
  • Allows selective recovery of mailboxes
  • Recovery of Unicode-formatted EDB files also supported
  • Recovers deleted mailboxes
  • User-friendly and safe application
  • Demo version provides preview of mailboxes
  • Compatible with Windows 2000/XP/2003/Vista/Windows 7

About Pricing and Availability

Stellar Phoenix Mailbox Exchange Recovery 4.0 is available in three license options including Administrator, Technician and Academic. The Administrator license is available both in CD+Download versions and is priced at $599 plus service and handling charges extra.

About Stellar Information

Stellar Information Systems Limited (established since 1993) is the leading creators and providers of advanced data recovery software and data recovery services for more than 17 years. Holding direct presence in USA, Europe and Asia, Stellar is a name that is trusted for finest solutions to recover lost and inaccessible data.

For more information on the product refer to the official website www.stellarinfo.com and the product micro-site www.ms-exchange-server-recovery.com.

Contact Information :
For more information and product purchase options:

Call : 1-877-778-6083 (TOLL FREE)
Mailto: orders@stellarinfo.com.
Web Address- http://www.stellarinfo.com

How to recover EDB database in MS Exchange Server 2010 when you are unable to mount database

Are you facing some sort of problem while trying to access MS Exchange database folder? Such problem can occur if there are some problems with the configuration in Exchange Server settings. You should try to address the settings. If the problem is not resolved, then there is a quite prominent possibility that the EDB (Exchange Database) database file is damaged, which can happen due to various reasons including virus infections, database header corruption, transaction log file corruption, etc. In such cases, appropriate methods should be used to recover corrupt EDB file. If these methods are insufficient, then the use of a third-party EDB recovery software to perform EDB recovery is a must.

Let us discuss a scenario in which you are unable to mount the mailbox database in MS Exchange Server 2010. In such case, the following error message is displayed:

“Failed to mount database ‘Mailbox Database’

Mailbox Database


Exchange is unable to mount the database that you specified. Specified database: d1cdba46-6f79-46f2-ba14-3ae2fa8aad43; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0×80004005,ec=-2147467259).”

In addition, the following report is logged in the Application event log:

“Event ID 9518

Event Type:     Error

Event Source:  MSExchangeIS

Event Category:         General

Event ID:        9518

Date:   date

Time:   time

User:   N/A

Computer:       ServerName

Description: Error 0×80004005 starting Storage Group /DC=com/DC=example/CN=Configuration/CN=Services/CN=Microsoft Exchange/CN=335A1087-5131-4D45-BE3E-3C6C7F76F5EC/CN=Administrative Groups/CN=Exchange Administrative Group (FYDIBOHF23SPDLT)/CN=Servers/CN=ServerName/CN=InformationStore/CN=First Storage Group on the Microsoft Exchange Information Store.

MDB failed to start.”


There could be the following reasons for such erroneous situation:

  • The ‘DomainName\Exchange Servers’ group is not assigned the ‘Manage auditing and security log’ user right.
  • The EDB database file is damaged.


To overcome the problem, you can perform either of the following methods:

  • Run Setup /PrepareAD: You should run the ‘Setup /PrepareAD‘ command using the Exchange Server CD. This command restores the original configuration settings of Exchange Server.
  • Add the Exchange Servers group to the “Manage auditing and security log” policy: To do this, you should perform the following steps:

◦         Click Start | Administrative Tools | Domain Controller Security Policy.

◦         Click ‘User Rights Assignment’ in the Default Domain Controller Security Settings Microsoft Management Console (MMC) snap-in.

◦         Double-click ‘Manage auditing and security log’.

◦         Click ‘Add User or Group’ in the ‘Manage auditing and security log Properties’ dialog box.

◦         Enter ‘DomainName\Exchange Servers’ in the ‘User and groups names’ box.

◦         Click OK two times.

◦         Quit Default Domain Controller Security Settings MMC snap-in.

◦         Restart the Microsoft Exchange Information Store service.

If the problem is persisting, then a third-party EDB recovery software is to be used to recover corrupt EDB file. Such EDB recovery tools use fast and sophisticated scanning algorithms to recover EDB file without causing any damage to the original EDB file.

The EDB recovery tool that most of the recovery experts recommend is Stellar Phoenix Exchange Server recovery, which recovers corrupt EDB file created for MS Exchange Server 5.5, 2000, 2003, 2007, and 2010. Well equipped to extract individual PST files for every user mailbox, this EDB recovery software is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

Using EDB recovery software to recover EDB file in MS Exchange Server 2000

Are you getting random error messages while trying to mount Exchange folders? If yes, then there is a prominent probability that the EDB database file is damaged due to any miscellaneous reason. Such corruption can lead to severe damages as important data of several users becomes insecure, which a very undesirable proposition. In such cases, you should use a third-party EDB recovery tool to recover corrupt EDB file if the traditional ways to fix the file fail to do so.

Let us take an instance in which you are unable to mount on an MS Exchange Server 2000 database. The following error message is displayed:

“The database files in this storage are inconsistent

Id no: c1041739”

In addition, the following error is logged in the Application event log for MS Exchange Server 2000:

Event Type: Error

Event Source: ESE98

Event Category: Logging/Recovery

Event ID: 465

Date: Date

Time: Time

User: N/A

Computer: Computer_Name

Description: Information Store (2224) C:\Program Files\Exchsrvr\mdbdata\E00.log. Corruption was detected during soft recovery in logfile 4092:203. The failing checksum record is located at position 4117. Data not matching the log-file fill pattern first appeared in sector %6. This logfile has been damaged and is unusable.”


The root cause of this problem is that either the public store database or the mailbox store database is in an inconsistent state.


To resolve the situations, you should either restore or repair the corrupt EDB file. This could be done using the following methods:

  1. Restore the backup: Restoring the backup can be done by performing the following steps:
    1. Move or rename the E00.log file. By default, it is stored in the Drive:\Program Files\Exchsrvr\MDBDATA folder.
    2. Restore the storage group and the log files from the backup file.
    3. Mount the database when the storage group is restored.
  2. Repair EDB database file: To repair the EDB database file, you need to perform the following steps:
    1. Click Start | Run, and enter ‘cmd’ in the ‘Open’ box.
    2. Press the ‘Enter’ key to open Command Prompt.
    3. Move to the Drive:\Program Files\Exchsrvr\Bin folder.
    4. Type the following command and press the ‘Enter’ key:
    5. eseutil /p “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”

    6. Type the following command and press the ‘Enter’ key to defragment and rebuild the EDB database file:
    7. eseutil /d /t:x “drive:\program files\exchsrvr\mdbdata\database_file_name.edb

    8. Verify the state of the database by using the following command:
    9. eseutil /mh “drive:\program files\exchsrvr\mdbdata\database_file_name.edb”

    10. If the database is consistent, then the following text is displayed:
    11. State: Clean Shutdown

    12. Use the ‘isinteg’ tool with the following switches to repair the logical corruption:
    13. Isinteg –s exchange_server_name –fix –test alltests

    14. Mount the database and check if the error is appearing again or not.

If the problem is still there, then you need to use a third-party EDB recovery software to recover EDB database file. The use of extremely safe scanning algorithms in a highly interactive user interface are some of the striking features of these EDB recovery tools.

Stellar Phoenix Exchange Server Recovery is one the best EDB recovery software that works well on Windows 7, Vista, Server 2003, XP, and 2000. With the ability to recover corrupt EDB files created for MS Exchange 5.5, 2000, 2003, and 2007, this EDB recovery utility extracts distinct PSTs from various user mailboxes.

Download the Most trusted free EDB Recovery Software to recover corrupt EDB file !

download edb recovery

‘1067 The information store terminated abnormally’ error while mounting Exchange Server 2000 and 2003

Microsoft Exchange Server maintains an .edb file which stores all user mailboxes. This .edb file when goes corrupt can give a real headache to server administrators. The reasons behind corruption include abrupt system shutdown, operating system malfunction, hardware failure, power fluctuations and others. As a result, the users are not able to send or receive e-mails. Each and every task related to Exchange server comes to a halt due to server downtime. Since such situations pose a great threat to valuable data, it becomes important to take appropriate steps. Being an administrator, you must opt for an efficient EDB recovery application.

Consider a scenario, wherein, you may come across the following error with your Microsoft Exchange 2000 or 2003 server computer:

The information store won’t start and you may receive the following error:

‘1067 The information store terminated abnormally’

When you go for online defragmentation, the following event is generated in the application log:

Date:      date        Source:   ESE
Time:      time        Category: Database Corruption
Type:      Error       Event ID: 447
User:      N/A
Computer:  Servername

Information Store (nnnn) A bad page link (error -338) has been detected in a
B-Tree (ObjectId: 70950, PgnoRoot: 157120) of database e:\Program
Files\excshsrvr\mdbdata\priv1.edb (157120 => 296404, 296403).

In case of Event ID: 447, you are not able to mount the information store and the crucial .edb files goes inaccessible. To troubleshoot the problem, you must have a thorough understanding of the exact causes. Then only, you can decide upon relevant Recover EDB steps.

The Even ID 447 clearly indicates that the logical structure of the database has become corrupt. The reasons behind corruption could be:

1. The server suffered a crash as disk caching has not committed transactions to the hard disk
2. During a database restoration, incorrect log files were replayed
3. Or if a server has a defective hard disk controller

Also, as seen in the application log, a bad page link error means logical corruption at the Jet level in the database.

In order to troubleshoot the problem, you must consider the following steps:

1.If possible, restore the database using a backup which was created before this error
2.If no backup exists, perform hard repair by using eseutil.exe / p command.
3.After the hard repair, perform an offline defragmentation by running the eseutil.exe / d command
4.Finally run, the isinteg -s servername -fix -test alltests command on the database
5.If you are still not able to mount the database, then grab a third-party EDB recovery software

Such applications, being read-only are absolutely safe to use and perform EDB file recovery in a hassle-free manner.

Stellar Phoenix Mailbox Exchange Recovery is an advanced software which repairs corrupt edb files and recovers mailboxes as separate PSTs which can be directly imported in Outlook. Compatible with Exchange Server 5.5, 2000, 2003, and 2007, the Exchange recovery software also performs recovery of deleted mailboxes.

Recovering corrupted EDB file due to virus infections in Exchange Server 2007

Microsoft Exchange Server is an exchange server that is server-side of the client-server product. It stores all the information of emails, contacts, calendar entries in an EDB (Exchange Information Store Database) file. In addition, you can access Exchange Server using Windows-based mobile devices as well. Sometimes, you are unable to mount the Exchange Server because of EDB file corruption. The reasons that lead to EDB corruption are human errors, database header corruption, virus infections, oversized EDB file. In such cases, you should try to find the cause of corruption and perform appropriate operations to repair corrupt EDB file. If you are unable to do this, then you should use a third-party EDB recovery software to recover EDB file.

Consider a scenario wherein you are unable to mount the Exchange Store in Exchange Server 2007. An error message is displayed, that is:

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

In addition, if you check the Application log you may find the following error entry:

“Event Type: Error
Event Source: Antivirus_Program_Name
Event Category: None
Event ID: 5
Description: The description for Event ID ( 5 ) in Source ( Antivirus_Program_Name ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Virus Found! Virus name: W32.Netsky.P@mm!enc in File: E:\Program Files\Exchsrvr\Mailroot\vsi 1\Queue\NTFS_216f566e01c43c76000002af.EML by: Realtime Protection scan. Action: Clean failed : Quarantine failed : Access denied.”


One possible cause of this problematic situation is that an antivirus is deleting or quarantining the existing Exchange log file.


To resolve this error, you should perform the following steps:

1. Check the antivirus configurations: You should check whether the antivirus is configured to scan the Exchange Server directories.
2. Review the log files: You should check whether the log files were deleted or quarantined by the antivirus.
3. Recover the log file: You should attempt to recover the log file.

The problem will be resolved using aforementioned steps and you would be able to mount the database. However, if you are not able to address the situation then you should use a third-party EDB recovery software to do so. Such read-only tools recover EDB files using fast yet sophisticated scanning algorithms.

Stellar Phoenix Mailbox Exchange Recovery is an Exchange recovery software that repairs corrupt EDB file by converting it into different PST files. It is designed to support EDB file recovery for MS Exchange Server 2007, 2003, 2000, and 5.5. This EDB recovery tool is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

Problems in Edb.chk File of Circular Logging Enabled EDB File Cause Corruption

Microsoft Exchange Server uses circular logging option for maintaining the database transaction. These log files are stored until data is actually written to EDB (Exchange Server Database file). This feature uses the log files for recovering the database transactions if Exchange Server is shut down improperly or in inconsistent state. However, in some situations, circular logging cannot help you to recover the database transactions after improper system shutdown and you come across serious database corruption circumstances. In such situations, EDB recovery software come for your help to extract corrupt data from the database.

In a practical scenario of this problem, Microsoft Exchange Server database, which circular logging enabled, may not start after an improper shut down. Furthermore, you may run across a JET_errFileNotFound error in one of the below given forms:

  • -1811
  • 0xfffff8ed
  • 4294965485

In the Exchange Server Application Event Log, events 5000 and 1120 are logged in hexadecimal version of this error. The events are generic Exchange Server database startup errors. You should interpret the error code in descriptions for understanding exact cause of the problem and then fix it through EDB recovery solutions.

Root of the problem

You may come across this behavior of Microsoft Exchange Server due to any of the below reasons:

  • There is some problem in the checkpoint file of Microsoft Exchange Server database. The file may get damaged due to unexpected shut down of Exchange Server computer.
  • Exchange Server removes transaction log files after the data is written to main database file, if the circular logging option is enabled.
  • Another database process is having an open Edb.chk file. It prevents MS Exchange Server from modifying checkpoint file when checkpoint advances.
  • The Exchange Server database is severely damaged.


Try out any of the Microsoft Exchange recovery methods to fix the problem:

  • Locate and remove Edb.chk file from your Exchange Server database. However, you should play safely while doing this.
  • If problem is caused due to critical Exchange Server database corruption, repair and restore the database using powerful third-party applications.

The EDB recovery tool are particularly designed to scan entire Exchange Server database, to recover edb and extract all inaccessible data from it. They are incorporated with rich and interactive graphical user interface to offer easy recovery.

Stellar Phoenix Mailbox Exchange Recovery is the most advanced EDB recovery solution to effectively fix all your database corruption issues. The Corrupt EDB File recovery software is designed to repair corrupt databases of Microsoft Exchange Server 2007, 2003, 2000, and 5.5. It restores all inaccessible items from EDB file, such as emails, notes, tasks, contacts, journal, and attachments.

Exchange Server Upgrade Fails with Error c106fdda

Microsoft Exchange Server version upgrade is the practice followed for keeping the server up-to-date, secure, and more reliable. The process involves upgrading Exchange Server databases, which includes the Priv.edb and Pub.edb- the essential data storage components of Exchange Server. If the upgrade process fails on any of these database files, then that database might be inconsistent. This usually occurs because of an ungraceful shutdown and requires specific EDB Recovery solutions.

Here is an example illustrating how an upgrade process can fail in MS Exchange Server. Let’s say, you try to upgrade to Exchange Server and the process fails. On each attempt of doing so, you receive the below mentioned error message:

An unexpected error has occurred.
ID No. c106fdda”

This error won’t allow you to upgrade Microsoft Exchange Server. However, if you apply a fault-tolerant setup, the given error pops up:

Your upgrade did not complete successfully. Please restart your Microsoft Exchange services and your system will behave as it did before the upgrade was attempted.”

Such problems specifically occur when Exchange Server setup during upgrade finds a database that is not consistent. Since an inconsistent database cannot be upgraded, the setup exits with a failure error message, as above.

User Action

If you encounter the problem that has been discussed above, you need to perform the below sequence of steps:

  • Quit the Exchange setup program

  • If you didn’t choose the fault-tolerant upgrade at start, you need to check the consistency of all databases using commands as follows:

drive:\Winnt\System32\eseutil /mh file_path\priv.edb

drive:\Winnt\System32\eseutil /mh file_path\pub.edb

However, in case the fault-tolerant upgrade was chosen. The following commands will help:

drive:\exchsrvr\bin\edbeutil /mh file_path\priv.edb
drive:\exchsrvr\bin\edbeutil /mh file_path\pub.edb

  • Execute the below mentioned command for the inconsistent database:

<drive>:\Winnt\System32\eseutil /r /ispriv

<drive>:\Winnt\System32\eseutil /r /ispub

If the database doesn’t become consistent again, you should restore it from the last available backup or run a third-party EDB Recovery Tool. An Corrupt EDB File recovery software can scan a corrupted Exchange database file and extract its data in readable form, accessible by normal means.

Stellar Phoenix Mailbox Exchange Recovery is a comprehensive recover edb solution designed for repairing a corrupted Exchange EDB file and restoring the mailboxes as *.pst files. This EDB Recovery Software supports MS Exchange Server 5.5, 2000, and 2003 and provides advanced options to aid recovery. In addition, it can also recover deleted mailboxes.

Resolving Event 1148 with Rule Synchronization Error

A storage group in Microsoft Exchange Server Information Store contains one or more mailbox stores, depending on the version of Exchange Server you use and requirements of the organization. Mailbox stores are the most critical components from data preservation perspectives as they comprise of system and user mailboxes. If corrupted, mailbox store causes serious problems in the working of an organization. A mailbox store is further comprised of two files, namely Priv1.edb and Priv1.stm. Corruption usually affects Priv1.edb file and occurs because of typical reasons like, database dirty shutdown, anti-virus software scan, virus infection, and network issues. When corrupted, EDB file on being accessed, prompts errors under a few event IDs, which can be read from application event log. Following is one such event IDs that generally occurs because of database corruption and requires EDB Recovery solutions.

Suppose you are an Exchange Server administrator with a mailbox store that contains hundreds of user mailboxes. Since the store contains critical information required for uninterrupted working of the organization, its consistency cannot be compromised. But you observe that the below mentioned event ID is repeatedly observed in application event log:

Event Type: Error

Event Source: MSExchangeIS Mailbox Store

Event Category: Rules

Event ID: 1148

Date: date

Time: time

User: N/A

Computer: Computer_Name


A rule synchronization error (Read verification error) has occurred.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

This error occurs irrespective of the fact that all Exchange Server services are working without any issue.


Exchange database is corrupt.

Note: The same error can also occur if required data is missing.


Following are the possible solutions that can help you recover from such database corruption issues:

  1. Run ‘Eseutil’ with ‘/r’ switch for soft database recovery

  2. Restore database from the last available backup

  3. Execute ‘Eseutil’ with ‘/p’ switch to repair the database. But make sure to backup the database before running this command. This prevents data loss.

  4. Use a third-party EDB Recovery Tool to repair and restore the corrupted Exchange database

EDB Recovery Software are exclusive tools built to scan and repair the damaged EDB database file safely and effectively. One of the best utilities is Stellar Phoenix Mailbox Exchange Recovery software with deleted mailbox recovery capability, this EDB Recovery Tool supports MS Exchange Server 2007, 2003, 2000, and 5.5 and can extract individual mailboxes as *.pst files.

Fixing “-1605 0xFFFFF9BB JET_errKeyDuplicate…” Exchange Server Error

Microsoft Exchange Server is a popular application for creating collaborative messaging environment. It is a server-side application of client-server environment. It stores all your valuable data, such as emails, notes, contacts, tasks, appointments etc., in EDB (Exchange Database) file. In some situations, the database gets damaged and you encounter Jet errors while accessing the database. This behavior of Exchange Server database leads to significant data loss and requires EDB Recovery Software to be sorted out.

The Jet errors generally occur when Exchange Server database gets damaged beyond repair capabilities of the Eseutil.exe and other EDB Recovery Tool. A number of Jet errors are quite difficult to handle.

In a practical scenario, you may receive the below Jet error while working on Exchange Server or trying to repair the database using Eseutil utility:

-1605 0xFFFFF9BB JET_errKeyDuplicate Illegal duplicate key 4294965691

When the above error message is encountered, you can’t continue using the Exchange Server database. This error indicates that EDB file is severely damaged and thus immediate recovery of corrupted database is required.

Microsoft Exchange Server offers an inbuilt utility to handle database inconsistency and corruption. But, this error can not be fixed using Eseutil.exe tool. If you keep running the Eseutil.exe tool after receiving this error message, it may cause a bigger headache, lost data, and lost time,in other words, it would merely aggravate the problem.

When you run the Eseutil.exe, it seems that the changes are not committed to Exchange Server Information Store or database, but the program may modify the database without displaying any sort of verbose information. It can apply changes to database even if it shows that database is not repairable.

In such circumstances, an absolute backup of your Exchange Server database proves a great help. You can easily restore your database from the backup and save your time and data. However, if the backup is either not updated or is damaged, severe problems occur.

This implies, you face critical data loss and need advanced and powerful third-party Recover EDB file tools. The applications are powerful enough to systematically scan the damaged EDB file using advanced scanning techniques and extract damaged data from it.

Stellar Phoenix Mailbox Exchange Recovery software repairs and restores damaged Exchange Server database in all cases of corruption. This EDB Recovery application does not demand sound technical skills to repair and restore the damaged database as it has simple and interactive user interface. It preserves the integrity of data owing to its read-only and non-destructive conduct. The software is usable with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. It restores all EDB file objects, such as emails, notes, contacts, tasks, calendar entries, attachments, and more.

Resolving “Error 4294966746: JET_errDatabaseInconsistent” Error in Exchange Server

Is your Exchange Server database inaccessible due to corruption of the Information Store? Are you getting Jet Database Engine errors while restoring database from backup? Information Store is the most commonly affected Exchange Server component, when database corruption occurs. Corruption generally occurs in Priv.edb or Pub.edb, that are located in ExchSrvr\Mdbdata directory on server. EDB (Exchange Server Database) is an extension of Exchange Server database file. In case of corruption, the database becomes inconsistent and Exchange Server can not read data from it. It leads to significant data loss situations and needs EDB Recovery, if you do not have an updated backup in place.

Microsoft Exchange Server indicates Information Store corruption with a number of symptoms, which include:

  1. You can not start Microsoft Exchange Server Information Store Service.

  2. The Information Store Service can not be stopped.

  3. The CPU (Central Processing Unit) usage level reaches at 100% and Information Store stops responding.

  4. Clients can not send or retrieve emails. The problem persists even if you stop and restart Information Store service.

  5. If you attempt to restore Microsoft Exchange Server database from offline backup and run Isinteg (Information Store Integrity) utility, you come across the below error message:

Error 4294966746: JET_errDatabaseInconsistent”

How to Fix Information Store Corruption?

To rectify the Information Store damage and recover the private and public information stores:

  1. Start the Information Store service.

  2. Check the consistency of Information Store using Eseutil.exe tool.

  3. Remove all .chk and .log files in ExchSrvr\Mdbdata folder.

  4. Verify that Exchange Server databases are working, by starting Information Store service. If it starts successfully, stop the service.

  5. Defragment the Exchange Server database that you repaired. You can defragment the database using Eseutil utility.

  6. Run Isinteg.exe utility to repair the databases.

  7. Restart Microsoft Exchange Server Information Store Service.

  8. Run the DS/IS (Directory Service/Information Store) Consistency Adjuster.

If the above method can not help you to Recover EDB file, you need to restore database from the most recent backup. However, if the backup is either damaged or not updated, you need to repair and restore the database using third-party applications.

The EDB Recovery Software work in all cases of database corruption and successfully restore database in original state, without modifying the original data.

EDB Recovery Tool is the most advanced recover edb utility for assured recovery of your damaged EDB file. The software effectively repairs Corrupt EDB File and restores all EDB file objects, such as emails, notes, contacts, tasks, notes, calendar items, and journals. It is designed for Microsoft Exchange Server 2007, 2003, 2000, and 5.5.

What is Hard Recovery in Microsoft Exchange Server?

Is your Exchange Server Database (EDB) file corrupted due to virus attack or improper system shutdown and various other reasons alike? Are you unable to access the database and your valuable emails, notes, contacts, tasks, and other objects? To extract data in such cases, EDB Recovery becomes need of hour. Microsoft Exchange Server facilitates you two types of recovery- Hard Recovery and Soft Recovery.

You must complete the hard recovery after restoring the database from an online backup. It is primarily a log replay process. In hard recovery, the below operations are performed:

  1. Patch information is applied to database during the log file replay.

  2. Checkpoint is ignored. The Restore.env file is used in place of checkpoint to consider for which file the recovery needs to be started.

  3. If EDB is restored to different file path than from which the file was backed up, the replay process of log file completes successfully, ignoring database paths that are listed in log files.

  4. Replay the restored transaction log files from temporary folder designated by administrator prior to restore.

  5. Hard recovery process doesn’t fail if other Exchange databases in storage groups are not available.

The database files, which are restored from online backup, are stored to normal paths set for database. The restore process starts by overwriting the existing Exchange Server database files. If you need existing database in future, you should back it up before restoring the database from backup.

You must consider that the restore process may fail due to any reason. Even if existing EDB file cannot be played at the moment, the files are possibly still repairable, and you can salvage the data.

The Corrupt EDB File recovery through hard recovery is possible in the majority of Exchange Server database corruption scenarios. However, you must have complete backup of the database to carry out this task. In case,the backup is either not available or not updated, you need to go for third-party Exchange recovery solutions.

In such situations, EDB Recovery Software come for your rescue. They are particularly designed to carry out in-depth scan of entire Exchange Server database and extract all mailboxes and their objects. The EDB Recovery Tool is totally easy to use with simple and self-explanatory graphical user interface. The applications preserve integrity of your database due to their read-only conduct.

EDB Recovery Software is the most advanced solution tor Recover EDB and handle all types of EDB corruption situations. It works well with Microsoft Exchange Server 2007, 2003, 2000, and 5.5. The software restores emails, notes, contacts, tasks, calendar entries, appointments, attachments, and other objects.

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.


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.

Know More: How to Recover EDB File?

UM Utility for Exchange Server Fails to Start

Unified Messaging (UM) is the integration of various communications media and electronic messaging technologies into a single store, while giving full access from different devices. The unified messaging products for Exchange Server have the capability to store all types of messages (like voicemails, faxes, e-mails etc.) in one system. The UM solutions for Exchange Server require Exchange database to be intact in order to get started. There can be situations when a unified messaging utility may stop. Apart from other reasons, you can deduce this behavior for database corruption. In such situations, if you don’t have any valid data backup, an EDB Recovery solution is required.

The following scenario will help you understand such problems better. Consider you deploy a Unified Messaging system in your Exchange Server environment. You observe that the UM utility cannot start. Later, you observe that Microsoft Exchange database is also unable to mount and reports an error, such as below:

The database files in this store are corrupted.
ID no: c104173b
Exchange System Manager.

You cannot mount the Exchange database at even further attempts.


The prime reason for the above error to occur is corruption of Exchange Server database.

This issue can also occur due to presence of old transaction log files in the folder.


You should try these solutions to overcome the existing problem:

  • Execute Eseutil /R command to replay the transaction log files and perform soft recovery

  • Remove the transaction logs from the folder and try to mount the database again. You can successfully rerun the UM utility once the database mounts

  • Check for the database backup. If available, restore

  • Run Eseutil /P command, followed by Eseutil /D and Isinteg commands. But this command deletes data and hence, is less recommended

  • Use an EDB Recovery Software to repair the corrupted database and extract the valuable data

An Recover EDB application uses a powerful, yet safe, set of algorithms to repair the corrupted Exchange database. These repair applications are easy to install and use with interactive user design. You can use these utilities in any case of Exchange database corruption.

EDB Recovery Tool is an advanced utility that repairs corrupted or damaged Exchange database and restores the mailboxes in *.pst files. The EDB Recovery Software supports Exchange Server 5.5, 2000, 2003, and 2007. The software is easy to operate and can also recover deleted mailboxes. The tool is compatible with Windows 7, Vista, XP, 2003, and 2000.

More 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: Exchange User Profile Recovery software Recover user Profile that is comprised in Exchange EDB file.

Stellar Phoenix Mailbox Exchange Recovery v3.0 Released with Added Support and Features

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


Stellar Phoenix Mailbox Exchange Recovery v3.0 is an affordable edb recovery 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.edb-recovery.com