• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 534
  • Last Modified:

Event ID 7020


I have 2 windows 2003 Servers R2, Both are on same LAN, and both are DC's. The first DC we promoted and that has all of the master roles is also the Exchange 2003 Server (i know its not ideal but budget was not there)

I had an issue that when the server rebooted i got the following error in system Log and Exchange MTA stack and Information store did not start, however both started manually. Looking at other event logs it implied that the server had a problem contacting the GC (which is itself!!). I made the 2nd DC a GC as well and now the problem has gone.

Does anyone have any idea's why that would happen and how i can troubleshoot the GC on Exchange server.


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date:  6/1/2006
Time:  11:28:10 PM
User:  N/A
Computer: HPC01
The Microsoft Exchange Information Store service terminated with service-specific error 0 (0x0).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
1 Solution
Hi higgsy,

its due to service dependencies not starting before your exchange services - may have been one off
another idea, please back up the reg before attempting this:
Exchange Store Does Not Start: Errors 7024, 1026, 9542, and 5000
When you start Windows with Exchange installed, you may be notified by Service Control Manager with an error message similar to the following error message:
At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.

The Exchange Microsoft Exchange Information Store will not start. As a result, all services that depend on Information Store service will not be able to start.
You may find the following error events in Event Viewer:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
The Microsoft Exchange Information Store service terminated with service specific error 0.


7020 » The Windows Server 2003 Terminal Services
Licensing service does NOT start

Work Manager error Can't Startup work scheduler, Error code -1072167891.

On databases larger than 80 megabytes, the Microsoft Jet database engine transactions can use a lot of memory.

You can tune the version store in Windows Server 2003:

1. Use the Registry Editor to navigate to:


2. Add a MaxVerPages Value Name as a REG_DWORD data type and set the data value to a Decimal number between 256 and 2048. The default is 1024. For a large database, set it to 2048.

3. Exit the Registry Editor.

Joseph NyaemaIT ConsultantCommented:
Try changing the service account to system.
Walter PadrónCommented:
Hi higgsy,

As Jay_Jay70 said is some kind of a dependency issue, the Information Store service uses the Global Catalog for message routing and mailbox lookup and if none are available it can't start or if running inmediately shutdown. There is a lag of time between the boot process and the server be ready for GC services, this is why the exchange services don't start and why it works installing another GC because the service find GCs automatically (not recommend, but you can modify this behaviour on ESM\First Administrative Group\Servers\server_name\Properties\Directory Access)


Featured Post

[Webinar] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now