E-mail client users experience a decrease in performance, and event 623 is logged when you receive a large message in Exchange Server 2003 (911836)



The information in this article applies to:

  • Microsoft Exchange Server 2003 Enterprise Edition
  • Microsoft Exchange Server 2003 Standard Edition

SYMPTOMS

When you receive a large e-mail message in a Microsoft Exchange Server 2003 organization, you experience the following symptoms:
  • E-mail client users experience a decrease in performance.
  • Exchange Server 2003 stops responding until you perform one or both of the following actions:
    • Restart the Microsoft Exchange Information Store service
    • Remove the large e-mail message from the message queue
  • The following event is logged in the Application log:Event Type: Error
    Event Source: ESE
    Event Category: Transaction Manager
    Event ID: 623
    Description: Process_Name (PID) The version store for instance instance> ("name") has reached its maximum size of valueMb. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back. Possible long-running transaction: SessionId: value Session-context: value Session-context ThreadId: value
These symptoms may occur again when you receive the next large message.

CAUSE

This problem occurs when Exchange Server 2003 receives a large, corrupted MIME message. For example, a 10-megabyte (MB) MIME message may cause this problem. When Exchange Server 2003 tries to convert the corrupted message from MIME format to MAPI format, the version store runs out of memory.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Exchange Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

836993 How to obtain the latest service packs for Exchange Server 2003

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 Microsoft Exchange Server 2003 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.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart the computer after you apply the 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 file attributes) 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.
File nameFile versionFile sizeDateTimePlatform
Exmime.dll6.5.7233.62202,24007-Dec-200503:39x86

WORKAROUND

To work around this problem, you can set the message size limits for an organization. To do this, follow these steps:
  1. Start Exchange System Manager.
  2. Expand Global Settings, right-click Message Delivery, and then click Properties.
  3. Click the Defaults tab.
  4. Under Sending message size, click Maximum (KB). Then, type the size that you want, in kilobytes (KB). For example, type 10240 to set a limit of 10 MB.
  5. Under Receiving message size, click Maximum (KB). Then, type the size that you want, in kilobytes (KB). For example, type 10240 to set a limit of 10 MB.

STATUS

This problem was first corrected in Microsoft Exchange Server 2003 Service Pack 2.

MORE INFORMATION

The version store is memory that is reserved for outstanding transactions. Exchange Server 2003 stores all the operations of incomplete transactions in the version store. If anything delays the transactions from being completed, the version store fills up. The version store then stops generating additional transactions. This problem lasts until the outstanding transactions are cleared. Usually, the version store recovers by itself. However, the users cannot work in the interim. Additionally, the version store will not accept or deliver new messages. For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

817903 New naming schema for Exchange Server software update packages


Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbQFE kbfix kbBug kbpubtypekc KB911836 kbAudITPRO