| Previous | Next |
| DV_E_STGMEDIUM | DV_E_LINDEX |
DV_E_STATDATA
Invalid STATDATA structure
DV_E_STATDATA is the failure HRESULT 2147745895 (0x80040067, signed -2147221401) from winerror.h. The documented description is “Invalid STATDATA structure”. In practical terms, a STATDATA advisory record is internally inconsistent or unusable. Interpret it in the context of enumerating or consuming data-change advisory connections.
Relevant contract
COM data-transfer structures are compound contracts: a field can be numerically well formed yet invalid for the provider, object instance, requested aspect, or ownership rules. Diagnosis therefore has to preserve the complete descriptor and the exact method that consumed it.
- Associate this result with one exact operation in IDataObject, FORMATETC/STGMEDIUM negotiation, data advisory enumeration, or OLE rendering.
- Confirm that this result came from enumerating or consuming data-change advisory connections, rather than from cleanup or a wrapper that ran afterward.
Likely cause branches
- It can result when the FORMATETC member contains a format/aspect/medium combination that the data object never accepted.
- It can result when pAdvSink is null, already released, or belongs to a disconnected proxy.
- It can result when dwConnection is stale because DUnadvise or object teardown already removed that advisory connection.
Evidence to preserve
A useful incident records the IDataObject identity, method, clipboard format, aspect, lindex, tymed mask, target-device size, advisory cookie, and ownership of every returned interface or medium.
- Inspect each STATDATA field rather than treating the structure as an opaque blob.
- Compare the cookie with the current IDataAdviseHolder or IDataObject instance.
- Verify that the enumerator and every returned IAdviseSink remain alive while the record is read.
Diagnostic sequence
- Identify the exact object, method, and lifecycle phase involved in enumerating or consuming data-change advisory connections.
Recovery and retry
Correction. discard the bad advisory snapshot, rebuild the connection through DAdvise, and enumerate again from the current object. Retry condition. Retry only after creating a fresh advisory connection; repeating the same STATDATA record cannot repair its fields or lifetime. Before repeating the operation, release every returned STGMEDIUM according to pUnkForRelease, retain advisory cookies only after successful DAdvise, and discard enumerated formats after the data object is replaced.
Practical scenario
A container restores persisted advisory metadata but the saved connection cookie belongs to the prior object instance; a new DAdvise call returns a valid cookie and sink.
Difference from related HRESULTs
DV_E_FORMATETC concerns the transfer descriptor itself, while it concerns the larger advisory record that also carries the sink, flags, and connection cookie.
Developer and administrator guidance
Copy complete FORMATETC and DVTARGETDEVICE structures, preserve signed lindex values, intersect tymed masks before requesting data, and encode STGMEDIUM ownership explicitly. Regression coverage should include provider-advertised versus caller-invented formats, supported and unsupported DVASPECT/tymed combinations, sentinel lindex values, malformed target-device sizes, and replacement during advisory callbacks.
Compare the data provider, consumer, and registered handler versions; repair a handler only when traces identify that provider as missing or incompatible.
References
Looking for a different code? Search another status or error code.