Hello, We're having a problem with our newest Exchange 2003 SP2 server where a free/busy public folder will not replicate from the new server in its new admin group to an existing server at a different admin group (which hosts the PF tree), although the reverse is working as expected. This prevents users at the existing admin group to view free/busy information for users in the new admin group, while users in the new admin group can see the free/busy info for users in the existing admin group. I've found the free/busy folder in the new server's PF store and set its replication settings to replicate to the existing server. The existing server, however, is not receiving the folder (it is getting other folders from the new server, though, so transport is not an issue). On the existing server, which is in the forest root domain and the first admin group, I cannot see the free/busy folder in the PF hierarchy nor in its PF store. I can only see the folder if I go directly to the new server's PF store in the ESM. Here's a summary of the setup: The Exchange organization started with a single server in a single-domain forest. We created a new admin group in the ESM. We then created a new domain in its own AD tree, and installed the new Exchange server in the new domain and admin group. New mailboxes were set up after migrating user and computer accounts from a legacy domain (which did not have Exchange) to the new server and domain. A new free/busy folder appeared in the new server's PF store after the users started using their mailboxes. We set this new folder to replicate to the existing server. The free/busy folder is not listed under the PF hierarchy on the existing admin group/server nor in the server's PF store. Right-clicking on the folder from the new server's PF store shows a limited set of property pages - the Exchange General, E-mail Addresses, and Exchange Advanced tabs are not shown. The mailbox store on the new server has the PF store on the same server as the default public store. The folder cannot be found on ADSI Edit at the usual location on either domain.From what I can see, the problem seems to be caused by a lack of a public folder directory object that refers to this folder in the corresponding PF store. As noted above, replication for other folders is working as expected. I've hit a wall while trying to solve this issue, as all I've been able to find is instructions on rebuilding the system folders, which I would hate to do and am not sure if it'd apply to our problem. Does anyone have any suggestions on what we could do to solve this problem? Thanks in advance.

Take a look at this blog article: http://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=25 I walk through how to troubleshoot the replication message delivery and a couple root causes that aren't already covered on many common articles (also linked inside).

Dear customer: In order to better troubleshoot the issue, please help collect the following information: 1. On the original Exchange server, open ESM, navigate to public folder, right click it and select view system folders, expand SCHEDULE + FRRE/BUSY, right click EX:/o=ORG_NAME/ou=first administrative group, select properties, click replication tab, send the screenshot of it to v-rocwan@microsoft.com for analyze, 2. On the original Exchange server, open ESM, right click the original server and select properties, click diagnostics logging tab, and navigate MSExchangeIS Public Folder, set logging on Replication Incoming and Replication Outgoing to Maximum. 3. On the new Exchange server, open ESM, right click the original server and select properties, click diagnostics logging tab, and navigate MSExchangeIS Public Folder, set logging on Replication Incoming and Replication Outgoing to Maximum. 4. Modify the calendar of a user which is belong to second administrative group, wait for the event is logged in application log and save the log as .evt file, and send both the original and new Exchange servers application log file to me. Note: when you send e-mail to me, please add the subject of the post. Thanks for your cooperation. If anything is unclear, please feel free to let me know. Rock Wang - MSFT

Thanks, Jeff. I followed the steps in that page to which you linked, but unfortunately the problem continues. Also, the proxyAddress attribute is set properly on the public store on both servers. Rock, thanks for the assistance offer. I turned logging to maximum for incoming and outgoing replication messages, NDRs, general replication, and replication errors on both servers. I've noticed that the new server is issuing replication messages for the affected public folder, however the original server is not logging any incoming messages. The reverse works, though: messages from the original server are received and processed by the new server. Both servers are logging event ID 3093, error -2147221233, on their respective public stores. You'll receive an e-mail from me shortly.

Bump... I guess no one has seen this particular error before?

Dear customer: Please post the complete event log into the forum for analyze, include the source, Event ID, description, Category, only this we can give you more help. In addition, I havent received your e-mail now. Thanks for your cooperation. If anything is unclear, please feel free to let me know. Rock Wang MSFT

Hello, My name is william, and my company exchange 2003 now appear this case, and i have following the kbhttp://support.microsoft.com/Default.aspx?id=301460try to fix, but not successful to fix the error, the replicate between two server doesn't work and the original server can replicated with the new exchange server and the new can not replicated with the old one, and the new exchange is the back-end clustering. i have run the commandexchsrvr\bin\isinteg -s server1 -fix -test alltests, it show 6 errors from replications , how can i do now??

Dear customer: Please send your issue into a new thread, so that we can follow up it. Thanks for your cooperation. Rock Wang - MSFT