Hello,I've an exchange 2003 cluster with a particular public folder that's been around for years, no rules on it, no replicas and I started getting replication conflict messages in the last few weeks, only on this folder. With just one instance and no replicas, why would I get conflicts? I turned up diagnostic logging a bit and can see messages like this one:An item conflict occurred in public folder (1-346FD1) IPM_SUBTREE\TicketsMessage ID: 1-177D730 From: --- Subject: (removed) Received: 2/17/2010 3:05:15 PM Database "First Storage Group\Public Folder Store (servername)". Notification(s): userlist Conflicts: 1-178E35F 2/17/2010 3:06:05 PM1-178E360 2/17/2010 3:06:05 PM1-178E362 2/17/2010 3:06:05 PMAre there any further diagnostics I can perform or steps to take to either determine why this is happening or simply shut something off to stop the issue?thanksPeter

What are the event IDs that you are seeing in the application logs?Chris cbfive.com

Application Event "MSExchangeIS Public Store" 3069 (the above conflict messages)Application Event "MSExchangeIS Public Store" 3092 (offline address book replication failure event)I probably should mention that my exchange org has 2 servers- one is online production, the second is a DR server with OS up but exchange services are all turned off. The DR server gets the exchange DBs, logs etc replicated to by XOsoft.I would guess the OAB replication errors might be from the second server being offline but the PF replication conflicts I'd think not since there are no replicas of the troubled folder.thanks

When you get this error message there could be a chance of a hierarchy change replicated to a server that had a hierarchy change which had not replicated out, the two changes are a design conflict. Or there could be two changes made quickly on two different servers (not in your case), or there are one or more servers out there that have had a replication problem for some time that have prevented them from replicating, and this latest change just happened to expose it and let you know. So there are some common reasons you will get this error message 1. This error could be generated because of normal maintenance (online maintenance) against the Public Folder database 2. Error because of replication 3. AV components such as client AV making MAPI calls or Exchange level AV processing old items after configuration changes 4. A virus that hits the database making changes and resulting in conflict messages 5. You have something like comvault in the environment that is changing PF data So what can you do 1. You can suppress these messages by modifying the registry of the Exchange server HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\<servername>\Public-<GUID of Public Store>On the Edit menu, click Add Value, and use the following entry:Value Name: Replication Folder Design Conflict DisableData Type: REG_DWORDValue: 1 2. Check the queue’s to ensure there is not Public Folder replication messages pending delivery (in your case I’m sure there are since you second Exchange server is offline) 3. Check Anti-Virus exclusion on the Exchange server (http://support.microsoft.com/default.aspx/kb/823166) or check for other events like 327 or any other event source MSExchangeTransport 4. For you the last option is try to turn on the other Exchange server and replication take place and see if the message goes away5. Ingore the alert since you know there is a replication error Chris cbfive.com

Thanks a lot Chris. I'lll look into it further with your suggestions and let you know how it works.I do have Symantec AV for Exchange as well as a compliance product (sherpa email attender) that might be getting in and messing around as you pointed out.We'll see...thanks again!

No Problem hope it helps. let me know how it works outChris cbfive.com

Any update?Chris cbfive.com