I am now on my third day of trying to work out why most (but not all) public folders are not replicating between two Exchange 2003 servers. A few of the PFs repliacte fine - the rest do not replicate. I have tried creating a new PF, and it also did not replicate. I have defragged and run isinteg on both PF databases. Isinteg was unable to fix 3 errors on server1, and 2 errors on server2. The errors are all like this: Error: ReplState 41: Error ecNotFound-MAPI_E_NOT_FOUND while configuring MGL from ptagReplicaListWhen I try to force a sync I get a large number of events like this:Event Type:WarningEvent Source:MSExchangeIS Public StoreEvent Category:Replication Errors Event ID:3084Date:05/05/2009Time:13:15:00User:N/AComputer:server1Description:Error (0x8004010f) has occurred while processing the Owning Folders table on database "First Storage Group\Public Folder Store (server1)". /O=ORG/OU=COUNTRY/CN=RECIPIENTS/CN=PFNAME PPP66BBBC1066BBBC1066BBBC10B1AAA8CE1EB180. I am starting to come to the conclusion that there is some type of corruption in the DBs that is preventing replication for most of the folders - but what to do about it? Should I be exporting the contents and the permissions of the PFs, deleting the database, and then recreating it all? There are 300 PFs and 7GB of content, so this could take some time. What would be the best way to go about it?Thanks,CarolPS. Please, no advice to documents on PF troubleshooting - I have read them all. And yes I have run the ExBPA.http://www.wapshere.com/missmiis

Hello,I guess this error islogged because ptagReplicaList in the ReplState table is empty and i bet removing replica and re-adding replica will resolve the issue.Give a shot and let me know. Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3

I had tried that on one PF and it didn't help - but now I've removed the replicas for all 84 PFs that are definitely not replicating and leaving it to settle overnight. Tomorrow I will attempt to recreate a replica and see what happens.Would it be worth trying another isinteg first? It concerns me that there are errors in both the source and target databases. Also there are no Outgoing Replication messages for the faulty PFs, so I don't think the source server is even attempting to replicate them.Thanks for your response,Carolhttp://www.wapshere.com/missmiis

Yes, we can try one more time and this time hopefully it will fix all the logical corruption with the database, try the following command as well.isinteg -s (server name) -test replstate -fixlet me know how it goes.Good Luck!Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3

Yes that is the command I have been running. I also ran it with the alltests option.Will try again tomorrow,Carolhttp://www.wapshere.com/missmiis

No chnage overnight. I re-ran isinteg - it still reports the same errors and doesn't fix them.I tried adding back the replica for one PF - it still does not replicate. Still hundreds of 3084 warnings in the event log when it tries.We are also getting thethree events belowevery 5 minutes, despite removing replicas from the OAB and free busy a couple of days ago.There is still an Exchange 5.5 server in the network, though all replicas were removed from it some time ago. Thanks again for your help,CarolEvent Type:WarningEvent Source:MSExchangeIS Public StoreEvent Category:Replication Errors Event ID:3085Date:06/05/2009Time:08:53:42User:N/AComputer:SERVERDescription:Error 0x8004010f occurred while generating an outgoing replication message. Type: 0x4Folder: (3-7) NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY\EX:/o=ORG/ou=COUNTRY Database "First Storage Group\Public Folder Store (SERVER)". Event Type:WarningEvent Source:MSExchangeIS Public StoreEvent Category:Replication Errors Event ID:3092Date:06/05/2009Time:08:53:42User:N/AComputer:SERVERDescription:Error 1129 occurred while processing a replication event. Folder: (7-FC5) NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK\EX:/o=ORG/ou=COUNTRY\OAB Version 2 Event Type:WarningEvent Source:MSExchangeIS Public StoreEvent Category:Replication Errors Event ID:3085Date:06/05/2009Time:08:53:42User:N/AComputer:SERVERDescription:Error 0x8004010f occurred while generating an outgoing replication message. Type: 0x4Folder: (1-6935D3) Database "First Storage Group\Public Folder Store (SERVER)". http://www.wapshere.com/missmiis

Hi Carol, This Error event indicates that a table may be corrupted, inconsistent, or changed. Database maintenance should correct the problem. Exchange database maintenance occurs daily by default. No user action is required. However, if this event is logged repeatedly, try one or more of the following: 1. Review the Application log for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this event. 2. Does it cause mailflow interruptions or other problems in your Exchange environment? 3. If your symptom are as follows: New content created in a new public folder will successfully replicate to other Exchange servers. Old content moved into a new public folder will successfully replicate to other Exchange servers. This problem can occur when the Owning Folders table in the public folder store has become corrupt. The following workaround can be done to resolve the folder that is not replicating. 1) Create a new top level public folder called 'Public Folder Recovery'. 2) Select a root level public folder that is not replicating. 3) Right click on the selected folder, then select the option to MOVE the folder (and all of its subfolders) into the new 'Public Folder Recovery' folder. 4) Right click on the moved folder under the 'Public Folder Recovery' folder, then choose COPY to copy it back to the root of the tree. 5) Add your content replicas to the copied folder 6) Wait for replication to occur. Also, I provide some steps about public folder troubleshooting guide for your reference: Exchange General FAQ2 (11. How to troubleshoot public folder replication issue?) http://social.technet.microsoft.com/Forums/en-US/exchangesvrgeneral/thread/f0e81ab0-99f0-46db-b1aa-83511a3af427 Rock Wang Rock Wang MSFT

Thanks for this Rock.Can I just ask for some clarification on that workaround? Are you only supposed to do it if conditions 3 apply? This is not the case for us. Instead:- The 50% or so of PFs that are replicating are fine.- The other 50% do not replicate new content or old.- When I created a new PF it also did not replicate.My other question about the workaround - it says you have to copy from a root folder. All the PFs I am looking at are under a single root folder, so this will mean copying all 160 of them, and 6Gb of data. I don't want to embark on this unless there is a good chance of success as we'll basically have to take the whole system down, including the PFs that are replicating fine.I tried the workaround on a single PF, but it still won't replicate the content. It replicates the heirarchy only.Carolhttp://www.wapshere.com/missmiis

The copied PFs are now replicating, so it looks like that is the solution.Thanks Arun and Rock, Carolhttp://www.wapshere.com/missmiis

Glad to help Carol, and Hey Rock "Solid Plan" :).Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3

I have the exact same issue at work. I am not a public folder guru and therefore I do not quite understand some of the terminology in this thread. Rock, when you wrote the resolution: The following workaround can be done to resolve the folder that is not replicating. 1) Create a new top level public folder called 'Public Folder Recovery'. 2) Select a root level public folder that is not replicating. 3) Right click on the selected folder, then select the option to MOVE the folder (and all of its subfolders) into the new 'Public Folder Recovery' folder. 4) Right click on the moved folder under the 'Public Folder Recovery' folder, then choose COPY to copy it back to the root of the tree. 5) Add your content replicas to the copied folder 6) Wait for replication to occur. I understand creating a top level public folder. Basically, to me this just means create a new folder. In Step 4, what do you mean by "COPY it back to the root of the tree." ? What is the root of the tree? Does this mean copy it back to the original location of the Public Folder? Which could be beneath another Public Folder? Then what do you mean by "Add your contect replicas to the copied folder." ? From what I have seen, when we copy it back to the origincal location, it just copies the folder back and not the content itself. If you or someone else can clarify these steps in simple terms, it would be a great help to me. Thanks,