What does HRESULT 0x80040E67 (DB_E_COMMANDNOTPERSISTED) mean?

 
Previous Next
DB_E_NOCOLUMN DB_E_DUPLICATEID

DB_E_COMMANDNOTPERSISTED

Exact value and result class

DB_E_COMMANDNOTPERSISTED has unsigned value 2147749479 (0x80040E67) and signed 32-bit value -2147217817. AllStat describes it as “Command does not have a DBID”. In this result, ICommandPersist is asked for the current command DBID when the command has no persistent identity.

The high bit is set, so this result is a failure HRESULT. Its facility is 4 (FACILITY_ITF) and its low code is 3687 (0x0E67). These fields identify an interface-defined result family; they do not identify the provider instance, method, object generation or partial effects.

Conditions that specifically lead to the result

  • Cause 1 for it: the command was created only from transient text.
  • Cause 2 for it: the provider has not saved or assigned the command a DBID.
  • Cause 3 for it: a previously persisted command was deleted from the provider namespace.

Contract boundary

Persisted OLE DB commands use DBIDs and persistence flags that are distinct from command text. A live command can execute successfully without having a persistent identity, and a persistent name is scoped to the provider namespace.

Investigation of this result should start with the command object, current DBID, persistence flags and provider namespace. Capture it before ADO, ATL,.NET or a database abstraction layer replaces the native HRESULT with a generic exception.

Diagnostic sequence

  1. Capture raw 0x80040E67 and symbolic it at the native call boundary.
  2. Identify the exact failing stage for it: ICommandPersist is asked for the current command DBID when the command has no persistent identity.
  3. Retrieve all OLE DB error records for it before another COM call replaces thread error information.
  4. Compare the live object state and provider-granted capabilities with the input that produced it.
  5. Reduce the operation to the smallest case that preserves the same persist contract.
  6. Apply one evidence-backed correction for it and verify that the result is not merely replaced by a neighboring HRESULT.

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 command text, persistent command names and schema identifiers, use types, lengths, hashes or redacted identifiers rather than secrets or complete business data.

  • Evidence 1 for it: command object identity and persistence history.
  • Evidence 2 for it: the requested persistence operation and flags.
  • Evidence 3 for it: whether the provider still resolves the expected DBID.

Corrective actions

  • Action 1 for it: persist the command through the supported interface before requesting its ID.
  • Action 2 for it: treat transient commands as having no DBID.
  • Action 3 for it: handle deletion of persisted commands as a separate lifecycle event.

Practical scenario

A cache asks GetCurrentCommand for every ad-hoc query; checking persistence state avoids treating a transient command as named. Keeping it with the method and object state makes this scenario diagnosable instead of reducing it to “database error”.

Retry and recovery

Retry rule for it: retry after successfully persisting the current command or loading an existing persisted 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.

Difference from nearby HRESULT values

DB_E_BADCOMMANDID rejects an invalid command DBID, while it means no DBID exists. 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.