Article ID: 254061
Article Last Modified on 2/27/2007
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
This article was previously published under Q254061
SYMPTOMS
When an Exchange 2000 user tries to send e-mail to a public folder, a "Message Transfer Failure" non-delivery report (NDR) is generated.
CAUSE
This behavior only occurs when there is no Exchange 2000 public folder server in the organization. The mail is being sent to the first Microsoft Exchange Server 5.5 computer in the public folder hierarchy list, and that server cannot look up a replica server for the public folder because there is no replica in the Exchange Server 5.5 computer's site, nor does it have an affinity to sites which do contain replicas.
WORKAROUND
There are two workarounds for this issue:
Method 1
This is the preferred method.
Install at least one Exchange 2000 public folder server in the organization, and allow the public folder hierarchy to replicate to it. After you do so, mail sent to public folders from Exchange 2000 users is routed to this server to get the replica list of where the public folder exists.
Method 2
Configure Exchange Server 5.5 site affinities from the site that contains the first Exchange Server 5.5 computer in the public folder hierarchy list to other sites as necessary, so that it can look up a replica list for the folders to be mailed to.
STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.
MORE INFORMATION
To see the folder hierarchy list, use the Lightweight Directory Protocol (LDP) tool to connect to a domain controller, and locate the following object
CN=Public Folders,CN=Folder Hierarchies,CN=name of first administrative group,CN=organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain
and view the msExchOwningPFTreeBL attribute, which tells which server owns the public folders.
Keywords: kbbug kbpending KB254061
