| Previous | Next |
| ERROR_TRANSACTION_PROPAGATION_FAILED | ERROR_TRANSACTION_INVALID_MARSHALL_BUFFER |
ERROR_CRM_PROTOCOL_NOT_FOUND
No registered CRM can handle the requested propagation protocol
ERROR_CRM_PROTOCOL_NOT_FOUND belongs to the Windows Kernel Transaction Manager transaction-processing model. KTM communication resource managers register propagation protocols so transaction context can cross coordinator boundaries. This status means the protocol identity requested by the propagation path has no current registration. It does not say that the transaction itself is missing or that an ordinary resource manager failed to enlist.
Compare the protocol identifier used by the caller with the CRM initialization logs and deployment configuration. Version skew can leave one side requesting a protocol that the installed coordinator does not register, while service-start ordering can expose a window before the CRM is ready. If the protocol was expected after restart, verify that its registration succeeded and was not rejected as a duplicate under another instance. Preserve the exact identifier; translating the failure to a generic network error loses the most useful diagnostic key.
What to inspect
- Record the exact propagation protocol identifier requested by the caller.
- Verify the CRM responsible for that protocol completed registration.
- Check deployment version and service-start ordering on both sides of the propagation boundary.
References
- Microsoft: KTM transaction, TM, RM, and enlistment functions
- Microsoft: superior transaction managers and superior enlistments
- MS-DTCO: superior and subordinate transaction-manager roles
Looking for a different code? Search another status or error code.