HRESULT 0x00040ED2 (DB_S_ERRORSRETURNED): meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

DB_S_ERRORSRETURNED reports that an OLE DB operation completed with one or more detailed provider errors or property-status results to inspect.

Previous	Next
DB_S_COLUMNSCHANGED	DB_S_BADROWHANDLE

DB_S_ERRORSRETURNED

OLE DB method returned a detail error array

DB_S_ERRORSRETURNED is HRESULT 265938 (0x00040ED2) from Microsoft OLE DB. The documented description is “Method had some errors, which were returned in the error array.” The high-order severity bit is clear, so this is a success result, but it carries more information than plain S_OK.

The method completed with one or more conditions described in an accompanying error or status array.

Evidence to preserve

Preserve overall HRESULT.
Preserve array length and each element status.
Preserve associated ordinal or property ID.
Preserve provider error records.
Preserve partial outputs retained by the method.

Where the result is encountered

This result can appear in multi-item schema or property operations; record the producing interface and method.
This result can appear in batch conversions; record the producing interface and method.
It can appear in methods that return per-element status alongside an overall HRESULT; record the producing interface and method.

State to verify

The central question is whether every element status is inspected before the caller decides which outputs are valid.

Diagnostic sequence

Capture the raw HRESULT 0x00040ED2 immediately after the returning method and record whether the caller used SUCCEEDED, FAILED, equality testing, or exception translation.
Verify the method-specific state: every element status is inspected before the caller decides which outputs are valid.

Difference from nearby HRESULT values

DB_S_ERRORSOCCURRED is the common multiple-step success-with-information code; it specifically indicates returned error-array details.

Correct handling, retry, and recovery

Process successful elements and repair failed ones according to the method contract. Never ignore the detail array because the overall HRESULT has success severity.

Practical validation scenario

A metadata request covers twenty objects and returns details for three unsupported items. The tool records each item status, uses the seventeen valid results, and does not label the entire request fully successful.

Developer and administrator guidance

References

Looking for a different code? Search another status or error code.