| Previous | Next |
| DB_S_BOOKMARKSKIPPED | DB_S_ENDOFROWSET |
DB_S_NONEXTROWSET
OLE DB has no additional rowset
DB_S_NONEXTROWSET is HRESULT 265925 (0x00040EC5) from Microsoft OLE DB. AllStat describes DB_S_NONEXTROWSET as “No more rowsets.” The high-order severity bit is clear, so this is a success result, but it carries more information than plain S_OK.
The current multiple-result operation completed and there is no next rowset to return.
Where this result is encountered
DB_S_NONEXTROWSETcan appear in stored procedures returning several results; record the producing interface and method rather than inferring behavior from the symbolic name alone.DB_S_NONEXTROWSETcan appear in IMultipleResults-style iteration; record the producing interface and method rather than inferring behavior from the symbolic name alone.DB_S_NONEXTROWSETcan appear in batch commands mixing rowsets and row counts; record the producing interface and method rather than inferring behavior from the symbolic name alone.
For DB_S_NONEXTROWSET, the same numeric success value can be mishandled when a wrapper exposes only a Boolean. For DB_S_NONEXTROWSET, keep the original HRESULT until the code-specific outputs and state transition have been evaluated.
State boundary that must be proved
The central question for DB_S_NONEXTROWSET is whether all previously returned results were consumed and released before the consumer terminates result iteration. For DB_S_NONEXTROWSET, the HRESULT alone confirms neither unrelated work nor the quality of optional outputs.
A reliable interpretation of DB_S_NONEXTROWSET names the exact method contract, the object generation, and the outputs that remain valid. For DB_S_NONEXTROWSET, this prevents a success-with-information result from being promoted to full success or demoted to a generic error.
Evidence and telemetry to preserve
- For
DB_S_NONEXTROWSET, preserve command text or procedure name. - For
DB_S_NONEXTROWSET, preserve result index and type. - For
DB_S_NONEXTROWSET, preserve row counts and output parameters. - For
DB_S_NONEXTROWSET, preserve open rowset interfaces. - For
DB_S_NONEXTROWSET, preserve transaction state after the final result.
Also record db_s_nonextrowset_operation, db_s_nonextrowset_object, db_s_nonextrowset_state_before, db_s_nonextrowset_state_after, UTC time, process and thread identifiers, and a correlation ID. For DB_S_NONEXTROWSET, keep secrets out of logs while retaining GUIDs, CLSIDs, media subtypes, property IDs, row identities, and hashes needed to distinguish objects.
Correct handling, retry, and recovery
End result enumeration normally, release the current result, and then read output parameters or commit according to the provider contract.
Retry DB_S_NONEXTROWSET only when the recorded state can change the documented outcome. For DB_S_NONEXTROWSET, 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.
Diagnostic sequence
- For
DB_S_NONEXTROWSET, capture the raw HRESULT0x00040EC5immediately after the returning method and record whether the caller usedSUCCEEDED,FAILED, equality testing, or exception translation. - Identify the exact owner of
DB_S_NONEXTROWSET: interface, method, object instance, provider or filter version, thread or apartment, and operation phase. - Validate the decisive contract boundary for
DB_S_NONEXTROWSET: all previously returned results were consumed and released before the consumer terminates result iteration. - For
DB_S_NONEXTROWSET, 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_NONEXTROWSET; do not assume that a success severity bit means every optional sub-operation completed. - For
DB_S_NONEXTROWSET, reproduce the smallest request with the same object state and then change only the condition identified by the evidence before repeating the operation.
Practical validation scenario
A procedure returns two rowsets followed by output parameters. After consuming the second rowset, the client receives DB_S_NONEXTROWSET and proceeds to read outputs without logging a failure.
The negative test should preserve the condition that produces DB_S_NONEXTROWSET; the recovery test should alter only that condition and verify the final state as well as the HRESULT.
Difference from nearby HRESULT values
DB_S_NORESULT can report no more result object for a particular call; DB_S_NONEXTROWSET specifically states there is no next rowset.
For DB_S_NONEXTROWSET, 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
For DB_S_NONEXTROWSET, application telemetry should separate terminal failure, ordinary success, partial completion, continuation, cancellation, and warning-like success. For DB_S_NONEXTROWSET, support bundles should contain the smallest reproducible call and the effective configuration seen by the owning component.
A support report for DB_S_NONEXTROWSET should include decimal 265925, hexadecimal 0x00040EC5, the AllStat meaning, the owning API, and the first detailed status or output that explains why the method did not return ordinary S_OK.
References
- Microsoft: OLE DB return codes — official documentation relevant to
DB_S_NONEXTROWSET. - Microsoft: OLE DB Driver return codes — official documentation relevant to
DB_S_NONEXTROWSET. - Microsoft: OLE DB error records — official documentation relevant to
DB_S_NONEXTROWSET.
Looking for a different code? Search another status or error code.