| Previous | Next |
| ERROR_CRM_PROTOCOL_ALREADY_EXISTS | ERROR_CRM_PROTOCOL_NOT_FOUND |
ERROR_TRANSACTION_PROPAGATION_FAILED
Transaction propagation failed before the remote branch was established
ERROR_TRANSACTION_PROPAGATION_FAILED belongs to the Windows Kernel Transaction Manager transaction-processing model. Distributed coordination requires the transaction context to be associated with another transaction manager and, for subordinate branches, a superior relationship to be registered. MS-DTCO describes branch registration and two-phase commit messages between superior and subordinate transaction managers. A propagation failure is therefore not the same as a later commit failure: the transaction branch could not be transferred or associated successfully.
Capture the propagation direction, protocol, local transaction ID, destination transaction manager, and the first transport or protocol error underneath this status. Verify authentication and service availability for the transaction coordinator path, but also check identity mismatches and duplicated branch association. Do not automatically replay application work until you know whether a remote branch was created; a retry after partial propagation can collide with existing transaction state.
What to inspect
- Log source and destination transaction-manager identities and the propagation protocol.
- Find the first transport, authentication, or branch-registration failure in the coordinator logs.
- Determine whether a remote branch exists before retrying propagation.
References
- MS-DTCO: superior and subordinate transaction-manager roles
- MS-DTCO: subordinate branch registration and two-phase commit
- Microsoft: superior transaction managers and superior enlistments
- Microsoft: KTM recovery processing and presumed abort
Looking for a different code? Search another status or error code.