XADM: System Attendant Does Not Start After Installing Exchange 2000 Server in a Grandchild Domain in an Exchange Enterprise Environment

View products that this article applies to.

This article was previously published under Q247473

Expand all | Collapse all

SYMPTOMS

When you set up an Exchange topology that consists of a parent domain controller, several child domains, and a grandchild domain, and then install Microsoft Exchange 2000 Server on a Microsoft Windows 2000-based member server in the grandchild domain, the system attendant (Mad.exe) may not start when you log on after the computer restarts. The following message is displayed in the Event Viewer:

Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 1005
Date: 9/13/1999
Time: 4:17:07 PM
User: N/A
Computer: DEPLOY17
Description: Unexpected error The specified directory service attribute or value does not exist. Facility: Win32 ID no: 8007200a Microsoft Exchange System Attendant occurred.

The Exchange 2000 servers and Exchange Administrator groups for the grandchild domain are not added to the Exchange container or the organization object.

Back to the top

CAUSE

This behavior can occur when the permissions set by the first Exchange 2000 server are modified and overwritten with the data from the second server during replication that occurs during the same time frame. This can occur when you install an additional Exchange 2000 server in another domain before the configuration objects of the first installation of Exchange 2000 Server in the grandchild domain have propagated throughout the entire Exchange organization.

Back to the top

WORKAROUND

To work around this issue, allow full replication of an Exchange 2000 server to propagate throughout the entire Exchange organization before installing an additional Exchange 2000 server.

Back to the top