|Message:||process name (process id) instanceThe version store for this instance (name) has reached its maximum size of valueMb. 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: value Session-context: value Session-context ThreadId: value|
You receive an ESE Event ID 623 with the following Description: The
version store for instance 0 (“guid”) has reached its maximum size of xxxMb.
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:[transaction].
You may also receive an MSExchangeIS Event ID 1022 with the following
Description: Logon Failure on database [Database name – Account] Error
The ESE version store is where the
Exchange Information Store service keeps records of transactions that are not
yet finished, giving ESE the ability to
track and manage current transactions. The version store has a list of
operations performed by active transactions. This is an in-memory list
of modifications made to the database. This list has several uses: Rollback —
if a transaction needs to roll back, it looks in the version store to get the
list of operations it performed. If two sessions try to modify
the same record, the version store will notice and reject the second
modification. In other words, the version store keeps track of what
version of a transaction that ESE is actively using.
A hung transaction will cause the version store to get
version store can grow quite quickly and ultimately it is possible to see
version store out of memory errors. A transaction that takes a very long
time to run can cause the Exchange store to run out of spaces because it
cannot flush more recent transactions from the version store. When the version
store is full, any updates to the database are rejected until the long-running
transaction is completely committed or rolled back. This causes a service
interruption for users. Then an ESE Event ID 623 may be reported in the
Application log and an associated MSExchangeIS Event ID 1022 with Error -1069
or JET_errVersionStoreOutOfMemory may also result.
Error -1069 indicates that the version store had been
consumed, reaching its defined size. No more transactions can continue until
this is clear. Because the version store is where transactions are held in
memory until they can be written to disk, if something is preventing ESE
from completing transaction or writing to disk, then ESE will consume this
cache and the store will stop responding to requests until there is room in the cache again.
NOTE: this error is NOT the result of the system running
out of memory. If there is a failure to allocate more memory and NT refuses to
provide it, there will be a failure with a different error. Increasing the
RAM in the server will NOT fix this problem.