| Previous | Next |
| XACT_E_NOIMPORTOBJECT | XACT_E_INDOUBT |
XACT_E_INVALIDCOOKIE
A transaction cookie is opaque propagation data, not an application token
XACT_E_INVALIDCOOKIE means imported transaction propagation data could not be accepted. A cookie represents coordinator-specific transaction context and must be transferred without truncation or reinterpretation; it is not interchangeable with the transaction GUID, a user session token, or a cookie from another transaction manager instance.
Log the exported byte length and a cryptographic hash at both ends instead of writing sensitive raw propagation data. Check framing, base64 conversion, character encoding, and whether a service restart invalidated cached exports. Export a fresh cookie for each required propagation path and import it through the matching DTC API. Reconstructing a cookie from visible identifiers is unsupported and can attach work to no transaction at all.
Propagation checks that reveal cookie corruption
- Exporting transaction manager and export timestamp.
- Exact byte count before and after transport encoding.
- Hash comparison between sender and receiver.
- Receiver DTC instance, protocol, and import API.
References
- Microsoft MS-DTCO: transaction marshaling and propagation
- IETF: TIP transaction identification and transfer
- IETF: transaction-manager interoperability requirements
Looking for a different code? Search another status or error code.