Exchange Information Store service is the most critical component, without which the server is of no use. The Information Store is comprised of different storage groups and if these groups go corrupted, it results into data inaccessibility. Further, the Information Store service also stops. In critical situations, when you cannot restore from the backup or repair it using standard utilities, an Exchange Server Repair tool is required to be used.

For example, when using Exchange Server, you might observe one or more of the following symptoms:

• You attempt to start Information Store service, but cannot do so with the following error:

"Windows could not start the microsoft exchange information store on local computer."

• When you try to start the Exchange event service, this also fails and the following error occurs:

"Could not start the microsoft exchange event service on local computer.

Error 1068:The dependency service or group failed to start."

• On viewing the event viewer, you see event IDs 7001 and/or 7024 logging that suggest that Information Store service has failed to start or has terminated

Cause

The general reasons of Information Store not starting are:

1. Permission issues related to file system, registry etc.

2. The message store or log files could not find the required disk space

3. Corrupt message store

Event 7024 generally occurs when the Exchange computer account doesn't has sufficient rights to access the Information Store. This can also occur if Exchange Enterprise Servers group that root from the parent domain doesn't consist the required Exchange Domain Servers group from child domain.

Solution

In order to solve the above problem, you need solutions such as:

1. Check for sufficient permissions required to access the file system, registry and other components

2. Check for required disk space for log files and message store

3. Run setup.exe /domainprep for Information Store permission related issues

4. Add the required group to the Exchange Enterprise Servers group in the parent domain

5. Repair the corrupted message store using eseutil /r and/or eseutil /p command or restore from backup

Backup is the safest option to restore the database as the eseutil utilities can cause irrecoverable data loss. However, if backup is absent, you are suggested to use an Exchange Repair utility. The Exchange Server Repair tools use powerful and safe scanning algorithms to repair and restore the corrupted Exchange database.

Exchange Repair Software is an advanced and safe tool that repairs Exchange databases and extracts the mailboxes as *.pst files. The Exchange Repair tool supports Exchange Server 5.5, 2000, 2003, and 2007. The software is applicable in each instance of database corruption and provides an interactive design and look.