| Previous | Next |
| ERROR_ERRORS_ENCOUNTERED | ERROR_REQUEST_OUT_OF_SEQUENCE |
ERROR_NOT_CAPABLE
the selected implementation does not support the requested operation.
ERROR_NOT_CAPABLE identifies the condition that this condition The request is understood, but the component lacks the necessary capability in its current implementation, mode, or negotiated feature set.
Where the result appears
- optional provider interfaces.
- storage or database features unavailable in a chosen backend.
- down-level implementations.
- operations disabled by the selected cursor or object mode.
How to interpret the result
Interpret the numeric value in the Win32/LRESULT domain and in the context of the API that returned it. Preserve this result before wrappers convert it to an HRESULT, exception, Boolean failure, or provider-specific message. When recording it, note whether the operation produced usable output; this determines whether the value is completion information, control flow, or a terminal failure.
Diagnostic evidence to collect
- component version and provider identity.
- capability or property-query results.
- operation flags and object creation options.
- whether an alternate implementation succeeds.
A diagnostic record for this Win32 error should contain the API name, input flags, relevant handles or object identifiers, thread and process identity, timestamp, and the immediately preceding state transition. Those fields are more useful than a generic screenshot because they show which contract and lifecycle phase produced the value.
Handling and recovery
Negotiate capabilities before enabling the feature and provide a documented fallback where one exists. Repeated retries against the same implementation and configuration are not useful because capability does not change transiently.
Retry after this result only when an external state relevant to this operation can actually change. When it is rooted in object state, unsupported capability, ownership, or invalid sequencing, an unchanged retry repeats the defect and can obscure the first useful diagnostic record.
Common misinterpretation
This differs from access denied: granting more privilege will not add an unimplemented feature. It also differs from invalid arguments, because the request may be valid for another provider.
Guidance for developers
Keep the original this result value and its Win32 domain in structured telemetry. If it crosses COM or another HRESULT-based boundary, store both the source Win32 value and the converted result. If it crosses JSON, RPC, or a database boundary, include error_domain, error_code, operation, and object_state so the receiver does not apply a second conversion.
An automated test should construct the specific state that leads to this result, assert the exact returned value, and verify cleanup on both the normal and exceptional path. The result test should additionally prove that the caller does not collapse this status into an unrelated generic error and does not retry forever.
References
Looking for a different code? Search another status or error code.