| Previous | Next |
| TPC_E_INVALID_RIGHTS | TPC_E_OUT_OF_ORDER_CALL |
VFW_E_ADVISE_ALREADY_SET
Meaning and numerical form
VFW_E_ADVISE_ALREADY_SET is HRESULT 2147746358 (0x80040236; signed -2147220938). AllStat records its meaning as “An overlay advise link already exists”. In practical terms, it is returned when an IOverlay advise link is already installed when code attempts to set another one.
The severity bit in 0x80040236 is set, so this result is a failure result rather than a success or informational status. Its facility is 4 (FACILITY_ITF) and its low 16-bit code is 566 (0x0236). Those fields classify the value but do not identify the component instance, call, object or input that produced it.
Likely causes
- Possible cause 1 for this HRESULT: initialization runs twice without clearing the previous advise sink.
- Possible cause 2 for this HRESULT: renderer reconnection creates a new owner while the old link remains.
- Possible cause 3 for this HRESULT: multiple controllers compete for one overlay notification relationship.
Where the failure belongs
This result belongs to DirectShow filter-graph processing. DirectShow is a legacy, component-based media pipeline. Graph state, pin transport, negotiated media types, allocators, clocks, samples, renderers and source filters contribute separate contracts to the operation. The decisive condition is this: an IOverlay advise link is already installed when code attempts to set another one. Record the first native producer instead of relying only on a framework exception translated several layers later.
Do not infer from this result alone that reinstalling, rebooting or repeating the whole workflow is appropriate. Because it can cross process and language boundaries, its correction depends on the object identity, lifecycle generation, input and state at the first failing call.
Diagnostic sequence
- Capture this result at the first native return and identify the exact object and method.
- Confirm that the observed path matches this condition: an IOverlay advise link is already installed when code attempts to set another one.
- compare the live state with the method contract before changing configuration.
- collect the code-specific evidence listed above and preserve any more specific preceding error.
- change one evidence-backed cause at a time, then repeat the smallest operation that can prove the correction.
- Add a regression check that distinguishes it from the related outcomes described below.
Evidence to collect
A useful it record includes the native API or interface method, component or CLSID, process and thread IDs, architecture, apartment where relevant, operation correlation ID, elapsed time, input identity, and the first state-changing event before failure. When diagnosing it, preserve IErrorInfo, an inner HRESULT, Win32 status, device event or provider message when available.
- Capture 1 for this HRESULT: overlay object identity and existing advise sink.
- Capture 2 for this HRESULT: first Advise call, owner and graph generation.
- Capture 3 for this HRESULT: reconnection and teardown sequence.
Telemetry for this HRESULT should retain types, lengths, hashes, stable opaque identifiers and lifecycle generations while redacting content and credentials. This makes repeated incidents comparable without exposing media content, file paths, device identifiers or credentials.
Correction and retry boundary
- Corrective action 1 for this HRESULT: reuse the existing link or cancel it before setting a replacement.
- Corrective action 2 for this HRESULT: assign one owner to overlay notification lifetime.
- Corrective action 3 for this HRESULT: clear advise state during disconnect and destruction.
Retry guidance for this HRESULT. Retry only after the old advise link is successfully removed. A retry must avoid this hazard: replay obsolete samples, duplicate graph changes or reuse interfaces from an earlier topology generation. It must also preserve the evidence needed to locate the original producer of it.
Difference from nearby HRESULTs
VFW_E_NO_ADVISE_SET occurs when canceling a link that was never established; it occurs when establishing a duplicate link. Keep these outcomes separate in logs, exception mappings, user messages, dashboards and automated retry policy.
Practical scenario
A video window is recreated but the original controller remains advised to the overlay; orderly unadvise prevents it. The result scenario narrows the result to a reproducible contract boundary and supplies a concrete before-and-after test.
Developer and operational guidance
Code handling it should log the failed stage before cleanup, keep ownership and lifecycle transitions explicit, and avoid converting every failure into a generic message. Tests for this HRESULT should cover the primary cause, one adjacent HRESULT and the retry boundary so a future change cannot turn a deterministic contract failure into an uncontrolled loop.
Operational repair for this HRESULT should use supported filter installation, device, graph-building and renderer configuration paths. Avoid unsupported configuration edits or component replacement unless evidence identifies that layer. Retain the original trace and a post-fix trace so the result can be attributed and the change reversed.
Official Microsoft references
Looking for a different code? Search another status or error code.