Article ID: 288700 - Last Review: October 25, 2007 - Revision: 2.5 Information Store Dismounts and StopsThis article was previously published under Q288700 SYMPTOMS
The information store dismounts and starts referencing "version store" errors similar to the following event:
Event ID 623
The Application log may also contain a series of MSexchangeIS events (#1022) and MSexchangeSA events (#9175).
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 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.
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.
STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server and Microsoft Exchange Server 2003.
| Article Translations
|
Back to the top
