HRESULT 0x80040E33 (DB_E_CANTTRANSLATE): meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Current tree cannot be represented as text. OLE DB diagnosis and safe retry guidance.

Previous	Next
DB_E_ROWSETINCOMMAND	DB_E_DUPLICATEINDEXID

DB_E_CANTTRANSLATE

Current tree cannot be represented as text

Exact value and interpretation

DB_E_CANTTRANSLATE has the unsigned 32-bit value 2147749427 (0x80040E33) and the signed representation -2147217869. AllStat defines the result as “Current tree cannot be represented as text”. In the concrete failure represented here, the current command tree cannot be represented as command text in the requested dialect.

The high bit is set for DB_E_CANTTRANSLATE, 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 3635 (0x0E33). Those bit fields place DB_E_CANTTRANSLATE 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_CANTTRANSLATE must be interpreted against this contract: an OLE DB command moves through explicit states: command definition, properties and parameters are established before optional preparation and execution; dialect, query-tree and optimizer contracts are provider-specific and should be inferred only from reported capabilities.

Start with the active command object, its state transition history, dialect and provider error records when investigating DB_E_CANTTRANSLATE. Preserve DB_E_CANTTRANSLATE 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.

Evidence to collect before changing the system

A useful DB_E_CANTTRANSLATE 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_CANTTRANSLATE involves command text, parameter values, object names and query-plan details, record types, lengths, hashes or redacted identifiers instead of secrets or full business data.

Evidence 1 for DB_E_CANTTRANSLATE: the command-tree node types and requested dialect.
Evidence 2 for DB_E_CANTTRANSLATE: the first node the provider reports as untranslatable.
Evidence 3 for DB_E_CANTTRANSLATE: whether the tree was produced from text or built programmatically.

Specific conditions that produce this result

Cause 1 for DB_E_CANTTRANSLATE: the tree contains provider-specific nodes with no textual form.
Cause 2 for DB_E_CANTTRANSLATE: a live object or opaque expression cannot be serialized.
Cause 3 for DB_E_CANTTRANSLATE: the requested dialect lacks syntax for a tree feature.

Diagnostic sequence

Capture DB_E_CANTTRANSLATE immediately at the native OLE DB return and obtain the current OLE DB error object before another COM call replaces thread error information.
Identify the exact stage for DB_E_CANTTRANSLATE: the current command tree cannot be represented as command text in the requested dialect.
For DB_E_CANTTRANSLATE, compare the live command, rowset, accessor or schema state with the metadata and properties actually granted by the provider.
For DB_E_CANTTRANSLATE, 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.
For DB_E_CANTTRANSLATE, reproduce the issue with the smallest command, rowset or definition operation that preserves the same contract boundary.
For DB_E_CANTTRANSLATE, apply one evidence-backed correction, then verify that the operation succeeds and does not merely change into a nearby HRESULT.

Retry and recovery policy

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

For DB_E_CANTTRANSLATE, use bounded retries and preserve cancellation. For DB_E_CANTTRANSLATE, configuration and contract failures should normally fail fast; concurrency, resource or transient state failures may justify retry only after their stated precondition changes.

Corrective actions

Action 1 for DB_E_CANTTRANSLATE: retain the tree as the authoritative representation when text is optional.
Action 2 for DB_E_CANTTRANSLATE: simplify or replace unsupported nodes before translation.
Action 3 for DB_E_CANTTRANSLATE: select a dialect that can represent the required constructs when one exists.

Practical incident

A diagnostic tool asks a provider to render a tree containing an opaque custom operator as SQL text; logging a structural summary instead avoids DB_E_CANTTRANSLATE. The diagnostic value comes from retaining DB_E_CANTTRANSLATE together with the failing interface and object state, not from reducing every provider result to “database error”.

Implementation guidance

Code handling DB_E_CANTTRANSLATE 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_CANTTRANSLATE, handles such as HACCESSOR, HROW, HCHAPTER and provider-specific region tokens must never be treated as portable integers across object lifetimes.

When DB_E_CANTTRANSLATE 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_CANTTRANSLATE, do not log passwords, access tokens, complete SQL text or unrestricted row values merely to make the event easier to search.

Difference from related HRESULT values

DB_E_ERRORSINCOMMAND means textual command processing failed, while DB_E_CANTTRANSLATE means a valid tree cannot be converted into text. Keep these outcomes separate in telemetry and user-facing remediation because DB_E_CANTTRANSLATE requires a different next action.

Official Microsoft references

Microsoft: OLE DB commands — official documentation relevant to DB_E_CANTTRANSLATE.
Microsoft: ICommand — official documentation relevant to DB_E_CANTTRANSLATE.
Microsoft: OLE DB command states — official documentation relevant to DB_E_CANTTRANSLATE.

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