harrietj updated the Transaction Tracking topology, where can I see it, where can I not? blog entry in the ITCAM for Transactions 7.3 and 7.4 Updates blog.

Manage transactions in the cloud, Part 1: Transaction basics and distributed transactions

In this first part of a two-part series, André Fachat discusses
transaction basics and distributed transactions. Transactions can make error
handling easy, not just with a single resource but also across resources.
Here, André shows you how two-phase commit distributed transactions work and
points out that even they are only “eventually consistent,” if only by a small
time interval. He also illustrates how a persistent transaction log in the
transaction manager is a requirement for distributed transactions.

Related:

process name (process id) idThe version store for this instance (name) cannot grow because it is receiving Out-Of-Memory errors from the OS. 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.Current version store size for this instance: numberMbMaximum version store size for this instance: numberMbGlobal memory pre-reserved for all version stores: numberMbPossible long-running transaction: SessionId: id Session-context: value Session-context ThreadId: thread id

Details
Product: Exchange
Event ID: 624
Source: ESE
Version: 6.5.0000.0
Message: process name (process id) idThe version store for this instance (name) cannot grow because it is receiving Out-Of-Memory errors from the OS. 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.Current version store size for this instance: numberMbMaximum version store size for this instance: numberMbGlobal memory pre-reserved for all version stores: numberMbPossible long-running transaction: SessionId: id Session-context: value Session-context ThreadId: thread id
   
Explanation
The version store is where the Exchange Information Store service keeps records of transactions that are not yet finished. The version store cannot grow because it is receiving out-of-memory errors from the operating system. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to increase in size.

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.

   
User Action
No user action is required.

If the problem persists, contact Microsoft Product Support Services.

Related:

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

Details
Product: Exchange
Event ID: 623
Source: ESE
Version: 6.5.0000.0
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
   
Explanation

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

-1069.

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
very large. If there are very long-running or hung transactions, the

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.

   
User Action
  1. Check to make sure that you have the current Exchange

    service pack installed.

  2. Install any publicly available ESE and Information Store

    hotfixes that released after the current service pack.

  3. Search the Microsoft Knowledge Base for the following:

    Event ID 623, Error -1069, and JET_errVersionStoreOutOfMemory. Known

    resolutions with the version store include turning off write-back

    caching on the physical disk (rather than the controller), and making registry

    changes if using Instant Messaging or heavily using POP3 and IMAP4

    clients against the server. Other issues will be documented as they

    arise.

  4. If the issue is still not resolved by the above methods,

    contact Microsoft Product Support Services to continue troubleshooting the

    problem.

Related: