Microsoft KB Archive/898785

= Public folder replication fails, and event IDs 3086 and 3085 are logged with error code 0x8007000e in Exchange 2000 Server =

Article ID: 898785

Article Last Modified on 11/2/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition
 * Microsoft Exchange 2000 Enterprise Server

-





SYMPTOMS
You may experience the following symptoms on a server that is running Microsoft Exchange 2000 Server:  Public folder replication fails. For example, when content is added to a public folder or when public folder content is modified on the affected Exchange server, the additions or modifications are not replicated to other Exchange servers in your organization.  If you increase diagnostic logging settings for public folder replication operations, the following events are logged in the Application event log:

Event ID: 3086 Event ID: 3086

Event Category: Replication Errors

Event Source: MSExchangeIS Public Store

Event Type: Warning

Computer:

Description: Error 0x8007000e occurred while generating an outgoing replication message. Event ID: 3085 Event ID: 3085

Event Category: Replication Errors

Event Source: MSExchangeIS Public Store

Event Type: Warning

Computer:

Description: Error 0x8007000e occurred while generating an outgoing replication message. 

For more information about how to increase diagnostic logging in Exchange 2000 Server, click the following article number to view the article in the Microsoft Knowledge Base:

842273 How to troubleshoot public folder replication problems in Exchange 2000 Server and in Exchange Server 2003



CAUSE
This issue occurs if Exchange 2000 Server runs out of a particular MAPI Property ID that is known as a named property.

Note Named properties are also known as named props.

Event ID 3086 and event ID 3085 replication warning events may be logged for several reasons. Each reason is distinguished by a particular error code. Error code 0x8007000e that appears in the warning events that are mentioned in the &quot;Symptoms&quot; section corresponds to the following error code message:

MAPI_E_NOT_ENOUGH_MEMORY

This error code indicates that MAPI has run out of property IDs.



WORKAROUND
To work around this issue, follow these steps:
 * 1) Save the public folder content from the affected Exchange server to one or more personal folders (.pst) files.
 * 2) Remove and then re-create the public folder store on the affected Exchange server.
 * 3) Allow for the public folder store to replicate public folder content from the other public folder servers in your organization. This process is known as backfilling.

For more information about how to troubleshoot public folders in Exchange 2000 Server, visit the following Microsoft Web site:

http://technet.microsoft.com/en-us/library/ac7d1fe3-bbc7-4723-bdb5-5cff59f11ef9.aspx



MORE INFORMATION
The MAPI specification defines the following two kinds of properties:
 * Standard MAPI properties
 * Named properties (also known as named props)

A named property is a custom property that is known by the property's name instead of by a coded ID. The MAPI specification defines many property tags. However, the MAPI specification also lets vendors extend the defined MAPI property set by creating their own properties or by publishing the property type together with a string value or with a numeric value.

To perform a Get operation or a Set operation on a named property, a client or a service provider must ask the object on which the Get or Set properties call is made to create an ID that corresponds to the published property name. In this situation, only the property name is fixed. The ID is dynamically created. The ID for the named property must be produced by the service provider. The service provider must maintain an internal map of property names to property IDs. The range for named properties is 0x8000 to 0xFFFF. This range gives a service provider an effective range of 32,766 possible entries from which to allocate IDs and from which to return those IDs to the requesting client.

The Exchange information store uses named properties and property IDs for tasks such as processing SMTP X-headers and DAV properties that are not well known.

Note SMTP-X headers are custom headers that programs and companies use. For example, if you send a message to a public folder, and that message has an X-spam-confidence level SMTP-X header that your company uses, a named property is created. SMTP-X headers differ from standard SMTP headers such as To, From, Date, and so on.

Exchange 2000 Server has a limit of 32,766 property IDs for each messaging database. If you use many named properties, this limit may be reached over time. After the limit of 32,766 property IDs is reached, Exchange 2000 Server cannot assign any more property IDs. Therefore, you must save the public folder content from the affected server, and then remove and re-create the public folder store.

Microsoft Exchange Server 2003 lets you set lower quota limits for property IDs. This functionality gives you more flexibility in case you experience this issue. By setting the property ID values to a lower limit, you can receive earlier notification about the depletion of property IDs. Therefore, you can take action before the range of property IDs is exhausted. For more information about how to set quota limits for named properties in Exchange 2003, click the following article number to view the article in the Microsoft Knowledge Base:

820379 How to configure quota settings for named properties and for replica identifiers in Exchange Server 2003

For more information about how to troubleshoot public folder replication issues, click the following article number to view the article in the Microsoft Knowledge Base:

842273 How to troubleshoot public folder replication problems in Exchange 2000 Server and in Exchange Server 2003

For more support information for Exchange 2000 Server, visit the following Microsoft Web site:

http://technet.microsoft.com/en-us/exchange/bb330828.aspx

Additional query words: XADM

Keywords: kbeventlog kbtshoot kbprb KB898785

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.