This article was previously published under Q318552
This article has been archived. It is offered "as is" and will no longer be updated.
In certain Active Directory directory service topologies in Microsoft Exchange 2000 Server, the following events are logged in the Application log:
Event ID: 9188 Source: MSExchangeSA Description: Microsoft Exchange System Attendant failed to read the membership of group 'cn=Exchange Domain Servers,cn=Users,dc=server,dc=domain,dc=dom'. Error code '8007203a'. Please check whether the local computer is a member of the group. If it is not, stop all the Microsoft Exchange services, add the local computer into the group manually and restart all the services.
Event ID: 9543 Source: MSExchangeIS Description: Unable to create Public Folder proxy object for folder xxxxxxx in the Active Directory.
This problem occurs when there are multiple trees in the forest and when one or more child domains are not under the root domain of the forest.
To resolve this problem, obtain the latest service pack for Exchange 2000 Server. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 How to obtain the latest Exchange 2000 Server service pack
The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel. Component: System Manager
Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.
Microsoft has confirmed that this is a problem in Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.
For example, consider the following topology.
Place an Exchange 2000 Server in the child.forest.com domain. Several errors appear in the event log, and the DSAccess page in Exchange System Manager does not display correct information.