What does HRESULT 0x80040E0F (DB_E_BADLOCKMODE) mean?

 
Previous Next
DB_E_BADBOOKMARK DB_E_PARAMNOTOPTIONAL

DB_E_BADLOCKMODE

Lock mode is invalid

Exact value and interpretation

DB_E_BADLOCKMODE has the unsigned 32-bit value 2147749391 (0x80040E0F) and the signed representation -2147217905. AllStat defines the result as “Lock mode is invalid”. In the concrete failure represented here, an OLE DB resource or binder operation receives a lock mode outside the modes accepted by that method or provider.

The high bit is set for DB_E_BADLOCKMODE, 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 3599 (0x0E0F). Those bit fields place DB_E_BADLOCKMODE 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

DB_E_BADLOCKMODE must be interpreted against this contract: OLE DB objects follow both COM lifetime rules and provider-specific state contracts; open dependents, ownership transfer, aggregation, callbacks and namespace identity must be traced from the exact interface call rather than inferred from a wrapper exception.

Start with the COM object that returned the result and every dependent interface or provider-owned resource involved in the call when investigating DB_E_BADLOCKMODE. Preserve DB_E_BADLOCKMODE 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 this result

  • Cause 1 for DB_E_BADLOCKMODE: the lock-mode enumeration value is invalid.
  • Cause 2 for DB_E_BADLOCKMODE: a valid mode is unsupported for the selected resource type.
  • Cause 3 for DB_E_BADLOCKMODE: combined bind flags request a lock semantic the provider cannot honor.

Evidence to collect before changing the system

A useful DB_E_BADLOCKMODE 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 DB_E_BADLOCKMODE involves object URLs, command trees, data source names, caller identities and copied data, record types, lengths, hashes or redacted identifiers instead of secrets or full business data.

  • Evidence 1 for DB_E_BADLOCKMODE: the exact lock mode and accompanying bind flags.
  • Evidence 2 for DB_E_BADLOCKMODE: the interface and URL or object type receiving the request.
  • Evidence 3 for DB_E_BADLOCKMODE: provider capability metadata for share and deny modes.

Diagnostic sequence

  1. Capture DB_E_BADLOCKMODE immediately at the native OLE DB return and obtain the current OLE DB error object before another COM call replaces thread error information.
  2. Identify the exact stage for DB_E_BADLOCKMODE: an OLE DB resource or binder operation receives a lock mode outside the modes accepted by that method or provider.
  3. For DB_E_BADLOCKMODE, compare the live command, rowset, accessor or schema state with the metadata and properties actually granted by the provider.
  4. For DB_E_BADLOCKMODE, 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.
  5. For DB_E_BADLOCKMODE, reproduce the issue with the smallest command, rowset or definition operation that preserves the same contract boundary.
  6. For DB_E_BADLOCKMODE, 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 DB_E_BADLOCKMODE: use only lock modes documented for the invoked interface.
  • Action 2 for DB_E_BADLOCKMODE: choose a weaker supported mode when exclusivity is not required.
  • Action 3 for DB_E_BADLOCKMODE: separate lock acquisition from unrelated bind options so failures remain diagnosable.

Retry and recovery policy

Retry rule for DB_E_BADLOCKMODE: retry after changing the requested lock mode or resource state. A safe DB_E_BADLOCKMODE retry must use a changed input, object generation, provider capability or state transition. If the call returning DB_E_BADLOCKMODE could have created, updated, deleted or copied data, determine partial completion before replaying it.

For DB_E_BADLOCKMODE, use bounded retries and preserve cancellation. For DB_E_BADLOCKMODE, 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 namespace binder requests an exclusive lock for a provider that supports only shared reads; selecting the supported mode avoids DB_E_BADLOCKMODE. The diagnostic value comes from retaining DB_E_BADLOCKMODE together with the failing interface and object state, not from reducing every provider result to “database error”.

Difference from related HRESULT values

DB_E_RESOURCELOCKED means another process currently holds a conflicting lock, while DB_E_BADLOCKMODE means the requested mode itself is invalid or unsupported. Keep these outcomes separate in telemetry and user-facing remediation because DB_E_BADLOCKMODE requires a different next action.

Implementation guidance

Code handling DB_E_BADLOCKMODE should release OLE DB resources in ownership order, preserve every provider error record, and log granted properties rather than only requested properties. When handling DB_E_BADLOCKMODE, handles such as HACCESSOR, HROW, HCHAPTER and provider-specific region tokens must never be treated as portable integers across object lifetimes.

When DB_E_BADLOCKMODE 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. For DB_E_BADLOCKMODE, 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.