I am getting the following event logged every 5 minutes in my event log: Event ID 3092 Source: MSExchangeIS Public Store Catagory: Replication Errors Error 1129 occurred while processing a replication event. Folder: (5-AFD2) NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK\EX:/o=Sell-Thru Services/ou=STS_DOMAIN\OAB Version 2 For more information, click http://www.microsoft.com/contentre This is a W2K3 Sp1 server with E2k3 SP2 on it. I did a disaster recover on this machine 6 months ago, and had to rebuild it from scratch, then importing the information stores. This is a back-end server, and I have another box that also has OWA on it. I put this on about 2 months ago. The one oddity i see is that there seem to be 2 OAB Version 2 folders. First one is /NON_IPM_SUBTREE/OFFLINE ADDRESS BOOK//o=Sell-Thru Services/cn=addrlists/cn=oabs/cn=Default Offline Address List/OAB Version 2/ Second one is: /NON_IPM_SUBTREE/OFFLINE ADDRESS BOOK/EX:/o=Sell-Thru Services/ou=STS_DOMAIN/OAB Version 2/ The second one doesn't appear to have any information in it, while the first one appears to have 217 items in it. Both have the name OAB Version 2 for the name. Thanks for the help. Dennis

does ExBPA complain about system folders are missing? http://support.microsoft.com/kb/822444/en-us

Nothing appears to be missing, and I'm not getting any logs indicating they are. Again I find it odd that i have 2 of these same folders, though only one has any data in it.

If you look at the folder properties, what replicas do you see? also found this http://support.microsoft.com/?kbid=936000

On both of the OAB2 the Always Run and Urgent are set. The only difference in all the set up I see is the following: /NON_IPM_SUBTREE/OFFLINE ADDRESS BOOK/EX:/o=Sell-Thru Services/ou=STS_DOMAIN/OAB Version 2/ /NON_IPM_SUBTREE/OFFLINE ADDRESS BOOK//o=Sell-Thru Services/cn=addrlists/cn=oabs/cn=Default Offline Address List/OAB Version 2/ I have no Exchange 2007 in my system, and honestly not sure why it's replicating at all, unless it's to my FE server. I only have one be server and one fe server. Thanks Dennis

has there been any other Exchange servers in the system before.

There was another system that i did a disaster recovery onto the current BE server. (the one with the errors). That system crashed and we had to restore from backups. (I even named the computers the same name) I havea FE server for OWA only, currently on the system. None of these are or have been 2007, they are all 2003. Thanks

did you use the same computeraccount in AD? if you created a new computeraccount it wont have the correct permissions.

I followed the Microsoft whitepage that told me to reset the computeraccount then to logon with the new server.

We had the exact same problem with our environment: Same warnings every 5 minutes on the back-end server and also referring to OAB version 2 folder. We also had similarly two of these OAB version 2 folders which of one was totally empty. The log messages were in fact relating to the empty OAB folder. When I was going through these folders with System Manager I noticed that I'm getting an c1038a21 error message when I try to access properties window of the non-empty OAB folder. I found a kb article http://support.microsoft.com/kb/328740 describing this and method2 fix worked for us: I mail disabled and re-enabled this OAB folder and the error message was gone.After this I simply deleted the empty OAB-folder that originated the log warnings and that was it. Warnings are now gone and everything works fine.

Hi Chillybean, Your mentioned link "http://support.microsoft.com/kb/328740 " doesn't work. Any other solution. Because I am also facing the same problem. One more thing, I am fearing to install the hotfixes on my exchange server which is described at http://support.microsoft.com/?kbid=936000 Thanks Shambhu Sharma

Hi, This problem occurs when messages in the Exchange Server 2003 public store include date properties that are set to zero. When date properties are set to zero, the date is displayed as Jan 1, 1601 in Exchange Server 2003. When the server that is running Exchange Server 2007 replicates the public folder that includes these messages, the replicated messages contain random data in the date properties. Therefore, Exchange Server 2007 determines that these messages are invalid, and it drops them. for referance : http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=6.5.6940.0&EvtID=3092&EvtSrc=MSExchangeIS+Public+Store&LCID=1033Dinesh S.