Chat random 1on1 - Msexchangefbpublish error updating public folder
The mailbox database was then re-created and the journal mailboxes moved back. Summary : something strange must have happened when the original mailbox database was created.
Not the technical solution that some would want, but hey, it fixed it nonetheless!
I guess it is back to perusing the forums to see if anyone else has encountered this as well.
Now, there are a ton of Internet posts on this particular error.
This resulted in Outlook 2003 clients unable to see Free/Busy information when creating a meeting request.
The user would see this error in Outlook when attempting to see another users schedule: Event Type: Error Event Source: MSExchange FBPublish Event Category: General Event ID: 8207 Date: 8/05/2007 Time: PM User: N/A Computer: EXCHSVR Description: Error updating public folder with free/busy information on virtual machine exchsrvr. After a bit of digging around, it occurred to me that I’d missed adding the new server to the Public Folder replicas.
The error number is 0x80070005." Ironically, the free busy information seems to be available for shared calendars (both Outlook 2003 & 2007).
The autodiscover service seems to working properly; all test succeed. I was able to get rid of this in my Exchange 2007's application event log by dismounting and then remounting the Public Folder Database under Mailbox in Server Configuration.
So, why on earth would a mailbox server be reporting this error relating to free/busy public folders?
To cut a long solution short, the journal mailboxes were moved to another server temporarily and the mailbox database deleted.
If you use ADSI Edit or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, serious problems may occur.Tags: Adult Dating, affair dating, sex dating