| Event Id | 3039 |
| Source | MSExchangeIS Public |
| Description | "Message ID: #-###### NDR recipients: 1 of 1 /O=Exchange_Organization_Name/OU=Exchange_Site_Name/CN=Configuration/cn=Servers/cn=Exchange_Server_Name/cn=MICROSOFT PUBLIC MDBThe recipient name is not recognized (0,0)" |
| Event Information | According to Microsoft: CAUSE: public folder replication is successful, but only for new public folder items or only for modified public folder content. In this scenario, previous public folder information does not replicate to other Exchange Server computers successfully. This problem occurs even if you restart the destination Exchange Server computer(s). Typically, this problem occurs more frequently in a scenario where the receiving computer is running Exchange 2000 Server or Exchange Server 2003 and the sending computer is running Exchange Server 5.5. This problem is caused by the changed behaviors between Exchange 2000 Server and Exchange Server 5.5. In Exchange Server 5.5, a status request message for all replicas, including the whole public folder hierarchy, is generated every time that the Microsoft Exchange information store service is started. This is not the default behavior in Exchange 2000 Server. However, with Exchange 2000 Service Pack 3 (SP3) and later versions, you can configure Exchange 2000Server and Exchange Server 2003 to generate status request messages every time that the information store service starts. To configure public folder replication status request messages, follow these steps: 1. Follow the steps in Microsoft Knowledge Base article 321082 to configure the registry value for the public folder replication status request messages on the Exchange 2000 Server computers and on the Exchange Server 2003 computers that do not have up-to-date public folder hierarchy information. 2. Dismount and then remount the public folder store on each of those Exchange Server computers where you configured this registry key. 3. Wait approximately 12 to 24 hours or longer, and then verify that the whole public folder hierarchy has replicated to the computer where you experience this problem. 4. Public folder content replication takes much longer to complete than public folder hierarchy replication. Wait at least 48 to 72 hour |
| Reference Links | How to troubleshoot public folder replication problems in Exchange 2000 Server and in Exchange Server 2003 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.