You are currently offline, waiting for your internet to reconnect

A rule to copy a message from the Inbox to a subfolder does not work after you register a synchronous store event sink in Exchange 2000 Server

This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
After you register a synchronous store event sink on your Inbox folder, a rule that you configured to move a copy of a message from the Inbox to a subfolder does not work. Additionally, all the following events are logged in the application event log of Event Viewer:

Event Type: Warning
Event Source: MSExchangeIS Mailbox Store
Event Category: Rules
Event ID: 1033
Description:The rule (#Rule Name#) with sequence number 10 is being ignored because it is disabled.The distinguished name of the owning mailbox is user1.Database "First Storage Group\Mailbox Store (SERVER)".

Event Type: Information
Event Source: MSExchangeIS Mailbox Store
Event Category: Rules
Event ID: 1037
Description:Triggering the rule (rule) with sequence number 11.The distinguished name of the owning mailbox is user1.Database "First Storage Group\Mailbox Store (SERVER)".

Event Type: Information
Event Source: MSExchangeIS Mailbox Store
Event Category: Rules
Event ID: 1042
Description:Attempting to perform action 0 in rule ID 1-3C02. The type of action is Copy.

Event Type: Error
Event Source: MSExchangeIS Mailbox Store
Event Category: Rules
Event ID: 1040
Description:The rule (rule) with sequence number 11 is being disabled due to errors encountered while applying the rule.The distinguished name of the owning mailbox is ---.Database "First Storage Group\Mailbox Store (SERVER)".

This problem occurs in the following scenario:
  • You register a synchronous store event sink on your Inbox folder to modify the subject of new incoming messages.
  • You configure a rule that moves a copy of a message to a subfolder if the message meets a certain condition. For example, the rule might move a copy of the message to a subfolder if your name is in the To line or in the Cc line of that message.
In this scenario, the synchronous store event sink runs successfully, but the rule that you have configured to copy the message to a subfolder does not work.

Note This problem only occurs if you create a rule to copy the messages that meet the condition. This problem does not occur if you create a rule to move these messages.
RESOLUTION

Hotfix information

To resolve this problem, obtain the August 2004 Exchange 2000 Server Post-Service Pack 3 update rollup.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
870540 Availability of the August 2004 Exchange 2000 Server Post-Service Pack 3 update rollup

Prerequisites

Because of file dependencies, this update requires 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

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

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   --------------------------------------------------------------   04-Mar-2004  18:52  6.0.6573.0      3,919,872  Cdoex.dll           16-Feb-2004  16:08                     12,720  Ctrl_calendarview20.htc   16-Feb-2004  16:08                     91,631  Ctrl_calendarview20.js   04-Mar-2004  18:43  6.0.6573.0        856,064  Davex.dll           04-Mar-2004  18:43  6.0.6573.0         53,248  Davexpc.dll         04-Mar-2004  18:38  6.0.6573.0        131,072  Drviis.dll          04-Mar-2004  18:39  6.0.6573.0        577,536  Dsaccess.dll        04-Mar-2004  17:49  6.0.6573.0        184,320  Dscmsg.dll          04-Mar-2004  17:50  6.0.6573.0        962,560  Emsmdb32.dll        04-Mar-2004  18:42  6.0.6573.0      2,179,072  Ese.dll             04-Mar-2004  18:42  6.0.6573.0         40,960  Eseperf.dll         16-Feb-2004  16:13                      6,991  Eseperf.hxx   04-Mar-2004  18:42                    391,634  Eseperf.ini   04-Mar-2004  18:52  6.0.6573.0      3,579,904  Excdo.dll           04-Mar-2004  18:38  6.0.6573.0         94,208  Eximap4.dll         04-Mar-2004  18:39  6.0.6573.0        262,144  Exmime.dll          04-Mar-2004  17:24  6.0.6573.0        176,128  Exnntp.dll          04-Mar-2004  18:43  6.0.6573.0        143,360  Exodbesh.dll        04-Mar-2004  18:43  6.0.6573.0         57,344  Exodbpc.dll         04-Mar-2004  18:43  6.0.6573.0        200,704  Exodbprx.dll        04-Mar-2004  18:43  6.0.6573.0      2,179,072  Exoledb.dll         04-Mar-2004  18:36  6.0.6573.0         81,920  Exosal.dll          04-Mar-2004  18:38  6.0.6573.0         32,768  Expop3.dll          04-Mar-2004  18:39  6.0.6573.0         32,768  Exproto.dll         04-Mar-2004  18:43  6.0.6573.0        307,200  Exprox.dll          04-Mar-2004  17:51  6.0.6573.0        143,360  Exschema.exe        04-Mar-2004  18:44  6.0.6573.0        331,776  Exsmtp.dll          04-Mar-2004  17:53  6.0.6573.0        675,840  Exwform.dll         04-Mar-2004  17:25  6.0.6573.0        180,224  Exwin32.dll         04-Mar-2004  17:52  6.0.6573.0         40,960  Febecfg.dll         04-Mar-2004  18:38  6.0.6573.0         32,768  Iisif.dll           04-Mar-2004  18:40  6.0.6573.0        135,168  Iisproto.dll        04-Mar-2004  18:40  6.0.6573.0         61,440  Imap4be.dll         04-Mar-2004  17:56  6.0.6573.0        319,488  Imap4evt.dll        04-Mar-2004  17:53  6.0.6573.0        126,976  Imap4fe.dll         04-Mar-2004  18:38  6.0.6573.0        126,976  Imap4svc.dll        04-Mar-2004  18:39  6.0.6573.0         40,960  Jcb.dll             04-Mar-2004  17:24  6.0.6573.0         49,152  Mdbevent.dll        04-Mar-2004  17:44  6.0.6573.0      2,293,760  Mdbmsg.dll          04-Mar-2004  17:27  6.0.6573.0         32,768  Mdbrole.dll         04-Mar-2004  17:50  6.0.6573.0        909,312  Mdbsz.dll           04-Mar-2004  18:39  6.0.6573.0         24,576  Mdbtask.dll         04-Mar-2004  17:24  6.0.6573.0        151,552  Nntpex.dll          04-Mar-2004  18:35  6.0.6573.0         94,208  Peexch50.dll        04-Mar-2004  18:36  6.0.6573.0        413,696  Phatcat.dll         04-Mar-2004  18:38  6.0.6573.0         36,864  Pop3be.dll          04-Mar-2004  17:56  6.0.6573.0        303,104  Pop3evt.dll         04-Mar-2004  17:54  6.0.6573.0         24,576  Pop3fe.dll          04-Mar-2004  18:36  6.0.6573.0         73,728  Pop3svc.dll         04-Mar-2004  17:56  6.0.6573.0        163,840  Protomsg.dll        04-Mar-2004  18:39  6.0.6573.0        532,480  Reapi.dll           04-Mar-2004  18:38  6.0.6573.0      4,673,536  Store.exe           04-Mar-2004  17:53  6.0.6573.0      3,735,552  Wmtemplates.dll  
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
MORE INFORMATION
For additional information about the terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
XADM
Properties

Article ID: 834043 - Last Review: 10/26/2013 20:32:16 - Revision: 2.2

Microsoft Exchange 2000 Server Standard Edition, Microsoft Exchange 2000 Enterprise Server

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbqfe kbfix kbexchange2000presp4fix kbbug KB834043
Feedback