| Previous | Next |
| ERROR_CRM_PROTOCOL_NOT_FOUND | ERROR_CURRENT_TRANSACTION_NOT_VALID |
ERROR_TRANSACTION_INVALID_MARSHALL_BUFFER
This error is specific to transaction propagation. The byte buffer supplied to the KTM propagation path is not a valid marshaled transaction payload. It should therefore be investigated as a boundary between components or processes, not as a generic memory-allocation failure.
Common integrity checks
- Keep the buffer returned by the KTM propagation API opaque; do not edit, concatenate, reinterpret, or serialize native pointers into it.
- Pass the exact byte count associated with the buffer and preserve its lifetime until the receiving call has completed.
- Confirm that sender and receiver use the matching propagation API and that an error was not ignored when producing the buffer.
- Log only safe metadata such as size, call path, transaction identifier, and producing process; avoid exposing opaque transaction material in normal logs.
Invalid propagation data is distinct from a missing transaction object. If the problem is a stale or unknown transaction handle, KTM can instead report a transaction-not-found or object-lifetime status.
See the KTM overview, KTM API reference, and the WinError entry for this code.
Looking for a different code? Search another status or error code.