HRESULT 0x80040002 (TAPI_E_NOITEMS): meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

No TAPI objects match the request

Could be also:
Constant	Type	OS
OLE_E_ENUM_NOMORE	HRESULT	Windows

Previous	Next
OLE_E_ENUM_NOMORE	OLE_E_ADVISENOTSUPPORTED

TAPI_E_NOITEMS

No TAPI objects match the request

TAPI_E_NOITEMS is HRESULT 2147745794 (0x80040002) from TAPI 3.0. AllStat describes it as “No items exist that match the request.” The result belongs to enumeration or lookup of addresses, calls, terminals, streams, or service-provider objects. The symbol this result is useful only when tied to the method and lifecycle phase where the requested collection or filter has no matching items.

The decisive meaning of this result is that the requested collection or filter has no matching items. The severity bit does not decide handling; the controlling fact is that the requested collection or filter has no matching items. A reliable it diagnosis preserves the raw value and reconstructs the state that made this true: the requested collection or filter has no matching items.

Where the result appears

This result can surface in a TAPI 3 address, call-control, terminal, stream, conference, dialing, or completion-management code.
map the failure to one concrete operation among ITTAPI, ITAddress, ITBasicCallControl, ITCallInfo, terminal and stream interfaces, provider events, and asynchronous request state.
Preserve provider name and version, address and call IDs, device class, media type, privilege, current address and call states, and asynchronous request ID before releasing or replacing the object that returned this result.

An incident record for this HRESULT must distinguish caller, runtime, provider, and backing resource while testing whether the requested collection or filter has no matching items.

Typical causes and interpretation boundary

The immediate contract boundary is specific: the requested collection or filter has no matching items. Common cause branches include the following:

The device or provider exposes no matching capability.
The filter uses an unavailable media type.
Objects disappeared after reconfiguration.

Confirm the cause branch that explains why the requested collection or filter has no matching items by using call arguments, object state, metadata, device information, or provider traces.

Correct handling and recovery

The primary recovery is to treat the empty result as a valid state when the API permits it and refresh after relevant device or provider events. The result failure report should expose enough enumeration or lookup of addresses, calls, terminals, streams, or service-provider objects state to understand why the requested collection or filter has no matching items without a production debugger.

The owner of it must define idempotency, cancellation, attempt limits, and reconciliation for the failed enumeration or lookup of addresses, calls, terminals, streams, or service-provider objects. Reconcile persistent, remote, device, or ownership state before repeating it.

Practical scenario

A client searches for video-capable terminals on an audio-only address and disables video UI when the collection is empty. Record the decisive state for this HRESULT and verify recovery on a fresh object or request generation.

Difference from related HRESULTs

TAPI_E_CALLUNAVAIL is specifically about call appearances; it applies to a broader object query Tests and telemetry should preserve that boundary for this HRESULT.

Developer and administrator guidance

Developers handling it should make object lifetime and state transitions explicit, preserve the native HRESULT, and keep cleanup paths safe when initialization or output is partial. Use a controllable service provider or simulator to cover state races, capability differences, device removal, cancellation, and provider restart.

Broad permission or compatibility changes are inappropriate unless evidence for the requested collection or filter has no matching items points to that layer. Repair for this HRESULT should target only the evidence-backed component, provider, document, device, or configuration.

References

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