Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

XADM: System Attendant Does Not Start with Event ID 2060


View products that this article applies to.

This article was previously published under Q251640

↑ Back to the top


Symptoms

The Microsoft Exchange 2000 Server system attendant may not start, and the following error messages may be logged in the Windows NT Event Viewer.
Event ID 2060
MSExchangeSA
The DsProxy failed to start, error '%1'.

Event ID 1005
MSExchangeSA
Unexpected error An unknown error has occurred. ID no: fffffffd
Microsoft Exchange System Attendant occurred.

↑ Back to the top


Cause

The domain controller that the Exchange 2000 Server computer is communicating with has been configured as a Global Catalog server (GC), but the domain controller was not restarted after it was configured as a GC.

↑ Back to the top


Resolution

To resolve this problem, restart the domain controller that was configured as a GC. The newly created GC must be restarted to initialize the MAPI interface on the GC.

↑ Back to the top


More information

A GC accepts requests from both MAPI and Lightweight Directory Access Protocol (LDAP) clients, and therefore must load both interfaces on the server. On the GC, MAPI does not dynamically load, and you must restart the GC to initialize the MAPI interface.

The system attendant does not start because a call to the directory service did not return the GCs that are in the domain. The directory service requires a list of the GCs to start, and if the directory service does not start, the system attendant does not start.

↑ Back to the top


Keywords: KB251640, kbprb

↑ Back to the top

Article Info
Article ID : 251640
Revision : 5
Created on : 2/27/2007
Published on : 2/27/2007
Exists online : False
Views : 279