One of our new Exchange 2007 mailbox servers is giving below error every 45 minutes in app log. We have Exchange 2003 & 2007 in coexistence environment. Event Type: Error Event Source: MSExchangeFBPublish Event Category: General Event ID: 8207 Date: 5/18/2008 Time: 10:00:32 PM User: N/A Computer: <ServerName> Description: Error updating public folder with free/busy information on virtual machine <ServerName>. The error number is 0x80004005. I checked kb945602 and found that one of the free busy system folders of old admin group was not having any replica so I added one of the public folder replica of exchange 2003 and one of exchange 2007 but still error is coming on server. None of the users free busy information is pointing to that free busy system folder so only Exchange 2007 server is getting this error every 45 minutes. Can anyone give some clue to solve this?

Hi, Please run Netsh int ip set chimney DISABLED to disable it to see whether the problem persists. BTW,pleaseprevent your Anti-Virus programfrom scanningmadfb.dll Event 8207 is logged after you remount the public information store http://support.microsoft.com/kb/327336/en-us Scalable Networking: Network Protocol Offload - Introducing TCP Chimney http://www.microsoft.com/whdc/device/network/TCP_Chimney.mspx Hope it helps. Xiu

Thanks for your response Xiu. I just verified below two points which you suggested. We disabled Chimney, TCPA & RSS during setup of server since those have some issue with exchange. We have bin dir of Exchange excluded from antivirus scanning. Any other clue would be really appreciated. Edit : Just checked KB327336, This Exchange 2007 server rebooted during last weekend after windows security patch installation. It says, this problem may also occur if a replica for the Schedule+ Free/Busy folder does not exist on any server in the Exchange organization, for that I followed KB945602 and found one folder without replica so I added it earlier and now there isnt any Free/Busy folder without replica.

Hi, You may try to run EXBPA tool to have a health check. Then check the report it generates to see whether any related error logged there. Best regards, Xiu

Hi Xiu, Thanks for the suggestion. ExBPA report looks clean with few non related warnings for older storage drivers and an error for a blank database which is never backed up.