I shoulda remembered that. ☹ From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Kennedy, Jim Sent: Friday, June 3, 2016 10:41 AM To: exchange@lists.myitforum.com Subject: [Exchange] RE: Broke public folder replication.
So, I dismounted and recreated the PF database on 02. No joy. Then I went into ADSI Edit and hit the left over Exchange 2003 Administrative Group and deleted the empty servers folder and blammo…replication instantly fixed itself. From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Kennedy, Jim Sent: Tuesday, May 31, 2016 10:27 AM To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com> Subject: [Exchange] RE: Broke public folder replication. So, still nothing is replicating properly from MBX02 to 01. I am thinking dismount the bad database on MBX02, then move the files. Then remount and let it recreate. Does that sound like a logical plan? From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Kennedy, Jim Sent: Friday, May 27, 2016 9:52 AM To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com> Subject: [Exchange] Broke public folder replication. I suspect this is from my DC hardware upgrade, the timing it too much of a coincidence. When I decommissioned the last of the old DC’s it triggered the below for a few days before I saw it and bounced the Exchange servers. SACL Watcher servicelet encountered an error while monitoring SACL change. Got error 1722 opening group policy on system OldDC.Domain.LOCAL in domain …….. Exchange 2010, one hub and two mbx servers. Current on SP’s and rollups. Public folders are all calendars and within the last 4 or 5 days replication has gone away. A close as I can tell some flow is working. New items from MBX01 to MBX02 is broke…but new items created on MBX02 do flow to MBX01. So I real quick flipped everyone over to MBX01 for their public folders. I know I could delete the DB on 02 and recreate but would rather fix the issue. Logging is cranked up and all I am getting are the usual phantom 3093’s. Not sure what to try next to get it going again.
