| Previous | Next |
| STATUS_RKF_KEY_NOT_FOUND | STATUS_RKF_BLOB_FULL |
STATUS_RKF_DUPLICATE_KEY
The resume key is already registered
Resume keys must identify persisted handle state unambiguously. This error occurs when a request tries to attach a key that is already present in the RKF store. It points to duplicate registration, replay of an earlier create request, or incorrect reuse of key material rather than to an ordinary file-sharing conflict.
SMB durable-handle requests also carry a CreateGuid so the server can distinguish retries from unrelated opens. Diagnostics should determine whether the second request is a legitimate replay that should reference existing state or a separate handle that incorrectly copied the same resume key.
What to inspect
- Compare the resume key, CreateGuid, client GUID, file ID, share, and node for both registrations.
- Check whether network retry logic resent a create after the first request had already succeeded.
- Review failover timing to determine whether old state should have been reclaimed or expired.
- Generate unique key material per persisted handle instead of deriving it only from a file path.
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
Looking for a different code? Search another status or error code.