| 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 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.
What 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.
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.
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.
References
Looking for a different code? Search another status or error code.