What does HRESULT 0x80040140 (VIEW_E_DRAW) mean?

VIEW_E_DRAW

Error drawing view

When Windows returns VIEW_E_DRAW—HRESULT 2147746112, 0x80040140, signed -2147221184—The documented description is “Error drawing view”. The actionable meaning is IViewObject accepted the view request but failed while rendering it. The surrounding operation is drawing an OLE object into a supplied device context.

Precise failure point

Rendering crosses object, container, and GDI boundaries. A useful incident record must show which side supplied every device context and rectangle, because repainting the same object with a newly valid target is different from repairing the object server.

• Associate this result with one exact operation in IViewObject::Draw and the container-supplied drawing context, bounds, aspect, target device, and continuation callback.
• Confirm that this result came from drawing an OLE object into a supplied device context, rather than from cleanup or a wrapper that ran afterward.

Diagnostic evidence

A useful incident records the requested DVASPECT, lindex, target device, HDC types, logical bounds, mapping mode, continuation callback result, object state, and rendering fallback used.

• Log the target HDC type, bounds, aspect, lindex, and continuation callback.
• Test drawing to a memory DC to separate object rendering from printer or display behavior.
• Capture server exceptions, linked-source state, and whether cached presentation data can be used.

Resolution path

1. Identify the exact object, method, and lifecycle phase involved in drawing an OLE object into a supplied device context.

Distinct causes

• It can result when the object cannot render the requested state or presentation data.
• It can result when the target or information HDC is invalid, incompatible, or already torn down.
• It can result when the object server fails during drawing, including a reentrant callback or unavailable linked source.

Retry policy

Correction. fall back to a valid cached presentation, recreate the drawing context, or repair the object server while preserving the container layout. Retry condition. Retry only with changed rendering state or a fresh DC; avoid tight repaint loops that repeatedly invoke the failing server. Before repeating the operation, restore every HDC and selected GDI object, discard only the failed presentation, and preserve a previously valid cache until a replacement render succeeds.

Practical scenario

A print preview asks an embedded object to draw into a printer DC that disappeared after device reconfiguration; recreating the DC and retrying once succeeds.

Difference from related HRESULTs

DV_E_DVASPECT rejects the requested presentation category before drawing; it reports failure after the drawing contract was entered.

Developer and administrator guidance

Validate aspect, lindex, target device, drawing bounds, mapping mode, and continuation callbacks at the IViewObject boundary. Regression coverage should include screen, printer, metafile, and thumbnail targets; empty or extreme bounds; cancellation callbacks; absent interfaces; and fallback to cached or application-provided rendering.

Compare the object server and presentation-handler versions and reproduce with a known-good host before reinstalling the component that actually owns rendering.

References

• Microsoft: generic COM error codes
• Microsoft: HRESULT values
• Microsoft: IViewObject::Draw
• Microsoft: IViewObject