Article ID: 822427
Article Last Modified on 10/26/2006
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
SYMPTOMS
After you enable the JournalBCC registry key on a Microsoft Exchange 2000 Server computer so that blind carbon-copy recipients are recorded to a journal, you intermittently experience all the following symptoms:
- Message delivery is very slow.
- The Store.exe process uses a very high percentage of CPU resources.
- If you restart the Exchange 2000 computer, the problem is temporarily resolved, and mail flow is restored.
CAUSE
This problem occurs because the Exchange 2000 categorizer component may incorrectly set the property for recording blind carbon-copy recipients to a journal. In this scenario, Exchange 2000 might try to process multiple recipients at the same time when a message has both cached recipients and non-cached recipients. As a result, the journal that contains the blind carbon-copy recipients is corrupted.
Note This problem only occurs when you enable the JournalBCC registry key on the computer.
RESOLUTION
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 Microsoft 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:
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.
Component: Transport
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 -------------------------------------------------------------- 22-Jul-2003 19:39 6.0.6489.0 131,072 Drviis.dll 22-Jul-2003 19:43 6.0.6489.0 307,200 Exsmtp.dll 22-Jul-2003 19:36 6.0.6489.0 94,208 Peexch50.dll 22-Jul-2003 19:37 6.0.6489.0 397,312 Phatcat.dll 22-Jul-2003 19:40 6.0.6489.0 528,384 Reapi.dll 22-Jul-2003 19:43 6.0.6489.0 311,296 Resvc.dll
Note Because of file dependencies, this hotfix 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 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
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 how to enable the registry key that is discussed in this article, click the following article number to view the article in the Microsoft Knowledge Base:
810999 XADM: Bcc Information Is Lost for Journaled Messages in Exchange 2000
For additional information about the terminology that is used to describe Microsoft product 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
Additional query words: bcc journaling journalling
Keywords: kbhotfixserver kbqfe kbqfe kbfix kbexchange2000presp4fix kbbug KB822427
