Thursday, November 3, 2011

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


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.

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.

No comments:

Post a Comment