| Previous | Next |
| MK_E_SYNTAX | MK_E_INVALIDEXTENSION |
MK_E_NOOBJECT
No object for moniker
The native value 0x800401E5 is MK_E_NOOBJECT, unsigned 2147746277 and signed -2147221019. The documented description is “No object for moniker”. Treat it as evidence that the moniker is valid but no corresponding object can be obtained; the operation in progress is binding a parsed moniker to an object through the ROT, activation, or class-specific lookup.
Operational meaning
- Confirm that this result came from binding a parsed moniker to an object through the ROT, activation, or class-specific lookup, rather than from cleanup or a wrapper that ran afterward.
Cause model
- It can result when the target object was deleted, renamed, or never created.
- It can result when the object is not running and the moniker cannot activate it.
- It can result when the display name identifies storage but the caller requests an object not supplied by that storage.
Troubleshooting workflow
- Identify the exact object, method, and lifecycle phase involved in binding a parsed moniker to an object through the ROT, activation, or class-specific lookup.
- Check IsRunning and the Running Object Table before activation.
- Record target identity, requested IID, and whether storage binding succeeds.
- Verify scope such as user session, desktop, tenant, or document generation.
What to log
Correction strategy
Correction. create or locate the intended object, correct the moniker identity, or use BindToStorage when storage is the actual contract. Retry condition. Retry after target creation or registration; repeated lookup of the same absent identity should be throttled. Before repeating the operation, release partial monikers and bound interfaces, unregister only owned Running Object Table entries, and abandon a bind context whose deadline or parameters no longer match the retry.
Practical scenario
A link points to an item removed from a document; the file still opens, but object binding fails, so the application prompts the user to repair the item link.
Difference from related HRESULTs
MK_E_NOSTORAGE says the moniker does not expose storage; it says object binding found no target object.
Developer and administrator guidance
References
Looking for a different code? Search another status or error code.