Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Information Store Dismounts and Stops


View products that this article applies to.

This article was previously published under Q288700

↑ Back to the top


Symptoms

The information store dismounts and starts referencing "version store" errors similar to the following event:
Event ID 623

Information Store (2356) The version store for instance 0 ("ca192ae5-ad76-478e-8530-0b1756e7d28d") has reached its maximum size of 85Mb. 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: 0x111006E0
Session-context: 0x00000000
Session-context ThreadId: 0x00000B64
The Application log may also contain a series of MSexchangeIS events (#1022) and MSexchangeSA events (#9175).

↑ Back to the top


Cause

When the Write Disk Caching (write-back caching on the hard drive) option is enabled for performance reasons, the Exchange server may encounter a JET or information store dismount and crash.

↑ Back to the top


Resolution

Restart the computer, and then disable the Write Disk Caching option. Write-back caching on a disk controller is acceptable so long as the controller has a battery backup; however, write-back caching on a physical disk can lead to JET-related issues in Exchange 2000.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server and Microsoft Exchange Server 2003.

↑ Back to the top


Keywords: KB288700, kbpending, kbbug

↑ Back to the top

Article Info
Article ID : 288700
Revision : 7
Created on : 10/25/2007
Published on : 10/25/2007
Exists online : False
Views : 301