| Previous | Next |
| DB_E_CANTCANCEL | DB_E_DUPLICATEDATASOURCE |
DB_E_DIALECTNOTSUPPORTED
Exact value and interpretation
DB_E_DIALECTNOTSUPPORTED has the unsigned 32-bit value 2147749398 (0x80040E16) and the signed representation -2147217898. AllStat defines the result as “Command dialect is not supported by this provider”. In the concrete failure represented here, ICommandText receives a command dialect GUID the provider does not support.
The high bit is set for it, 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 3606 (0x0E16). Those bit fields place this result in an interface-defined family, but they do not reveal the provider, object identity, method, rowset generation or command state that produced it.
Specific conditions that produce the result
- Cause 1 for it: the consumer assumes DBGUID_SQL for a non-SQL provider.
- Cause 2 for it: a provider-specific dialect GUID is used with a different provider.
- Cause 3 for it: the command object exposes text commands but only a narrower set of dialects.
OLE DB contract boundary
This result 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 this result. Preserve it 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.
Diagnostic sequence
- Capture it 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 it: ICommandText receives a command dialect GUID the provider does not support.
- compare the live command, rowset, accessor or schema state with the metadata and properties actually granted by the provider.
- 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.
- reproduce the issue with the smallest command, rowset or definition operation that preserves the same contract boundary.
- apply one evidence-backed correction, then verify that the operation succeeds and does not merely change into a nearby HRESULT.
Evidence to collect before changing the system
A useful it 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 it 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 it: the requested dialect GUID and provider CLSID.
- Evidence 2 for it: dialects reported or documented by the provider.
- Evidence 3 for it: the command text source and fallback-selection logic.
Corrective actions
- Action 1 for it: choose a dialect explicitly supported by the active provider.
- Action 2 for it: keep provider-specific command text separated by dialect.
- Action 3 for it: avoid silently relabeling text under a different GUID without translating its syntax.
Practical incident
A component passes an MDX dialect GUID to a relational provider because both share the same command wrapper; provider-aware selection prevents it. The diagnostic value comes from retaining it together with the failing interface and object state, not from reducing every provider result to “database error”.
Retry and recovery policy
Retry rule for it: retry after selecting a supported dialect and supplying command text valid for that dialect. A safe it retry must use a changed input, object generation, provider capability or state transition. If the call returning it could have created, updated, deleted or copied data, determine partial completion before replaying it.
Use bounded retries and preserve cancellation. Configuration and contract failures should normally fail fast; concurrency, resource or transient state failures may justify retry only after their stated precondition changes.
Difference from related HRESULT values
DB_E_ERRORSINCOMMAND means the dialect was accepted but the command failed parsing or validation, while it rejects the dialect contract itself. Keep these outcomes separate in telemetry and user-facing remediation because it requires a different next action.
Implementation guidance
Code handling it should release OLE DB resources in ownership order, preserve every provider error record, and log granted properties rather than only requested properties. When handling it, handles such as HACCESSOR, HROW, HCHAPTER and provider-specific region tokens must never be treated as portable integers across object lifetimes.
When it 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. 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.