The Microsoft Exchange Information Store Service may intermittently stop responding during database transactions and an event ID 623 message may be logged in Exchange 2000 Server (892396)



The information in this article applies to:

  • Microsoft Exchange 2000 Server

SYMPTOMS

On a computer that is running Microsoft Exchange 2000 Server, the Microsoft Exchange Information Store service may intermittently stop responding (hang) when it tries to update the mailbox table during a database transaction.

Additionally, the following event may be logged in the Application event log:
Event Type: Error
Event Source: ESE
Event ID: 623
Computer: computername
Description: Information Store (2048) The version store for instance 0 ("c49a179d-ac1f-4894-8211-0c2917d34500") has reached its maximum size of 108Mb. 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: 0x1B6525A0 Session-context: 0x00000000 Session-context ThreadId: 0x00000AF8

RESOLUTION

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 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.

Prerequisites

Because of file dependencies, this software update requires both the following packages:
  • Microsoft Exchange 2000 Server Service Pack 3 (SP3)

    For more 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

  • The August 2004 Exchange 2000 Server Post-Service Pack 3 update rollup

    For more 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

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, many Exchange 2000-related services are automatically stopped and then restarted when 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 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 item in Control Panel.
   Date         Time   Version            Size    File name
   --------------------------------------------------------------  
   25-Mar-2005  13:19  6.0.6617.58     2,342,912  Mdbmsg.dll       
   25-Mar-2005  14:12  6.0.6617.58     4,706,304  Store.exe        

Hotfix installation information

After you install this hotfix, the LookupAccountSid function call is moved outside the database transaction. Therefore, after you install this hotfix, Exchange 2000 is less affected if the Lsass.exe process on a domain controller responds slowly or does not respond at all.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Modification Type:MajorLast Reviewed:5/25/2006
Keywords:kbQFE KBHotfixServer kbfix kbExchange2000preSP4fix kbbug KB892396 kbAudITPRO