| Previous | Next |
| CO_E_OBJSRV_RPC_FAILURE | CO_E_SERVER_STOPPING |
MK_E_NO_NORMALIZED
MK_E_NO_NORMALIZED means that the moniker path cannot be transformed into the normalized form required for stable binding, reduction, or comparison.
Meaning in the subsystem
A resource can exist but still lack a normalized moniker representation; do not treat this solely as file-not-found.
Minimum useful evidence
- The exact display name and moniker class sequence before parsing
- Filesystem/URL case, separators, relative segments, prefixes, and escaped characters
- Binding context, left moniker, and result of IMoniker:Reduce or GetDisplayName
- Whether the underlying resource exists under the same canonical identity
Isolate the responsible condition
- Parse and normalize a minimal absolute display name for the same moniker type.
- Compare relative and absolute construction while holding the target resource fixed.
- Round-trip display name to moniker and back, then compare with IsEqual.
Avoid the common misdiagnosis
Read the comparison results in this order for moniker normalization and comparison:
Regression proof
Apply the smallest change that addresses the first rejected condition: Construct the correct moniker type with an absolute, canonical display name and remove ambiguous relative composition.
Close the incident only when parse, reduce, serialize, and bind the moniker consistently across processes and working directories.
Technical references
The following documentation is most relevant when checking the code against the actual Windows contract for moniker normalization and comparison:
Looking for a different code? Search another status or error code.