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.