| Previous | Next |
| STATUS_TXF_METADATA_ALREADY_PRESENT | STATUS_VIDEO_HUNG_DISPLAY_DRIVER_THREAD_RECOVERED |
STATUS_TRANSACTION_SCOPE_CALLBACKS_NOT_SET
Transaction-scope support was used before its handlers were registered
This status concerns the thread transaction-scope machinery rather than the validity of a particular transaction record. Code that pushes or restores an ambient transaction context requires its scope callbacks to be installed before entering that scope.
The usual defect is initialization order: a library begins transactional work during static initialization, worker startup, or teardown while the component responsible for registering the scope handlers has not run or has already been unloaded.
What to inspect
- Trace callback registration, module load order, thread creation, and the first scope-entry attempt.
- Check whether the failure occurs only during process startup or shutdown.
- Ensure every thread that uses an ambient transaction follows the same initialization contract.
- Do not substitute an arbitrary transaction handle; the missing facility is the scope-management callback layer.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Kernel Transaction Manager overview
- Microsoft: Kernel Transaction Manager functions
- Microsoft Windows SDK metadata: ktmw32.h
Looking for a different code? Search another status or error code.