Exchange uses three databases to store information about mailboxes, public folders, and directories. User mailboxes are stored in the private information database, public folders are kept in the public information database, and directory and configuration information are kept in the directory database. The private and public information databases collectively referred to as the Information Store are managed by one Windows NT program, the information store service (store.exe).
Unable to Initialize the Microsoft Exchange Information Store Service – Error
Due to the connection between the client and server computers. If the server computer’s clock and the client computer’s clock are not properly synced, then either the client computer or the server computer will record a different time. This generic error event appears when the local machine’s Exchange server database service could not be initialized. The user might need to restart the Information Store service while debugging instances or while switching from mixed to native mode. The domain ought to be online and correctly set up. Other than that, either of the next two things could be the cause of this problem:
- The Default Policy is deleted from the E-mail Address Policies tab.
- By substituting a custom email address policy for the Default Policy.
This error will stop the Exchange Information Store from running and provide an event ID 5000. In Exchange Server 2010, you can get the details of this error in the event viewer of the application log.
Event ID: 5000
Event Source: MSExchangeIS
Event Category: General
Description: Unable to initialize the Microsoft Exchange Information Store service.
It poses a serious risk to the entire database. The entire EDB file, including priv1.edb and pub1.edb, may become inoperable if the problem is not fixed right away, or the data may get corrupted. The stored data is therefore under significant warning, which could result in real loss.
Method #1. Update the default policy
- Right-click on the Windows icon and choose Run.
- In the text field, type ‘adsiedit.msc’ and click OK.
- Follow Action >> Connect >>’ Select a well-known Naming Context’ >> Configuration and click OK.
- Expand all the following fields –
- Configuration (the_Domain_Controller_Name. the_Name_Of_The_Domain.com)
- CN=Configuration, DC= domain, DC=com
- CN=Services
- CN=Microsoft Exchange
- CN= Organization
- CN=Recipient Policies
- Go to Email Address Policy, right-click and choose Properties.
- Look for purportedSearch option under the Attribute option. Ensure that the value is mailNickname=*.
- If the purported value is not the desired one, then you can change it manually too. Click Edit in the purportedSearch option.
- Go to clear and type mailNickname=*. Then, click OK and save.
- Now go to the msExchPolicyOrder option under Attribute and click Edit.
- Click Clear and input 2147483647 in the value field. Click OK.
- Exit from the Active Directory Service Interface (ADSI) Edit.
- Restart the Exchange Server.
Method #2. Restart the Active Directory service
The second method is the simple one where you can restart the server and it will try to start the Exchange Information Storage service.
- First, verify that the domain is properly configured.
- Make sure that the domain is currently online.
- Restart the Exchange Active Directory Topology Service at this time.
- Run Exchange Server as Administrator by using the command prompt.
- Run the command – \\ADServerName\Set
- Restart the Exchange Active Directory Topology Service at this time.
Conclusion
There is no other choice if either method of error diagnosis is unsuccessful; otherwise, data loss or damage to EDB files may result. Consequently, one might move forward with a different Exchange Server Recovery Solution choice. Professional Exchange Server Recovery software will help you in repairing the EDB file from the affected server and restore it to a live Exchange account. You can also move the data to an Exchange Online account from Office 365.
