You cannot create a new Offline Address Book in a Hosted Message and Collaboration environment

This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
In a multiple-tenant hosting environment such as Microsoft Hosted Messaging and Collaboration (HMC), each hosted tenant is configured to use only one Offline Address Book (OAB). Therefore, you must generate an OAB for each tenant on HMC 4.5 or on HMC 4.0. However, new OABs are not generated or Public Folder Hierarchy replication may not be successful. When this behavior occurs, the following events are logged:
Event Type: Error Event Source: MSExchangeIS Public Store Event ID: 3079 Description: Unexpected replication thread error 0x3f0 on database " <Storage Group> /		  <Public Folder Store> ". EcLoadBinary REPL::EcSetPropCnsetSeen REPL::EcSetProp EcUnpackStatus EcReplMessageUnpack FReplRcvAgent
Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 9669 Description: Failed to create a new replica identifier for database " <Storage Group> / <Public Folder Store> " because the number of replica identifiers reached the quota limit (<Number>). User attempting to create the replica identifier: " <Replid> " 
Cause
This problem occurs because the maximum number of OABs that can exist in HMC is limited by the architecture of public folders. Specifically, the Replication ID limit is 32,768. Additionally, each OAB that you create consumes one Replication ID in the public folder hierarchy. Therefore, when you exhaust all the Replication IDs in the database, new OABs are not generated, or public folder hierarchy replication may not be successful.
Resolution
When you exhaust all the Replication IDs, you must reduce the number of OABs to less than 20,000. Additionally, all the public store databases must be rebuilt. To do this, follow these steps:
  1. Reduce the number of OABs to fewer than 20,000.
  2. If you have non-OAB public folder content, make arrangements to move it to a non-Exchange data store such as a .pst file.
  3. Unmount all the Public Store databases in the organization.

    Note
    If any Public Store databases remain online, the whole process will fail.
  4. Delete the physical files that are associated with the Public Store databases.
  5. Mount the public store databases to re-create the database files.
  6. Restore the public folder content from External Store.
  7. Update the existing OABs, and then rebuild them by using Exchange Administrative Tools.
More information
The problem is not specific to HMC 4.5 or to HMC 4.0. However, HMC customers are more likely to create many OABs. This problem also occurs when you create more than 32,768 Public Folder-based OABs in any version of Exchange Server.

You may also experience the Replication ID problem on an Exchange Server 2007 server. For more information about this problem, visit the following Microsoft Web site:

For more information about how to resolve the Named Properties problem or the Replication ID problem on an Exchange database, visit the following Microsoft Web site:

For more information about HTTP offline address books, click the following article number to view the article in the Microsoft Knowledge Base:
972272 A new download method is available for HTTP offline address books on Exchange Server 2007 servers that has the Client Access Server role installed
For more information about public folder hierarchy replication, click the following article number to view the article in the Microsoft Knowledge Base:
969487 A Public Folder Hierarchy replication fails, and then event errors 3079 and 9669 occur in Exchange Server 2007
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Properties

Article ID: 977990 - Last Review: 10/25/2013 23:10:00 - Revision: 3.0

Microsoft Solution for Hosted Messaging and Collaboration 4.5, Microsoft Solution for Hosted Messaging and Collaboration 4.0

  • kbnosurvey kbarchive kbsurveynew kbexpertiseinter kbexpertiseadvanced kbtshoot KB977990
Feedback