What does HRESULT 0x80041687 (FDAEMON_E_NOWORDLIST) mean?

 
Previous Next
FDAEMON_E_WORDLISTCOMMITFAILED FDAEMON_E_TOOMANYFILTEREDBLOCKS

FDAEMON_E_NOWORDLIST

No word list is currently being constructed

FDAEMON_E_NOWORDLIST is HRESULT 0x80041687. Windows documents it as “No wordlist is being constructed. May happen after fatal filter error.”

Exact contract boundary

This result belongs to legacy Windows content indexing and is returned while accepting extracted terms into the active word-list build context. The exact condition is: a prior fatal filtering failure, cancelled generation or lifecycle race leaves no valid word-list builder for the document.

This value belongs to the legacy filter daemon and content-indexing pipeline. It identifies failure while extracting or committing indexed content, so query syntax changes do not repair it. Preserve the document, filter handler and catalog generation that owned the work item. Current IFilter documentation clarifies handler extraction contracts, while the daemon HRESULT remains tied to the legacy content-indexing pipeline and its catalog generation.

Input or state defects

An unindexed document is only the outcome; it does not identify the handler, resource, partition generation, change list or word-list stage that failed.

Incident record

  • Record the source and normalization path of word-list context ID, not only its display form.
  • Record preceding fatal HRESULT before releasing the relevant objects.
  • Associate catalog generation with the exact UTC timestamp and correlation identifier.
  • Compare failing and known-good values for queued work generations under the same provider or handler version.
  • Record the source and normalization path of document identity and type, not only its display form.

Hash document content while retaining file type, size, handler CLSID, extraction stage, block counts and catalog generation.

How to isolate the cause

  1. Capture word-list context ID and creation/teardown events at the call boundary that returns this result.
  2. Confirm the operation reached accepting extracted terms into the active word-list build context with the intended preceding fatal HRESULT.
  3. trace creation and teardown of the word-list context and find the earlier error that removed it.

Run a copied document through the same filter version in an isolated queue and compare the exact extraction or commit stage with a known-good document type.

Restoration strategy

Recover the failed catalog generation or start a new valid indexing batch before resubmitting documents. Retry only after resource pressure, handler behavior, work generation or catalog storage state changes and stale work is discarded.

Scope of the result

It does not prove that all documents or all filters are affected; preserve the triggering work item, handler and catalog generation before broad recovery.

Comparison with adjacent codes

FDAEMON_E_WORDLISTCOMMITFAILED requires an existing word list that fails during commit.

Developer and administrator guidance

Retain the document identity, filter CLSID/version/bitness, daemon event, catalog generation and retry or quarantine history. Before rebuilding catalogs or reregistering every filter, isolate the document, handler and failed work generation.

Example from a search pipeline

After a fatal filter error tears down the active build, queued documents continue briefly. Generation-aware dispatch stops them and starts a clean batch.

Official Microsoft references


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