| Previous | Next |
| STATUS_RKF_FILE_BLOCKED | STATUS_RDBSS_RESTART_OPERATION |
STATUS_RKF_ACTIVE_KEY
The resume key is valid but not eligible for recovery
A resume operation is intended to reclaim a handle whose live connection was lost while its state remained persisted. This status means RKF found the key, but the associated handle is still active or open. Reconnecting it would create two owners for the same persisted state and could violate locking and I/O ordering guarantees.
The distinction from STATUS_RKF_DUPLICATE_KEY is important: the key is not merely duplicated during registration; it resolves to a currently active handle. This often exposes an erroneous reconnect attempt, overlapping client sessions, or failover logic that started recovery before the previous owner was fenced.
What to inspect
- Identify the active session, tree connection, file ID, node, and client GUID that still owns the key.
- Verify whether the original transport actually failed or only experienced a transient delay.
- Check cluster ownership and fencing before allowing a second node to recover the handle.
- Do not close the active handle solely to make the reconnect succeed without application coordination.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft Open Specifications: durable handle request v2
- Microsoft Open Specifications: durable handle response v2
- Microsoft: SMB 3 file server features
Looking for a different code? Search another status or error code.