Comments on: Exchange 2007 Event 8207 MSExchangeFBPublish Finally Fixed

By: Todd Walters

Todd Walters — Tue, 13 Oct 2009 20:57:47 +0000

Jason,
I just want to thank you for your article I had the exact same scenario and had been searching for a solution when i came here. This is the last problem that i had to iron out after my conversion. Again thank you worked like a charm.

By: Neil Hunter

Neil Hunter — Wed, 16 Sep 2009 20:38:38 +0000

Thanks for this info, it worked a treat!

I started to get 8207 error on all of my Exchange 2007 servers roughly 3 weeks after transitioning my final site to Exchange 2007. Of all of the different fixes I’ve seen and tried this is the only one that has worked. In my case though i had to set a replica on every server in Exchange Administrative Group (FYDIBOHF23SPDLT)…something that MS doesn’t recommend. After talking to MS premier support they agreed that in my instance it was needed after all.

By: Darwin

Darwin — Thu, 26 Mar 2009 20:20:37 +0000

I have been unable to resolve the Event Id 8207. I spoke with Microsoft yesterday and we created a new Public Folder to use since it appeared the Public Folders did not migrate properly through teh answer file during the migration process. Luckily the users and the store are not affected, the server just generates 22 errors per day with the FREE BUSY event. My stores are mounted and this appears to be the only event left over from the migration. Perhaps someone out there knows how to address through ASDI Edit.

By: Darwin

Darwin — Fri, 27 Feb 2009 14:57:09 +0000

Jason, I stumbled across your excellent article trying to solve a very similiar problem of my own. I have not, to date, been successful in addressing this event. Usually the cmdlet returns an error ( I also went to Aaron’s post first) at the FREE BUSY portion of the command. I am using the Exchange Shell to do this. If I post my version of the 2 cmdlets would you be willing to verify my syntax? Thanks in advance.

P.S. This was an SBS 2003 to SBS 2008 migration using the answer file. Everything else went real smooth except for the Public Folders which now have their own Storage Group.