Article ID: 2847591 - View products that this article applies to.
Not sure what release of Office 365 you're using? Go to the following Microsoft website:
Am I using Office 365 after the service upgrade?
You have a hybrid deployment of on-premises Microsoft Exchange Server and Microsoft Exchange Online in Microsoft Office 365, and the following conditions are true:
This issue occurs if Exchange 2003 cannot refer Outlook to the Exchange 2010 public folder server that contains the replica. Although an Exchange 2010 server is specified in the custom list for public folder referrals, the cost calculation fails. When the Exchange 2010 server is selected in the public folder referral custom list from the Exchange 2003 Management System, the public folder database is displayed instead of the server.
Exchange 2003 incorrectly resolves the Exchange 2010 server in the list of public folder referrals to the GUID of the Exchange 2010 public folder database instead of the GUID of the Exchange 2010 public folder server. When Exchange 2003 looks up the database GUID to assign cost, it's not a valid server path. Therefore, it's marked with an infinite cost. Because the cost is infinite, Exchange 2003 doesn't refer the client to the Exchange 2010 server.
To resolve this issue, use Active Directory Service Interfaces Editor (ADSI Edit) to modify the msExchfolderAffinityList attribute on the server that is running Exchange 2003. Specifically, replace the GUID of the Exchange 2010 public folder database with the GUID of the Exchange 2010 public folder server.
To do this, follow these steps on the server that is running Exchange 2003.
The msExchfolderAffinityList attribute is the Active Directory property that resolves the custom list for public folder referrals to server GUIDs.
For more information, see the following Microsoft resources:
Still need help? Go to the Office 365 Community
Article ID: 2847591 - Last Review: May 20, 2013 - Revision: 2.0