Recover Exchange database files in few simple steps

The Information Store is vital part of MS Exchange Server. It is specifically used to store crucial data in both Mailbox and Public folder. The Information Store can be looked a database of Exchange Server as it uses database files to manage the stored data efficiently. It must be quite understandable that Information Store holds users important data. Although the files kept in Information Store is always prone to number of threats. Which can severly damage the data that can result in corruption or permanent loss. However the positive side of using Exchange Server is that, these errors can be easily tackled using various recovery techniques.

How to do Exchange server recovery from error:-Error - 1022='JET_errDiskIO' = Disk I/O Error

Exchange database (EDB) files are designed to store all the information and folders. Exchange database is the bonanza of all types of data. Corruption in Exchange database may affect smoothness of working or may be due to this Exchange server may refuse to open. Your each and every effort to access database or user mailbox has to face failure since database is damaged due to some unexpected cause. In layman language these cause are called errors. To ignore these errors or to make Exchange database recoverable you can use previous backup file to mount all essential data again on Exchange server.

How to solve Exchange Event 9175 ?

Exchange Mailbox Store is a very important component of the server and essential to proper functioning of an Exchange server. Each Exchange mailbox store is constituted of two important files named Priv.edb and Priv.stm. The EDB file is an ESE database file and also known as MAPI based database. It stores all MAPI messages, e-mail attachments and other important data. The STM file, known as streaming file, is also an ESE database file and stores primal internet content. When Microsoft Exchange Server is started, ESE determines the state of database whether it is in Consistent or Inconsistent. If ESE finds any inconsistency in Exchange database, it performs soft recovery. However, when a severe corruption occurs in a mailbox store, you will no longer be able to work with Exchange database smoothly and when you attempt to mount the database, you may get some error messages.

For example, consider a scenario wherein you are using Exchange server 2000 or 2003 and you encounter some corruption problem in your database. When you try to mount the Exchange mailbox store, you may receive the below event log description mentioned in the application event log:

Event Type: Error
Event Source: MSExchangeSA
Event Category: MAPI Session
Event ID: 9175
Date: 7/9/2001
Time: 5:32:11 PM
User: N/A
Computer: XYZ
Description:
The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000

Causes:

Some of the reasons for the occurrence of above event are:

• Most of the time this event occurs if an Exchange Mailbox store failed to mount.
• System Attendant (SA) is attempting to make an Offline Address Book (OAB).
• Information Systems store services are stopped.
• Corruption in Exchange Mailbox store.

Solution:

You can try the following solution:

• Check whether Exchange Information Store service is running or not. If the Information store is not running, try to start it.
  

• If the Information store is working and the event is still logged. Confirm that the default Exchange mailbox store is mounted. If it is not mounted, try to mount it.
• If the Information Store is corrupt, you will need run built-in ESEUTIL/P command line utility.

If the above said repair utility fails to repair the corrupted Information Store, then you'll have to use a third-party Exchange recovery application to repair the damaged Exchange Information Store.

Such third party Exchange Server Recovery software are specifically developed to recover data from logically or physically damaged Exchange database (EDB) file. The repaired and recovered edb file can be saved at default or user's specified location.

Repairing oversized corrupt EDB file in MS Exchange Server 2003

Microsoft Exchange Server is the server-side of the client-server product by Microsoft. It provides support for emailing, calendar entries and mobile- and web-based access to exchange information. All such information is stored in an EDB (Exchange Information Store Database) file. However, sometimes the EDB file can get corrupt due to which you are unable to mount the mailbox. Corruption situations can arise due to various reasons such as virus infections, human errors, database header corruption, quitting Exchange server unexpectedly, etc. In such cases, you should take appropriate corrective measures to rectify the situation. However, if you are unable to do so, then you should use a third-party Exchange Repair software to do the needful.

Consider a scenario wherein you are not able to mount Microsoft Exchange Server 2003 Standard Edition mailbox. The event ID is logged in the Application Event Log:

“Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 1112
Description: The database "Mailbox Store (Server Name)" has reached the maximum allowed size. Attempting to unmount the database.”

Cause:

The cause of this erroneous situation is that the EDB file has corrupted as its size has exceeded the permissible size of 16 GB.

Resolution:

To resolve the situation:

1. Upgrade to Exchange Server 2003 SP2 as it has got size limit of 75 GB.

2. Perform the following tasks if you are an administrator:
     a)Increase the database size limit temporarily by 1 GB.
     b)Remove the not so required database content.
     c)Defragment the database to reduce it to the permissible database size limit.

3. Mount the database in a recovery storage group by using the Recovery Storage Group feature. Then, you can use the MS Exchange Merge Wizard (Exmerge.exe) to extract the mailboxes from the database.

However, if you still are unable to resolve this issue then you should use a third-party Exchange repair software to repair the EDB file. Such tools are able to repair the EDB file without overwriting the original contents and by using fast yet sophisticated scanning algorithms.

Stellar Phoenix Mailbox Exchange Recovery is an MS Exchange repair software that enables you to repair corrupt EDB files. It scans the corrupted EDB file, repairs it, and saves it at a user-specified location. This Exchange repair software recovers different mailboxes in a separate PST files. This software supports Exchange Server 5.5, 2000, 2003, and 2007. It is compatible with Windows 7, Vista, Server 2003, XP, and 2000.

How to Solve when Exchange Database Fails to Mount with (hr=0x80004005, ec=-528) Error?

Transaction log files record all the modifications to an Exchange Server database and are crucial for the proper functioning of Exchange. If you remove a log file that has not been written to the associated database, it can bring several issues, the most common being that the database may fail to mount. You can solve this problem by removing all the log files, but you first need to check the database consistency. If it exists in inconsistent state, the solution is to restore from backup or apply an EDB Repair technique. For instance, consider a scenario in Exchange Server. You try to mount a mailbox store, but the operation fails with the below error message.