| Previous | Next |
| DB_E_INVALID | DB_E_BADSTORAGEFLAGS |
DB_E_BADACCESSORFLAGS
Exact value and interpretation
DB_E_BADACCESSORFLAGS has the unsigned 32-bit value 2147749446 (0x80040E46) and the signed representation -2147217850. AllStat defines the result as “One or more accessor flags were invalid”. In the concrete failure represented here, IAccessor::CreateAccessor receives an invalid combination of DBACCESSORFLAGS.
The high bit is set for it, so it is a failure HRESULT rather than a success or informational status. Its facility field is 4 (FACILITY_ITF) and its low code is 3654 (0x0E46). Those bit fields place this result in an interface-defined family, but they do not reveal the provider, object identity, method, rowset generation or command state that produced it.
OLE DB contract boundary
This result must be interpreted against this contract: OLE DB accessors describe how columns or parameters map to a consumer buffer; an HACCESSOR is object-scoped, reference-counted and inseparable from its DBBINDING layout, bound parts, data types, offsets and ownership rules.
Start with the command or rowset that created the accessor and the consumer buffer passed to the failing method when investigating this result. Preserve it before ADO, ATL,.NET, a database abstraction layer or an application exception replaces it with a generic message; the exact interface and method matter because one OLE DB object can expose several contracts with different preconditions.
Specific conditions that produce the result
- Cause 1 for it: unknown flag bits are set.
- Cause 2 for it: row-data and parameter-data flags are combined where the object does not permit them.
- Cause 3 for it: a provider-specific unsupported flag is treated as universally available.
Evidence to collect before changing the system
A useful it record includes provider CLSID and version, process architecture, interface and method, COM apartment and thread, object correlation ID, transaction state, and the first preceding HRESULT. When it involves parameter values, row contents, connection-specific identifiers and long-data buffers, record types, lengths, hashes or redacted identifiers instead of secrets or full business data.
- Evidence 1 for it: the exact DBACCESSORFLAGS bitmask.
- Evidence 2 for it: whether the accessor is created on a command or rowset.
- Evidence 3 for it: provider capability and per-binding status.
Diagnostic sequence
- Capture it immediately at the native OLE DB return and obtain the current OLE DB error object before another COM call replaces thread error information.
- Identify the exact stage for it: IAccessor::CreateAccessor receives an invalid combination of DBACCESSORFLAGS.
- compare the live command, rowset, accessor or schema state with the metadata and properties actually granted by the provider.
- inspect per-binding, per-property, per-row or per-record statuses whenever the method supplies them; the aggregate result may not identify the rejected element.
- reproduce the issue with the smallest command, rowset or definition operation that preserves the same contract boundary.
- apply one evidence-backed correction, then verify that the operation succeeds and does not merely change into a nearby HRESULT.
Corrective actions
- Action 1 for it: mask out unknown bits.
- Action 2 for it: create separate row and parameter accessors when required.
- Action 3 for it: derive flags from the operation rather than copying them from another object.
Retry and recovery policy
Retry rule for it: retry after creating an accessor with a valid flag combination. A safe it retry must use a changed input, object generation, provider capability or state transition. If the call returning it could have created, updated, deleted or copied data, determine partial completion before replaying it.
Use bounded retries and preserve cancellation. Configuration and contract failures should normally fail fast; concurrency, resource or transient state failures may justify retry only after their stated precondition changes.
Practical incident
A wrapper copies parameter-accessor flags onto a rowset-only accessor; selecting DBACCESSOR_ROWDATA for that object removes it. The diagnostic value comes from retaining it together with the failing interface and object state, not from reducing every provider result to “database error”.
Difference from related HRESULT values
DB_E_BADBINDINFO concerns individual DBBINDING entries, while it concerns the accessor-level flag mask. Keep these outcomes separate in telemetry and user-facing remediation because it requires a different next action.
Implementation guidance
Code handling it should release OLE DB resources in ownership order, preserve every provider error record, and log granted properties rather than only requested properties. When handling it, handles such as HACCESSOR, HROW, HCHAPTER and provider-specific region tokens must never be treated as portable integers across object lifetimes.
When it crosses an abstraction boundary, attach a stable correlation ID and structured fields for the native HRESULT, provider source, interface IID, method, object generation and operation phase. Do not log passwords, access tokens, complete SQL text or unrestricted row values merely to make the event easier to search.
Official Microsoft references
Looking for a different code? Search another status or error code.