| Previous | Next |
| STATUS_REMOTE_FILE_VERSION_MISMATCH | STATUS_TRANSACTION_PROPAGATION_FAILED |
STATUS_CRM_PROTOCOL_ALREADY_EXISTS
The propagation protocol registration collides with an existing CRM
Communication resource managers extend transaction coordination across process or host boundaries. Their propagation protocol registration must be unique within the relevant transaction-manager context so that incoming propagation data is routed to the correct implementation.
A duplicate can indicate repeated initialization, two versions of the same provider loaded together, or two unrelated providers using the same protocol identifier. Replacing the active registration without proving ownership can break transactions already using it.
What to inspect
- Record the protocol identifier, provider version, module path, and transaction-manager identity.
- Find which component registered the protocol first and whether it is still active.
- Serialize provider startup and reject mixed incompatible versions.
- Do not generate a new identifier dynamically when interoperability requires a stable protocol identity.
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.