| Previous | Next |
| STATUS_TRANSACTION_PROPAGATION_FAILED | STATUS_TRANSACTION_SUPERIOR_EXISTS |
STATUS_CRM_PROTOCOL_NOT_FOUND
The transaction propagation data names an unavailable protocol provider
A propagated transaction is not self-describing enough to be handled by any resource manager. KTM must route it to the communication resource manager that owns the protocol used to marshal and unmarshal the transaction context.
The provider may not be installed, may have failed startup, may be registered under a different identifier, or may be unavailable after service restart. Parsing the propagation buffer in an unrelated component is unsafe because its format is protocol-specific.
What to inspect
- Capture the protocol identifier and the source that produced the propagation buffer.
- Verify the expected CRM provider is loaded and registered before transaction import.
- Check version and architecture mismatches between sender and receiver.
- Preserve the original buffer for provider-specific diagnostics; do not rewrite its header heuristically.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Kernel Transaction Manager overview
- Microsoft: creating a superior transaction manager
- Microsoft: Kernel Transaction Manager functions
Looking for a different code? Search another status or error code.