Article ID: 273428 - Last Review: December 3, 2007 - Revision: 3.5

Error Message When You Restart Exchange Services If Global Catalog Cannot Be Contacted

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

This article was previously published under Q273428

Expand all | Collapse all

SYMPTOMS

When you try to restart the Exchange services, you may receive the following error message:

Could not start the Microsoft Exchange System Attendant service on Local Computer.

Error 1053: The service did not respond to the start or control request in a timely fashion.

You may also see the following events in the Application Event Log:

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: None
Event ID: 2064
Date: 7/6/2001
Time: 2:16:31 PM
User: N/A
Computer: COMPUTER
Description:
Process <process name>.EXE (PID=2040). All the remote DS Servers in use are not responding.

-and-

Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 1005
Date: 7/6/2001
Time: 2:19:47 PM
User: N/A
Computer: COMPUTER
Description:
Unexpected error The specified domain either does not exist or could not be contacted. Facility: Win32 ID no: c007054b Microsoft Exchange System Attendant occurred.

Back to the top

CAUSE

This issue may occur if the Exchange server is installed on a member server in a child domain with no Global Catalog server in it. One of the following has occurred:

The Exchange server has lost connectivity to the domain controller or domain controllers in the child domain.

-or-
The domain controller or domain controllers in the child domain have lost connectivity to the Global Catalog server or Global Catalog servers in the root domain.

Back to the top

RESOLUTION

Restore all connectivity between the Exchange server, the domain controller or controllers in the child domain, and the Global Catalog server or servers in the root domain.

Back to the top

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

Back to the top

MORE INFORMATION

When an Exchange service starts, it contacts a domain controller in its local domain by using DSAccess. The domain controller, if it is not also a Global Catalog server, uses DSProxy to connect to a Global Catalog server. A Global Catalog server must be contacted for the Exchange service to get the context that it needs to start.

Back to the top