Microsoft KB Archive/821930

= A public folder rule with more than six recipients does not replicate =

Article ID: 821930

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



SYMPTOMS
When you create a rule that has more than six recipients in a public folder, the rule may not replicate to replicas of this folder that are on other servers in your organization. The following events may be found for the folder that contains the rule in the application log on the servers where the rule has not replicated: Event Type: Information

Event Source: MSExchangeIS Public Store

Event Category: Replication Incoming Messages

Event ID: 3025

Description:

An incoming replication message was processed.

Type: 0x4

Message ID: 1-7E4C

Folder: (5-821) IPM_SUBTREE\< >\< >

Database &quot;First Storage Group\Public Folder Store &quot;. CN min: 5-1 CN max:5-795E

Server: /O=ORG/OU=AG/CN=CONFIGURATION/CN=SERVERS/CN=/CN=MICROSOFT PUBLIC MDB

Event Type: Warning

Event Source: MSExchangeIS Public Store

Event Category: Replication Errors

Event ID: 3089

Description:

Error 0x8004010f occurred while processing an incoming replication message on Public Folder Store &quot;First Storage Group\Public Folder Store &quot;.

Event Type: Error

Event Source: MSExchangeIS Public Store

Event Category: Replication Errors

Event ID: 3079

Date: 5/21/2003

Time: 3:36:19 PM

User: N/A

Computer:

Description:

Unexpected replication thread error 0x8004010f on database &quot;First Storage Group\Public Folder Store &quot;.

EcReplFolderMessagesUnpack

EcReplMessageUnpack

FReplRcvAgent 0x800401

0f = ecNotFound-MAPI_E_NOT_FOUND



Cumulative rollup information
To resolve this problem, obtain the September 2003 Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824282 September 2003 Exchange 2000 Server Post-Service Pack 3 Rollup

Hotfix information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Exchange 2000 Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date         Time   Version            Size    File name --  15-Jul-2003  23:00  6.0.6487.1      3,915,776  Cdoex.dll 15-Jul-2003 22:55  6.0.6487.1        851,968  Davex.dll 15-Jul-2003 22:55  6.0.6487.1         53,248  Davexpc.dll 15-Jul-2003 22:50  6.0.6487.1        577,536  Dsaccess.dll 15-Jul-2003 20:25  6.0.6487.1        184,320  Dscmsg.dll 15-Jul-2003 23:00  6.0.6487.1      3,575,808  Excdo.dll 15-Jul-2003 22:50  6.0.6487.1        258,048  Exmime.dll 15-Jul-2003 22:55  6.0.6487.1        143,360  Exodbesh.dll 15-Jul-2003 22:55  6.0.6487.1         57,344  Exodbpc.dll 15-Jul-2003 22:55  6.0.6487.1        200,704  Exodbprx.dll 15-Jul-2003 22:55  6.0.6487.1      2,174,976  Exoledb.dll 15-Jul-2003 22:48  6.0.6487.1         81,920  Exosal.dll 15-Jul-2003 22:55  6.0.6487.1        307,200  Exprox.dll 15-Jul-2003 20:28  6.0.6487.1        143,360  Exschema.exe 15-Jul-2003 20:29  6.0.6487.1        675,840  Exwform.dll 15-Jul-2003 20:17  6.0.6487.1         49,152  Mdbevent.dll 15-Jul-2003 20:36  6.0.6487.1      2,285,568  Mdbmsg.dll 15-Jul-2003 20:19  6.0.6487.1         32,768  Mdbrole.dll 15-Jul-2003 22:50  6.0.6487.1         24,576  Mdbtask.dll 15-Jul-2003 22:49  6.0.6487.1      4,648,960  Store.exe Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301378 How to obtain the latest Exchange 2000 Server service pack



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

Additional query words: kbExchange2000preSP4septbarFix XADM

Keywords: kbhotfixserver kbqfe kbqfe kbfix kbexchange2000presp4fix kbbug KB821930

-

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

© Microsoft Corporation. All rights reserved.