| Previous | Next |
| DB_S_NONEXTROWSET | DB_S_COMMANDREEXECUTED |
DB_S_ENDOFROWSET
OLE DB reached the rowset or chapter boundary
DB_S_ENDOFROWSET is HRESULT 265926 (0x00040EC6) from Microsoft OLE DB. AllStat describes DB_S_ENDOFROWSET as “Start or end of rowset or chapter was reached.” The high-order severity bit is clear, so this is a success result, but it carries more information than plain S_OK.
The fetch reached the start or end of the rowset or chapter before satisfying the entire requested row count.
Where this result is encountered
DB_S_ENDOFROWSETcan appear in IRowset::GetNextRows; record the producing interface and method rather than inferring behavior from the symbolic name alone.DB_S_ENDOFROWSETcan appear in bookmark-relative fetches; record the producing interface and method rather than inferring behavior from the symbolic name alone.DB_S_ENDOFROWSETcan appear in forward or backward rowset paging; record the producing interface and method rather than inferring behavior from the symbolic name alone.
For DB_S_ENDOFROWSET, the same numeric success value can be mishandled when a wrapper exposes only a Boolean. For DB_S_ENDOFROWSET, keep the original HRESULT until the code-specific outputs and state transition have been evaluated.
Diagnostic sequence
- For
DB_S_ENDOFROWSET, capture the raw HRESULT0x00040EC6immediately after the returning method and record whether the caller usedSUCCEEDED,FAILED, equality testing, or exception translation. - Identify the exact owner of
DB_S_ENDOFROWSET: interface, method, object instance, provider or filter version, thread or apartment, and operation phase. - Validate the decisive contract boundary for
DB_S_ENDOFROWSET: the consumer processes the rows actually obtained and updates its cursor state to the documented boundary. - For
DB_S_ENDOFROWSET, inspect every output parameter, count, status array, returned interface, or side effect that the method documentation associates with this success-with-information result. - Compare the observed state before and after
DB_S_ENDOFROWSET; do not assume that a success severity bit means every optional sub-operation completed. - For
DB_S_ENDOFROWSET, reproduce the smallest request with the same object state and then change only the condition identified by the evidence before repeating the operation.
State boundary that must be proved
The central question for DB_S_ENDOFROWSET is whether the consumer processes the rows actually obtained and updates its cursor state to the documented boundary. For DB_S_ENDOFROWSET, the HRESULT alone confirms neither unrelated work nor the quality of optional outputs.
A reliable interpretation of DB_S_ENDOFROWSET names the exact method contract, the object generation, and the outputs that remain valid. For DB_S_ENDOFROWSET, this prevents a success-with-information result from being promoted to full success or demoted to a generic error.
Correct handling, retry, and recovery
Consume returned rows, then stop or reverse direction according to the application. Do not discard a partial final batch merely because the HRESULT differs from S_OK.
Retry DB_S_ENDOFROWSET only when the recorded state can change the documented outcome. For DB_S_ENDOFROWSET, repeating the same call is inappropriate for a stable end marker, cancellation, unsupported format, adjusted property, or partial result whose completed side effects have not been reconciled.
Evidence and telemetry to preserve
- For
DB_S_ENDOFROWSET, preserve requested and obtained counts. - For
DB_S_ENDOFROWSET, preserve fetch direction. - For
DB_S_ENDOFROWSET, preserve starting bookmark or offset. - For
DB_S_ENDOFROWSET, preserve rowset chapter. - For
DB_S_ENDOFROWSET, preserve next fetch position and held HROW handles.
Also record db_s_endofrowset_operation, db_s_endofrowset_object, db_s_endofrowset_state_before, db_s_endofrowset_state_after, UTC time, process and thread identifiers, and a correlation ID. For DB_S_ENDOFROWSET, keep secrets out of logs while retaining GUIDs, CLSIDs, media subtypes, property IDs, row identities, and hashes needed to distinguish objects.
Difference from nearby HRESULT values
DB_S_ROWLIMITEXCEEDED is an active-row capacity condition; DB_S_ENDOFROWSET is a data-position boundary.
For DB_S_ENDOFROWSET, this distinction determines whether the caller should consume partial outputs, stop iteration, wait, reconfigure, notify the user, or perform no error recovery at all.
Developer and administrator guidance
Tests for DB_S_ENDOFROWSET should verify both the encoded condition and the resulting outputs. A test for DB_S_ENDOFROWSET that checks only SUCCEEDED cannot detect stale counts, partial streams, adjusted properties, missing callbacks, or other code-specific effects.
A support report for DB_S_ENDOFROWSET should include decimal 265926, hexadecimal 0x00040EC6, the AllStat meaning, the owning API, and the first detailed status or output that explains why the method did not return ordinary S_OK.
Practical validation scenario
A page requests 100 rows near the end of a result set and receives 17 rows with DB_S_ENDOFROWSET. The client displays all 17 and marks the page as final.
The negative test should preserve the condition that produces DB_S_ENDOFROWSET; the recovery test should alter only that condition and verify the final state as well as the HRESULT.
References
- Microsoft: OLE DB return codes — official documentation relevant to
DB_S_ENDOFROWSET. - Microsoft: OLE DB Driver return codes — official documentation relevant to
DB_S_ENDOFROWSET. - Microsoft: OLE DB error records — official documentation relevant to
DB_S_ENDOFROWSET. - Microsoft: IRowset::GetNextRows — official documentation relevant to
DB_S_ENDOFROWSET.
Looking for a different code? Search another status or error code.