Article ID: 278441 - View products that this article applies to.
This article was previously published under Q278441
In Exchange System Manager, when you attempt to open the properties of an Exchange Server public folder, you may receive the following error message:
One or both of the following messages may also be logged in the Application event log every 15 minutes:
The mail proxy for this folder can not be found. This may be due to replication delays. The mail enabled pages will not be shown. ID no: C1038a21
Event ID: 9543
Unable to create Public Folder proxy object for folder folder_name in the Active Directory.
Event ID: 9188
Event Source: MSExchangeSA
Event Category: General
Microsoft Exchange System Attendant failed to read the membership of group 'cn=Exchange Domain Servers,cn=Users,dc=dcname,dc=dcname,dc=dcname,dc=com'. Error code '8007203b'. 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.
This symptom may be caused by one of the following:
The overall result is that the public folder is not stamped with a proxy address (such as firstname.lastname@example.org), and when you try to obtain the properties of the public folder in Exchange System Manager, you receive an error message.
IMPORTANT Follow the steps in the "Workaround" section to try to work around this problem before you apply the latest service pack for Windows 2000.
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/260910/EN-US/ )How to Obtain the Latest Windows 2000 Service Pack
To work around this problem, perform one or more of the following steps in the specified order, as necessary:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.
This problem may occur if the Windows 2000 LDAP provider does not correctly handle a reconnection attempt after any type of server failure. If a server goes down for any reason, typically, the Lightweight Directory Access Protocol (LDAP) provider reconnects, and everything is fine as long as the re-bind succeeds. If a re-bind does not work for any reason, all of the future operations on that connection do not work.
For additional information about a fix for this LDAP provider problem, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/289221/EN-US/ )LDAP_LOCAL_ERROR Occurs During Server Restart and LDAP Operations Do Not Work