| Previous | Next |
| MK_E_NOTBINDABLE | MK_E_CANTOPENFILE |
MK_E_NOTBOUND
Moniker is not bound
Windows defines MK_E_NOTBOUND as 2147746281 (0x800401E9; signed value -2147221015). The documented description is “Moniker is not bound”. The moniker or object is not currently bound where the operation requires an established binding. The relevant operation is using a relationship or callback state before BindToObject/BindToStorage has completed.
Where it is raised
- Confirm that this result came from using a relationship or callback state before BindToObject/BindToStorage has completed, rather than from cleanup or a wrapper that ran afterward.
Telemetry checklist
- Record bind operation ID, completion state, returned object identity, and cancellation.
- serialize consumers behind successful bind completion.
- Check disconnection and object release events.
Why it is specific
- It can result when the caller invokes a follow-up operation after failed or canceled binding.
- It can result when a previously bound object was released or disconnected.
- It can result when asynchronous code observes the moniker state before binding completion.
Investigation order
- Identify the exact object, method, and lifecycle phase involved in using a relationship or callback state before BindToObject/BindToStorage has completed.
- Serialize consumers behind successful bind completion.
Safe handling
Correction. perform a fresh successful binding and publish the resulting object atomically to consumers. Retry condition. Retry is reasonable after a transient bind failure, but never pretend the old unbound state became valid. 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 background link resolver exposes its moniker before BindToObject completes; gating consumers on the future’s successful result removes the race.
Difference from related HRESULTs
MK_E_NOTBINDABLE rejects the capability to bind; it reports missing current binding state.
Developer and administrator guidance
References
Looking for a different code? Search another status or error code.