Monday, April 29, 2013

How to say good bye to Exchange Error 1088 & 1005

Exchange server is becoming famous because of its user compatibility but it becomes irritating when you are working very heartily and sudden a error message pop up to disturb you.

It is a very common thing. Take one example of the scenario. Once I got stuck and the following error message appeared on my screen:-

Event ID: 1088
Source: MSExchangeIS
Type: Error
Category: General 

The information store could not be loaded because the distinguished name(DN)of message database
/O=org_name/OU=site_name/CN=RECIPIENTS/CN= does not match the DN of directory

This error comes when you initiate the Information Store service and the services do not run, you may receive Jet Error 1276 (ecDomainError), and Event ID 1088 may be logged. Generally in such a case you must reinstall Exchange Server and use the organization and site name that are displayed in the event ID 1088 error message. This act may solve the problem. But it may be possible that even after installing  Exchange Server again the information store may still be unable to start and may log the same events, but in the description of this event ID 1088 the Distinguished Name (DN) of the directory and the message database are reversed.

Possible causes of this Problem:-

  • If the DN are the different of the Priv.edb and the Pub.edb databases.
  • The main reason behind this situation is either when you install Exchange Server with an organization or site name that does not match with the information stores that you are restoring now, or you only restore the Priv.edb/Pub.edb database. 
  • When you install Exchange Server with a new organization and site name, the DN of the directory matches the .edb file that you originally restored, but the other .edb file DN is incorrect. 
  • When you attempt to start the information store, it logs an event ID 1088 error message in which the directory DN and the message database DN have switched from the previous event ID 1088 error message. 

Note the source of the event ID 1005 error message. For example: 
Event ID: 1005
Source: MSExchangeIS Public
Type: Error
Category: General
Unable to start the Microsoft Exchange Information Store. Error 0x4fc. 


  • Start the information store (the information store starts the private information store. Therefore, if the source of event ID 1005 error message is MSExchangeIS Private, the DN in the directory is not working on the Priv.edb database).
  • The Information Store service stops processing at this point, so the Pub.edb database DN may not match the directory whether DN in the directory is correct. 
  • If the source of the event ID 1005 error message is MSExchangeIS Public, the DN of the Priv.edb database is correct and the DN of the Pub.edb database is incorrect.
  • Make sure that you restore both the Priv.edb and the Pub.edb database files from the same backup set (or that the Priv.edb and the Pub.edb database files at least have DNs that match) and that you reinstall Exchange Server with the DN that matches the .edb files.

If all these steps are not able to repair EDB file then just install Stellar Phoenix Exchange Server Recovery software. This is one of the best commercial tool of the Stellar for Exchange server recovery and compatible with all Exchange Server versions like:- 2010, 2007, 2003, 2000 and 5.5.

No comments:

Post a Comment