What does HRESULT 0x80040E67 (DB_E_COMMANDNOTPERSISTED) mean?

 
Previous Next
DB_E_NOCOLUMN DB_E_DUPLICATEID

DB_E_COMMANDNOTPERSISTED

Command does not have a DBID

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 DB_E_COMMANDNOTPERSISTED is a failure HRESULT. Its facility is 4 (FACILITY_ITF) and its low code is 3687 (0x0E67). For DB_E_COMMANDNOTPERSISTED, 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 this result

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

Contract boundary

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

Investigation of DB_E_COMMANDNOTPERSISTED should start with the command object, current DBID, persistence flags and provider namespace. Capture DB_E_COMMANDNOTPERSISTED 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 DB_E_COMMANDNOTPERSISTED at the native call boundary.
  2. Identify the exact failing stage for DB_E_COMMANDNOTPERSISTED: ICommandPersist is asked for the current command DBID when the command has no persistent identity.
  3. Retrieve all OLE DB error records for DB_E_COMMANDNOTPERSISTED before another COM call replaces thread error information.
  4. Compare the live object state and provider-granted capabilities with the input that produced DB_E_COMMANDNOTPERSISTED.
  5. Reduce the DB_E_COMMANDNOTPERSISTED operation to the smallest case that preserves the same persist contract.
  6. Apply one evidence-backed correction for DB_E_COMMANDNOTPERSISTED and verify that the result is not merely replaced by a neighboring HRESULT.

Evidence to collect

A useful DB_E_COMMANDNOTPERSISTED event records provider CLSID and version, process architecture, interface IID and method, object correlation ID, transaction state and the immediately preceding HRESULT. When recording DB_E_COMMANDNOTPERSISTED 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 DB_E_COMMANDNOTPERSISTED: command object identity and persistence history.
  • Evidence 2 for DB_E_COMMANDNOTPERSISTED: the requested persistence operation and flags.
  • Evidence 3 for DB_E_COMMANDNOTPERSISTED: whether the provider still resolves the expected DBID.

Corrective actions

  • Action 1 for DB_E_COMMANDNOTPERSISTED: persist the command through the supported interface before requesting its ID.
  • Action 2 for DB_E_COMMANDNOTPERSISTED: treat transient commands as having no DBID.
  • Action 3 for DB_E_COMMANDNOTPERSISTED: 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 DB_E_COMMANDNOTPERSISTED with the method and object state makes this scenario diagnosable instead of reducing it to “database error”.

Retry and recovery

Retry rule for DB_E_COMMANDNOTPERSISTED: retry after successfully persisting the current command or loading an existing persisted command. A DB_E_COMMANDNOTPERSISTED retry is safe only when the relevant input, object generation, capability or external state has changed. Before replaying a modifying call that returned DB_E_COMMANDNOTPERSISTED, determine whether rows, schema objects or URL resources were partially created or changed.

Do not turn DB_E_COMMANDNOTPERSISTED into an unbounded retry loop. Preserve cancellation for DB_E_COMMANDNOTPERSISTED 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 DB_E_COMMANDNOTPERSISTED means no DBID exists. Telemetry and remediation for DB_E_COMMANDNOTPERSISTED should keep these outcomes distinct.

Developer and operations guidance

Code handling DB_E_COMMANDNOTPERSISTED 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 DB_E_COMMANDNOTPERSISTED, opaque values such as HACCESSOR, HROW, HCHAPTER, DBID components and provider handles must remain scoped to the object that issued them.

Operational dashboards for DB_E_COMMANDNOTPERSISTED should group by provider version, interface, method and normalized failure stage. A DB_E_COMMANDNOTPERSISTED 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.