| Previous | Next |
| DV_E_DVTARGETDEVICE_SIZE | DRAGDROP_E_NOTREGISTERED |
DV_E_NOIVIEWOBJECT
Object doesn't support IViewObject interface
Windows defines DV_E_NOIVIEWOBJECT as 2147745901 (0x8004006D; signed value -2147221395). The documented description is “Object doesn't support IViewObject interface”. The COM object does not expose IViewObject for the requested presentation path. The relevant operation is obtaining a drawable or cacheable view from an OLE data source or embedded object.
Where it is raised
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 obtaining a drawable or cacheable view from an OLE data source or embedded object, rather than from cleanup or a wrapper that ran afterward.
Telemetry checklist
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.
- query IViewObject directly and retain the returned E_NOINTERFACE detail if present.
- Inspect the CLSID and server version rather than inferring support from file extension.
- Test whether cached IDataObject formats provide an alternate presentation.
Why it is specific
- It can result when the class is a data-only object and intentionally implements IDataObject without IViewObject.
- It can result when the caller queried the wrong identity or an inner interface instead of the controlling object.
- It can result when the proxy, handler, or version installed on this machine omits the view interface expected by the container.
Investigation order
- Identify the exact object, method, and lifecycle phase involved in obtaining a drawable or cacheable view from an OLE data source or embedded object.
Safe handling
Correction. use an advertised IDataObject format, an OLE cache, or an application renderer; install or repair the correct handler only when registration evidence proves it is missing. Retry condition. Retrying QueryInterface on the same object is pointless unless the object is replaced or aggregation state changes. 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 document converter exposes file contents through IDataObject but has no visual implementation; the host uses a registered thumbnail provider instead of assuming IViewObject.
Difference from related HRESULTs
VIEW_E_DRAW occurs after IViewObject exists and drawing begins; it says that interface is unavailable.
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.