| Previous | Next |
| ERROR_CANTSCROLLBACKWARDS | ERROR_BAD_ACCESSOR_FLAGS |
ERROR_ROWSNOTRELEASED
previously fetched rows must be released before the provider can return more data.
ERROR_ROWSNOTRELEASED identifies the condition that this condition Some providers limit the number of simultaneously held row handles or require strict batch ownership. The caller still owns rows from an earlier fetch and requested another batch too soon.
Where the result appears
- OLE DB row-handle management.
- providers with small row-handle quotas.
- streaming or sequential rowsets.
- error paths that skip normal release calls.
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
- count of outstanding row handles.
- fetch batch size.
- release calls on success and exception paths.
- reference counts held by UI or business objects.
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
Release rows promptly after copying needed values, or reduce the fetch batch. Use scoped ownership so cancellation, parsing errors, and exceptions cannot bypass the release operation.
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
Closing only the command or accessor may not release individual row handles at the required time. Track the exact ownership object named by the provider contract.
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.