XADM: System Attendant Does Not Start with Event ID 2060
This article was previously published under Q251640 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. 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.
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.
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.
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Help and Support
Back to the top
|
