Article ID: 318162 - View products that this article applies to.
This article was previously published under Q318162
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
After you upgrade to Exchange 2000 Server Service Pack 2 (SP2), the Instant Messaging Service may stop responding to Instant Messaging client requests.
The following message may be logged in the Application event log:
Category Transaction Manager
Event ID 623
inetinfo (2824) The version store for this instance (0) has reached its maximum size of 1Mb. 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:
Session-context ThreadId: 0x000009A0
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378The English version of this fix has the following file attributes or later.
(http://support.microsoft.com/kb/301378/EN-US/ )XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Component: The Instant Messaging Service
Collapse this tableExpand this table
NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.
After you apply this fix, the default value for the MaxVerPages value is increased from 256 KB to 5 MB. After you apply this fix, you can also use the ESE version store to change to a higher value by using the DatabaseMaxVerPages registry value.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To add the DatabaseMaxVerPages value:
Contact us for more help
Connect with Answer Desk for expert help.