What does HRESULT 0x800401A0 (INPLACE_E_NOTUNDOABLE) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The requested in-place operation cannot participate in the expected undo transaction.

Previous	Next
OLEOBJ_E_INVALIDVERB	INPLACE_E_NOTOOLSPACE

INPLACE_E_NOTUNDOABLE

Undo is not available

INPLACE_E_NOTUNDOABLE is the failure HRESULT 2147746208 (0x800401A0, signed -2147221088) from winerror.h. AllStat defines it as “Undo is not available”. In practical terms, The requested in-place operation cannot participate in the expected undo transaction. Interpret it in the context of coordinating in-place object editing with container undo support.

The high bit in 0x800401A0 is set, so this is a failure rather than a success or informational result. Its facility field is 4 (FACILITY_ITF) and its low 16-bit code is 416 (0x01A0). Those bit fields classify the value, but they do not identify the failing object by themselves; the native method, object identity, and first producer of this result remain essential.

Contract boundary

Understanding this result requires this subsystem context: In-place activation is a negotiation between the object, client site, frame, and document window. Undo capability and border space are independent resources and need distinct recovery paths.

Associate this result with one exact operation in IOleInPlaceObject, IOleInPlaceSite, active-object negotiation, undo state, border space, and tool-window layout.
Confirm that this result came from coordinating in-place object editing with container undo support, rather than from cleanup or a wrapper that ran afterward.
Preserve any IErrorInfo, underlying Win32 result, provider message, or callback failure that preceded it; the HRESULT alone should not erase a more specific cause.

Likely cause branches

It can result when the object has already committed a change that cannot be reversed.
It can result when the container requests undo after deactivation or transaction disposal.
It can result when the server never offered an undoable unit for this operation.

Evidence to preserve

A useful incident records the in-place activation phase, active object, container and object rectangles, border widths, frame and document windows, undo transaction state, and UI deactivation sequence. Also retain the application and component build, architecture, process and thread IDs, COM apartment, operation correlation ID, elapsed time, and the first state-changing event before the failure. When logging it, redact content and credentials while preserving types, lengths, hashes, opaque identities, and lifecycle generations needed to reproduce its contract.

record the edit transaction ID and object activation lifecycle.
capture when the container enabled its Undo command and which interface promised it.
distinguish inability to undo from failure performing a supported undo.

Diagnostic sequence

Capture it at the first native return before a wrapper maps it to a generic exception.
Identify the exact object, method, and lifecycle phase involved in coordinating in-place object editing with container undo support.
Reproduce it with one controlled input or state change, and verify that the correction changes the decisive evidence rather than merely hiding the result.

Recovery and retry

Correction. for it, disable the undo command for that operation, preserve document dirty state, and offer a higher-level reload or revert only when safe. Retry boundary. Retrying the same undo is inappropriate unless the object returns to a prior transaction state. Before repeating the operation, deactivate any partially active object, restore frame and document-window border space, and close or commit the current undo unit consistently.

Practical scenario

An embedded chart applies an external data refresh that cannot be reversed; the host marks the document modified and disables only that undo entry. This isolates it within OLE in-place activation and container coordination and provides a regression test for the stated correction.

Difference from related HRESULTs

OLE_E_PROMPTSAVECANCELLED concerns a save decision; it specifically says the active edit lacks a reversible unit. Keep those outcomes separate in exception mappings, telemetry dimensions, user messages, and automated retry policy.

Developer and administrator guidance

Model activation, UI activation, border negotiation, and undo as separate states, and balance every site or frame callback even when a later phase fails. Regression coverage for it should include objects without undo, zero and insufficient border space, tool-window changes, nested activation, frame destruction, and failure during UI deactivation.

Operational repair for it must target the evidence-backed owner: compare the object server in a known compatible container; layout or undo contract failures should not be treated as generic COM-registration damage. Retain before-and-after traces for it so the change can be attributed and reversed.

References

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