Exchange 2007 services cannot start automatically

When you install Microsoft Exchange Server 2007 on a global catalog server, Exchange 2007 services cannot start. However, you can start other services manually. Servers in this configuration may take a long time to shut down.

SYMPTOMS

When you install Microsoft Exchange Server 2007 on a global catalog server, Exchange 2007 services cannot start. However, you can start other services manually. Servers in this configuration may take a long time to shut down. Additionally, the following events are logged:

Event ID : 1005
Source : MSExchangeSA
Category : General
Type : Error
Description : Unexpected error The Local Security Authority cannot be contacted ID no: 80090304 Microsoft Exchange System Attendant occurred.

Event ID: 2601
Source: MSExchange ADAccess
Category: General
Type: Warning
Description: Process MSEXCHANGEADTOPOLOGY (PID=1624). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,…> – Error code=80040934. The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.

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.

Note Exchange 2007 has less dependency on the Microsoft Exchange System Attendant. The Microsoft Exchange Information Store service no longer depends on the Microsoft Exchange System Attendant. Therefore, the symptoms that are described in this article may differ from the symptoms that you may experience in an earlier version of Microsoft Exchange Server.

 

CAUSE

This problem occurs because the domain controller and other Exchange-Server-dependent services do not start completely when Exchange 2007 tries to start.

WORKROUND

 

Method 1:

Manually start the services

Method 2:

Change the dependencies

An Exchange Server service does not depend on other Exchange Server services that depend directly on the Netlogon service and on the LSASS service.

Registry path
Registry subkey (Multi_SZ)
Registry value

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesMSExchangeSA
DependOnService
EventLog, NtLmSsp, RPCSS, LanmanWorkstation, LanmanServer, Netlogon

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesMSExchangeADTopology
DependOnService
Netlogon

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesMSExchangeIS
DependOnService
Netlogon

Note If any Windows service cannot start, Exchange Server will not start. However, the method should reduce the time that is required to shut down the server.

Method 3:

Use the BootPause registry key to delay the startup of Exchange Server

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 (http://support.microsoft.com/kb/322756/) How to back up and restore the registry in Windows

Add the following registry key to the affected server to delay the initial attempt to start the Microsoft Exchange System Attendant.

Registry path
Registry subkey (DWORD)
Registry value (Decimal, the value is in seconds)

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesMSExchangeSAParameters
BootPause
120

Note A value of 120 is very high. More time may be added to start the server. You can select values that are less than 120. However, selecting the correct value depends on several factors.
You may also have to set the other Exchange Server services to depend on the Microsoft Exchange System Attendant, as in the following example.

Registry path
Registry subkey (Multi_SZ)
Registry value

HKEY_LOCAL_MACHINESystemCurrentControlSetServicesMSExchangeADTopology
DependOnService
MSExchangeSA

HKEY_LOCAL_MACHINECurrentControlSetServicesMSExchangeIS
DependOnService
MSExchangeSA

If you do not set the other Exchange Server services to depend on the Microsoft Exchange System Attendant, other Exchange Server services that access the directory will also fail. Services that depend on the Microsoft Exchange System Attendant could lead to other services being shut down when you restart the Microsoft Exchange System Attendant.

Resources: http://support.microsoft.com/kb/940845