Article ID: 815417
Article Last Modified on 10/26/2006
APPLIES TO
- Microsoft Exchange 2000 Server Standard Edition
SYMPTOMS
Clients cannot connect to the information store. One or more of the following events are recorded in the application event log:
Event Type: Error
Event Source: ESE
Event Category: Transaction Manager
Event ID: 623
Computer: Computer_Name
Description: Information Store (3524) 23f6e44f-dd32-4f25-aff7-8af40e5904bb: The version store for this instance (3) has reached its maximum size of 155Mb. 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: 0xBFE49020
Session-context: 0x00000000
Session-context ThreadID: 0x00001350
Event Type: Error
Event Source: ESE
Event Category: Transaction Manager
Event ID: 623
Computer: Computer_Name
Description: Information Store (3524) 26ed7c47-1467-4e1b-9798-c12dbdd5f3dd: The version store for this instance (1) has reached its maximum size of 155Mb. 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: 0xBFE40C20
Session-context: 0x00000000
Session-context ThreadId: 0x000017E8
WORKAROUND
To work around this issue, restart the Information Store service.
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends 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 fix. For a complete list of Microsoft Product Support Services phone 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 typical 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 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 -------------------------------------------------------------- 03-Jun-2003 22:46 6.0.6472.0 3,915,776 Cdoex.dll 03-Jun-2003 22:40 6.0.6472.0 827,392 Davex.dll 03-Jun-2003 22:38 6.0.6472.0 577,536 Dsaccess.dll 03-Jun-2003 21:47 6.0.6472.0 184,320 Dscmsg.dll 03-Jun-2003 22:46 6.0.6472.0 3,575,808 Excdo.dll 03-Jun-2003 22:38 6.0.6472.0 258,048 Exmime.dll 03-Jun-2003 22:40 6.0.6472.0 2,138,112 Exoledb.dll 03-Jun-2003 22:36 6.0.6472.0 81,920 Exosal.dll 03-Jun-2003 22:40 6.0.6472.0 307,200 Exprox.dll 03-Jun-2003 21:39 6.0.6472.0 49,152 Mdbevent.dll 03-Jun-2003 22:08 6.0.6472.0 2,285,568 Mdbmsg.dll 03-Jun-2003 21:41 6.0.6472.0 32,768 Mdbrole.dll 03-Jun-2003 22:38 6.0.6472.0 24,576 Mdbtask.dll 03-Jun-2003 22:37 6.0.6472.0 4,648,960 Store.exe
Note Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 3 (SP3). For additional information about how to obtain the latest Exchange 2000 Server service pack, 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 problem in Microsoft Exchange 2000 Server.
Keywords: kbhotfixserver kbqfe kbqfe kbfix kbexchange2000presp4fix kbbug KB815417
