Article ID: 955443 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
In a Microsoft Exchange Server 2003 and Exchange Server 2007 coexisting environment, some free/busy messages are not successfully replicated from Exchange 2007 servers to Exchange 2003 servers after some mailboxes are migrated from an Exchange 2003 server to an Exchange 2007 server. Therefore, the updated free/busy messages of those migrated users are not available on the Exchange 2003 server. Additionally, the following error is logged in the application event log on the Exchange 2003 server.
Event Type: Error Event Source: MSExchangeFBPublish Event Category: General Event ID: 8207 Description: Error updating public folder with free-busy information on virtual machine <server name>. The error number is 0x80070057.
To resolve this problem, install Update Rollup 6 for Exchange 2007 Service Pack 1.
For more information about Update Rollup 6 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic:
Description of Update Rollup 6 for Exchange Server 2007 Service Pack 1For more information about how to obtain the latest Exchange service pack or update rollup, see the following Exchange Help topic:
How to Obtain the Latest Service Pack or Update Rollup for Exchange 2007
If you run the MFCMapi.exe tool against the Exchange 2003 server, and then you click the free/busy message, the same 0x80070057 error number appears. The 0x80070057 error number corresponds to the MAPI_E_INVALID_PARAMETER error code. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
238119To download the MFCMapi.exe tool, visit the following Web site:
(https://support.microsoft.com/kb/238119/ )List of Extended MAPI numeric result codes
http://www.microsoft.com/downloads/details.aspx?FamilyID=55FDFFD7-1878-4637-9808-1E21ABB3AE37&displaylang=enFor more information about how to use Microsoft Exchange Server MAPI Editor, visit the following Web site:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 955443 - Last Review: January 15, 2015 - Revision: 3.0