What does HRESULT 0x80040E59 (DB_E_BADLOOKUPID) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

DB_E_BADLOOKUPID means an OLE DB operation received a lookup identifier that is invalid for the current provider object or scope.

Previous	Next
DB_E_BADHRESULT	DB_E_BADDYNAMICERRORID

DB_E_BADLOOKUPID

Meaning

Windows documents DB_E_BADLOOKUPID as “Lookup ID is invalid”. In this case, an OLE DB error record carries a lookup identifier that the selected provider error lookup service cannot accept.

Evidence to collect

When recording diagnostic data involving native database messages, error parameters and command fragments, use types, lengths, hashes or redacted identifiers rather than secrets or complete business data.

Evidence 1: provider CLSID for the lookup service.
Evidence 2: hrError and dwLookupID from the record.
Evidence 3: registry and version information for the error lookup component.

Relevant contract

OLE DB error objects can contain multiple records. Provider-side error construction combines an HRESULT, lookup ID, optional parameters, custom error object and dynamic-error lifetime; each identifier has a different namespace and validation rule.

Investigation of this result should start with the provider code building or resolving the OLE DB error record and the exact IErrorRecords operation.

Conditions that specifically lead to it

Cause 1: the lookup ID belongs to another provider version.
Cause 2: the ID is uninitialized or outside the registered lookup table.
Cause 3: IDENTIFIER_SDK_ERROR semantics were confused with a provider-specific ID.

Diagnostic sequence

Identify the exact failing stage: an OLE DB error record carries a lookup identifier that the selected provider error lookup service cannot accept.

Corrective actions

Action 1: use an ID defined by the matching lookup service.
Action 2: keep provider binary and message resources version-aligned.
Action 3: fall back to the SDK identifier only under its documented contract.

Practical scenario

A provider DLL is upgraded without its message lookup component; aligning the versions makes the record resolvable.

Retry and recovery

Retry rule: retry description retrieval after repairing the lookup ID or matching lookup service.

Difference from nearby HRESULT values

DB_E_BADDYNAMICERRORID rejects dynamic-error lifetime identity, while DB_E_BADLOOKUPID rejects the message lookup key.

Official Microsoft references

Looking for a different code? Search another status or error code.