| Previous | Next |
| STATUS_VHD_ALREADY_AT_OR_BELOW_MINIMUM_VIRTUAL_SIZE | STATUS_RKF_DUPLICATE_KEY |
STATUS_RKF_KEY_NOT_FOUND
The requested persistent handle state is not present
The Resume Key Filter participates in preserving file-handle state for continuously available SMB workloads. A resume key identifies state that can be reclaimed after a planned or unplanned interruption. This status means the supplied key does not match an entry currently retained by the filter.
The key may be stale, may belong to another file or cluster incarnation, or may have been removed after its reconnect window expired. The failure should be correlated with the SMB durable or persistent handle request that carried the client-side identity; opening the file as a new handle is not the same as restoring the old state.
What to inspect
- Capture the SMB CreateGuid, persistent-handle flags, file path, client GUID, and reconnect timing.
- Check cluster failover and SMBServer logs for cleanup or ownership changes before the reconnect.
- Verify that the key was read from the same handle instance and volume where it was created.
- Do not reuse cached keys across a new server, share, or cluster generation.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: RKF_BYPASS_ECP_CONTEXT
- Microsoft Open Specifications: durable handle request v2
- Microsoft Open Specifications: durable handle response v2
- Microsoft: Scale-Out File Server overview
Looking for a different code? Search another status or error code.