| Previous | Next |
| DB_E_MULTIPLESTORAGE | DB_E_CANTORDER |
DB_E_CANTFILTER
Filter cannot be opened
Exact value and result class
DB_E_CANTFILTER has unsigned value 2147749471 (0x80040E5F) and signed 32-bit value -2147217825. AllStat describes it as “Filter cannot be opened”. In this result, the provider cannot open the requested filter view over the current source rowset.
The high bit is set, so DB_E_CANTFILTER is a failure HRESULT. Its facility is 4 (FACILITY_ITF) and its low code is 3679 (0x0E5F). For DB_E_CANTFILTER, these fields identify an interface-defined result family; they do not identify the provider instance, method, object generation or partial effects.
Contract boundary
For DB_E_CANTFILTER, OLE DB view interfaces apply filter and sort definitions to a source rowset. For DB_E_CANTFILTER, opening a filter or order depends on the view object, criteria metadata, rowset capabilities and current source state, not merely on the text of a predicate or sort key.
Investigation of DB_E_CANTFILTER should start with the IRowsetView-derived object, source rowset generation and filter or sort definition being opened. Capture DB_E_CANTFILTER before ADO, ATL, .NET or a database abstraction layer replaces the native HRESULT with a generic exception.
Conditions that specifically lead to this result
- Cause 1 for
DB_E_CANTFILTER: the filter definition uses unsupported criteria or types. - Cause 2 for
DB_E_CANTFILTER: the source rowset state no longer permits opening the view. - Cause 3 for
DB_E_CANTFILTER: the provider cannot allocate or materialize the filter object.
Evidence to collect
A useful DB_E_CANTFILTER event records provider CLSID and version, process architecture, interface IID and method, object correlation ID, transaction state and the immediately preceding HRESULT. When recording DB_E_CANTFILTER data involving filter values, sort keys and row identities, use types, lengths, hashes or redacted identifiers rather than secrets or complete business data.
- Evidence 1 for
DB_E_CANTFILTER: filter criteria and accessor metadata. - Evidence 2 for
DB_E_CANTFILTER: source rowset properties and generation. - Evidence 3 for
DB_E_CANTFILTER: provider error records from the filter-open call.
Diagnostic sequence
- Capture raw
0x80040E5Fand symbolicDB_E_CANTFILTERat the native call boundary. - Identify the exact failing stage for
DB_E_CANTFILTER: the provider cannot open the requested filter view over the current source rowset. - Retrieve all OLE DB error records for
DB_E_CANTFILTERbefore another COM call replaces thread error information. - Compare the live object state and provider-granted capabilities with the input that produced
DB_E_CANTFILTER. - Reduce the
DB_E_CANTFILTERoperation to the smallest case that preserves the same view contract. - Apply one evidence-backed correction for
DB_E_CANTFILTERand verify that the result is not merely replaced by a neighboring HRESULT.
Corrective actions
- Action 1 for
DB_E_CANTFILTER: reduce the filter to supported comparison operations. - Action 2 for
DB_E_CANTFILTER: recreate the view against the current source rowset. - Action 3 for
DB_E_CANTFILTER: apply filtering in command text only when semantics remain equivalent.
Retry and recovery
Retry rule for DB_E_CANTFILTER: retry after changing the filter definition, source state or provider capability. A DB_E_CANTFILTER retry is safe only when the relevant input, object generation, capability or external state has changed. Before replaying a modifying call that returned DB_E_CANTFILTER, determine whether rows, schema objects or URL resources were partially created or changed.
Do not turn DB_E_CANTFILTER into an unbounded retry loop. Preserve cancellation for DB_E_CANTFILTER and use a fresh provider object when the failed call may have left local state ambiguous.
Practical scenario
A cached filter references a column removed from the projection; rebuilding the view against current metadata allows it to open. Keeping DB_E_CANTFILTER with the method and object state makes this scenario diagnosable instead of reducing it to “database error”.
Difference from nearby HRESULT values
DB_E_BADCOMPAREOP rejects a specific comparison operator, while DB_E_CANTFILTER means the filter as a whole cannot be opened. Telemetry and remediation for DB_E_CANTFILTER should keep these outcomes distinct.
Developer and operations guidance
Code handling DB_E_CANTFILTER 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 DB_E_CANTFILTER, opaque values such as HACCESSOR, HROW, HCHAPTER, DBID components and provider handles must remain scoped to the object that issued them.
Operational dashboards for DB_E_CANTFILTER should group by provider version, interface, method and normalized failure stage. A DB_E_CANTFILTER event must not expose passwords, tokens, full connection strings, unrestricted command text or raw row contents.
Official Microsoft references
- Microsoft: rowset view interfaces — official documentation relevant to
DB_E_CANTFILTER. - Microsoft: OLE DB rowsets — official documentation relevant to
DB_E_CANTFILTER. - Microsoft: OLE DB interfaces — official documentation relevant to
DB_E_CANTFILTER.
Looking for a different code? Search another status or error code.