| Previous | Next |
| DB_E_NOTPREPARED | DB_E_WRITEONLYACCESSOR |
DB_E_BADACCESSORTYPE
Exact value and result class
DB_E_BADACCESSORTYPE has unsigned value 2147749451 (0x80040E4B) and signed 32-bit value -2147217845. AllStat describes it as “Accessor is not a parameter accessor”. In this result, a method that requires parameter bindings receives an accessor created for row data or another purpose.
The high bit is set, so this result is a failure HRESULT. Its facility is 4 (FACILITY_ITF) and its low code is 3659 (0x0E4B). These fields identify an interface-defined result family; they do not identify the provider instance, method, object generation or partial effects.
Contract boundary
Accessors are created on a specific command or rowset and encode direction, purpose, bound parts and buffer ownership. A valid HACCESSOR on one object is not interchangeable with a parameter accessor, a readable row accessor or an accessor created for another generation.
Investigation of this result should start with the object that created the accessor, its DBACCESSORFLAGS and every DBBINDING entry. Capture it before ADO, ATL,.NET or a database abstraction layer replaces the native HRESULT with a generic exception.
Conditions that specifically lead to the result
- Cause 1 for it: the HACCESSOR was created with row-data flags instead of parameter-data flags.
- Cause 2 for it: a wrapper reused an accessor from a rowset on a command.
- Cause 3 for it: the accessor belongs to an earlier command generation.
Evidence to collect
A useful it event records provider CLSID and version, process architecture, interface IID and method, object correlation ID, transaction state and the immediately preceding HRESULT. When recording it data involving parameter values, row values and provider-owned storage pointers, use types, lengths, hashes or redacted identifiers rather than secrets or complete business data.
- Evidence 1 for it: the DBACCESSORFLAGS used at CreateAccessor.
- Evidence 2 for it: the object identity that returned the HACCESSOR.
- Evidence 3 for it: the parameter ordinals and DBBINDING array used by Execute.
Diagnostic sequence
- Capture raw
0x80040E4Band symbolic it at the native call boundary. - Identify the exact failing stage for it: a method that requires parameter bindings receives an accessor created for row data or another purpose.
- Retrieve all OLE DB error records for it before another COM call replaces thread error information.
- Compare the live object state and provider-granted capabilities with the input that produced it.
- Reduce the operation to the smallest case that preserves the same accessor contract.
- Apply one evidence-backed correction for it and verify that the result is not merely replaced by a neighboring HRESULT.
Corrective actions
- Action 1 for it: create the accessor on the command that owns the parameters.
- Action 2 for it: use DBACCESSOR_PARAMETERDATA where required.
- Action 3 for it: invalidate cached accessors whenever command text or parameter metadata changes.
Retry and recovery
Retry rule for it: retry after replacing the handle with a current parameter accessor owned by the command. A it retry is safe only when the relevant input, object generation, capability or external state has changed. Before replaying a modifying call that returned it, determine whether rows, schema objects or URL resources were partially created or changed.
Do not turn it into an unbounded retry loop. Preserve cancellation for it and use a fresh provider object when the failed call may have left local state ambiguous.
Practical scenario
A generic binding cache supplies a row accessor to ICommand::Execute; rebuilding it as a parameter accessor removes the type mismatch. Keeping it with the method and object state makes this scenario diagnosable instead of reducing it to “database error”.
Difference from nearby HRESULT values
DB_E_BADACCESSORHANDLE means the handle itself is invalid, while it means a valid accessor has the wrong purpose. Telemetry and remediation for it should keep these outcomes distinct.
Developer and operations guidance
Code handling it should release COM objects in ownership order, retain per-row, per-column or per-property statuses, and log granted capabilities rather than only requested options. While handling it, opaque values such as HACCESSOR, HROW, HCHAPTER, DBID components and provider handles must remain scoped to the object that issued them.
Operational dashboards for it should group by provider version, interface, method and normalized failure stage. A it event must not expose passwords, tokens, full connection strings, unrestricted command text or raw row contents.
Official Microsoft references
Looking for a different code? Search another status or error code.