Event ID 14029 logged on Exchange 2010 with coexistence 2003

Going to need some more background on this. Has this worked before? Did you just do a migration from an older Exchange software such as 2003? Did you just decommission an Exchange server?

for me it looks someone have removed self replica or deleted public folder through ADSIEDIT

This is fresh install of 2010 coexistent with 2003. 2003 not decomission and plan on stay for while.

Thanks

It sounds like you need to set 2010 as a Replica Server for all your Public Folders. Check this article here towards the very bottom.
https://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010/

Follow that article. When I setup replication from 2003 it works fine.
When on the 2010 and add server to replication tab then select update content get following error:

--------------------------------------------------------
Microsoft Exchange Error
--------------------------------------------------------
Action 'Update Content' could not be performed on object '/o=Solve Limited/cn=addrlists/cn=oabs/cn=Default Offline Address List'.

/o=Solve Limited/cn=addrlists/cn=oabs/cn=Default Offline Address List
Failed
Error:
Server 'MARS' doesn't have a replica of public folder '\NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK\/o=Solve Limited/cn=addrlists/cn=oabs/cn=Default Offline Address List'. Public folder content can be synchronized only from a server that has a replica of that public folder.




--------------------------------------------------------
OK
--------------------------------------------------------


I think this is the error that is logged on the application log.

I think if memory servers, Exchange 2010 has created its own OAB. You need to identify which one that was and just set the replication on it, to go back to the 2003 server. In essence you are sending each servers OAB files in the other servers direction. Same for the Schedule+ and Free/Busy information.

I have moved the OAB generator to the new server. How would be possible to see which one is that?

Issue resolved after reboot the server.