Thursday, 27 August 2015

How to Resolve Exchange Event ID 1121 and 5000

Microsoft facilitates you to configure Windows Server operating system as a global catalog server. Global catalog is basically a distributed data depository, which comprise of the searchable, partial demonstration of each object in each domain in multi-domain AD DS (Active Directory Domain Services) forest.
It offers enhanced performance over typical Windows Servers. However, you may not start Exchange Server services on the global catalog server and thus the EDB (Exchange Server Database) can not be accessed. It may cause database corruption and lead to data loss. At this point, you are required to go for Exchange Server recovery solutions to extract data from EDB file.

Exchange Server services cannot be started if you Install the Exchange Server 2007 on global catalog server. But, it is possible to start other server related services manually. It may take a very long time to shut down the servers in such configuration. Furthermore, you may encounter the below events in Application Event Log of MS Exchange Server:

Event ID: 1121 
Source: MSExchangeIS 
Category: General 
Type: Error 
Description: Error 0x96e connecting to the Microsoft Active Directory. 

Event ID: 5000 
Source: MSExchangeIS 
Category: General 
Type: Error 
Description: Unable to initialize the Microsoft Exchange Information Store service. - Error 0x96e. 

You cannot access data from MS Exchange Server database if the Exchange Information Storage does not get started. To gain access of your significant data in such cases, you need to find out the root of this problem and perform Microsoft Exchange recovery by fixing it


This behavior of Microsoft Exchange Server may occur due to any of the following reasons:

  • The Exchange Server dependent services and domain controllers don't start properly when MS Exchange Server 2007 attempts to start. 
  • Exchange Server Information Storage or entire database is corrupt. 


To work around this problem, follow the underwritten steps:

  • Try to start the Microsoft Exchange Server Information Store Service manually. 
  • Change the dependency of Microsoft Exchange Server services. 
  • Restore corrupt EDB file from an online or offline backup. 

If you fail to fix the problem using the above Exchange recovery methods, Exchange recovery software remains the only way to go. Such tools perform thorough scan of the database to extract all corrupt or damaged data from it. They are absolute safe and easy to use. 

Stellar Phoenix Mailbox Exchange Recovery is the most advanced and efficient utility to insure perfect recovery. The software restores emails, contacts, tasks, notes, journal, attachments, appointments, and all other EDB file objects and saves. It supports Microsoft Exchange Server 2013, 2010, 2007, 2003, 2000, and 5.5. 


Post a Comment