| Previous | Next |
| hrWriteConflict | hrInvalidSesid |
hrTransTooDeep
Diagnostic focus
hrTransTooDeep means the session exceeded the supported nesting depth of transaction save points.
This is the legacy Directory Service backup/restore HRESULT form of JET_errTransTooDeep (0xC800044F).
The key comparison is: hrNotInTransaction reports no save point; this code reports too many nested save points. The first useful observation is to count unmatched JetBeginTransaction calls on the exact session and log each owner. This evidence shows whether the failure is nesting, ownership, cursor-local conflict, cross-session contention, or changed row state.
The ESE objects in play
| Diagnostic layer | JET_SESID transaction depth, row versions, and write ownership |
|---|---|
| Typical API surface | JetBeginSession, JetBeginTransaction, JetCommitTransaction, JetRollback, and update APIs |
| Code-specific condition | the session exceeded the supported nesting depth of transaction save points |
| First corrective direction | flatten helper-level transactions or make callers explicitly own the outer transaction |
Each begin must be matched by commit or rollback on the same session. Nested ESE transactions are save points and still share the outer session context.
Evidence that resolves the ambiguity
- Code-specific observation: count unmatched JetBeginTransaction calls on the exact session and log each owner.
- every begin, commit, and rollback for the exact JET_SESID; associate it with this result rather than with a later generic exception.
- transaction depth, thread owner, cursor handles, and target bookmark or key; associate it with this result rather than with a later generic exception.
- the row version and business preconditions observed before the write.
Nearby results that mean something different
hrSessionWriteConflict | two cursors in the same session attempted incompatible replacement of one record |
|---|---|
hrWriteConflict | another session owns a conflicting write lock for the target record or page |
hrNotInTransaction | the operation requires a transaction but the supplied session has no active save point |
A disciplined correction path
- Freeze the failing request context and record
0xC800044F, the Jet API name, and the current instance/session ownership. - Verify the code-specific precondition: count unmatched JetBeginTransaction calls on the exact session and log each owner.
- Apply the targeted fix: flatten helper-level transactions or make callers explicitly own the outer transaction.
- Before retrying the operation, reconcile transaction depth, lock release, row version, and application-level idempotency.
Actions that can hide or worsen the problem
- Do not blindly retry a non-idempotent update after a conflict.
- Do not share a session with an open transaction across unrelated threads or requests.
Technical references
Looking for a different code? Search another status or error code.