What does HRESULT 0x80040E96 (DB_E_CANNOTCONNECT) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Connection to the server for this URL cannot be established. Meaning and corrective action.

Previous	Next
DB_E_ASYNCNOTSUPPORTED	DB_E_TIMEOUT

DB_E_CANNOTCONNECT

Exact value and result class

DB_E_CANNOTCONNECT has unsigned value 2147749526 (0x80040E96) and signed 32-bit value -2147217770. AllStat describes it as “Connection to the server for this URL cannot be established”. In this result, binding to the resource URL cannot establish a connection to the named server.

The high bit is set, so this result is a failure HRESULT. Its facility is 4 (FACILITY_ITF) and its low code is 3734 (0x0E96). These fields identify an interface-defined result family; they do not identify the provider instance, method, object generation or partial effects.

Contract boundary

The OLE DB binder model maps URLs to row, rowset, stream or collection objects. URL scope, requested object type, bind flags, asynchronous capability, locks and server reachability are independent parts of the binding contract.

Investigation of this result should start with the binder or session, normalized URL, requested GUID/object type and DBBINDURLSTATUS result. Capture it before ADO, ATL,.NET or a database abstraction layer replaces the native HRESULT with a generic exception.

Diagnostic sequence

Capture raw 0x80040E96 and symbolic this result at the native call boundary.
Identify the exact failing stage for it: binding to the resource URL cannot establish a connection to the named server.
Retrieve all OLE DB error records for it before another COM call replaces thread error information.
Compare the live object state and provider-granted capabilities with the input that produced it.
Reduce the operation to the smallest case that preserves the same binder contract.
Apply one evidence-backed correction for it and verify that the result is not merely replaced by a neighboring HRESULT.

Conditions that specifically lead to it

Cause 1 for it: the host or endpoint is unreachable.
Cause 2 for it: transport or TLS negotiation fails.
Cause 3 for it: the URL resolves to a server that is not accepting the provider protocol.

Evidence to collect

A useful it event records provider CLSID and version, process architecture, interface IID and method, object correlation ID, transaction state and the immediately preceding HRESULT. When recording it data involving URLs containing credentials, tenant paths and remote object names, use types, lengths, hashes or redacted identifiers rather than secrets or complete business data.

Evidence 1 for it: normalized host and endpoint.
Evidence 2 for it: DNS, transport and TLS failure details.
Evidence 3 for it: provider-native error records and retry-after information.

Corrective actions

Action 1 for it: verify endpoint reachability outside the application.
Action 2 for it: correct proxy, TLS or provider transport configuration.
Action 3 for it: separate connectivity from later authentication failure.

Retry and recovery

Retry rule for it: retry with bounded backoff only when the transport condition is transient. A it retry is safe only when the relevant input, object generation, capability or external state has changed. Before replaying a modifying call that returned it, determine whether rows, schema objects or URL resources were partially created or changed.

Do not turn it into an unbounded retry loop. Preserve cancellation for it and use a fresh provider object when the failed call may have left local state ambiguous.

Difference from nearby HRESULT values

DB_SEC_E_AUTH_FAILED means the server was reached but identity failed, while it means the connection could not be established. Telemetry and remediation for it should keep these outcomes distinct.

Practical scenario

A binder URL points to a retired host after failover; updating endpoint discovery restores the resource connection. Keeping it with the method and object state makes this scenario diagnosable instead of reducing it to “database error”.

Developer and operations guidance

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

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