| Previous | Next |
| OLEOBJ_E_NOVERBS | INPLACE_E_NOTUNDOABLE |
OLEOBJ_E_INVALIDVERB
Invalid verb for OLE object
When Windows returns OLEOBJ_E_INVALIDVERB—HRESULT 2147746177, 0x80040181, signed -2147221119—The documented description is “Invalid verb for OLE object”. The actionable meaning is the requested OLE verb is not valid for this object or state. The surrounding operation is calling IOleObject::DoVerb from a menu, double-click, or programmatic activation command.
Precise failure point
OLE verbs are object-advertised commands. Containers should construct UI from current enumeration and object state instead of assuming that standard-looking commands exist for every embedded class.
- Associate this result with one exact operation in IOleObject::EnumVerbs, IOleObject::DoVerb, container menus, object state, and verb availability.
- Confirm that this result came from calling IOleObject::DoVerb from a menu, double-click, or programmatic activation command, rather than from cleanup or a wrapper that ran afterward.
Diagnostic evidence
A useful incident records the verb ID, enumerated OLEVERB records, object CLSID, activation state, client site, parent HWND, MSG pointer, rectangle, and server response.
- Log lVerb and the full current EnumVerbs result.
- Record object CLSID, misc status, activation state, and user command source.
- Test the primary/default verb separately from class-specific positive IDs.
Resolution path
- Identify the exact object, method, and lifecycle phase involved in calling IOleObject::DoVerb from a menu, double-click, or programmatic activation command.
Distinct causes
- It can result when the lVerb value was not returned by EnumVerbs and is not a supported standard verb.
- It can result when a persisted or cached verb ID belongs to another class/version.
- It can result when the verb is unavailable in the object’s current activation or read-only state.
Retry policy
Correction. choose a verb currently advertised by the object or disable the unavailable command. Retry condition. Retry after refreshing verbs or changing object state; cycling through arbitrary integers is not safe discovery. Before repeating the operation, restore container menus and active-object state, close any partially activated UI, and re-enumerate verbs after the object or server changes.
Practical scenario
A container caches verb 2 from one spreadsheet server version, but the upgraded server advertises different positive IDs; rebuilding the menu from EnumVerbs fixes activation.
Difference from related HRESULTs
OLEOBJ_E_NOVERBS says enumeration provides no commands; it rejects one selected command.
Developer and administrator guidance
Build commands from current OLEVERB enumeration, preserve signed verb identifiers, and pass the correct client site, parent window, message, and rectangle to DoVerb. Regression coverage should include objects with no verbs, negative standard verbs, private verbs, state-dependent availability, headless activation, server restart, and UI deactivation after failure.
Confirm that the expected object server is installed and that the same CLSID exposes the verb in another supported container before repairing registration.
References
Looking for a different code? Search another status or error code.