| Previous | Next |
| NS_E_NAMESPACE_NAME_TOO_LONG | NS_E_NAMESPACE_EMPTY_NAME |
NS_E_NAMESPACE_DUPLICATE_NAME
Mechanism and scope
This result (0xC00D1393) marks a sibling node with the requested name already exists. Treat the symbolic name as a map to the owning Windows Media Services subsystem rather than as a request to reinstall every media component.
Windows Media Services persists server configuration as a typed hierarchy; nodes have names, value types, security classifications and persistence rules; callbacks are attached to particular nodes rather than to arbitrary strings. In the trace, when configuration was imported or replicated, compare ServerNamespace.xml, NameSpaceDelta.xml and plug-in registrations, but do not edit those files while WMServer is running.
Test the owning precondition
- Capture
0xC00D1393, this result, the exact API/administrative action and the first failure timestamp. - Preserve parent path, normalized requested name, existing child type, persistence and creating transaction.
- Perform one isolated experiment: reuse or update the existing node, or choose a genuinely distinct sibling name after enumerating the parent.
Code-specific failure anatomy
A representative occurrence is when a sibling node with the requested name already exists. Capture parent path, normalized requested name, existing child type, persistence and creating transaction together with the object instance and the exact administrative or protocol request.
For a useful negative control, reuse or update the existing node, or choose a genuinely distinct sibling name after enumerating the parent.
The tempting but misleading response is retrying creation after a delay; deterministic name collision will remain. That action does not test the distinction that matters here: wrong type can occur when updating the existing node; duplicate name occurs while trying to create another node.
Build a reproducible incident record
| Controlled comparison | Use a known-good object of the same type and vary only the precondition described as “a sibling node with the requested name already exists”. |
Changes that do not establish the cause
- retrying creation after a delay; deterministic name collision will remain.
- Avoid changing the publishing point, protocol, content and plug-in set in one test; such a test cannot show which precondition cleared the code.
Comparison with adjacent states
Primary distinction: wrong type can occur when updating the existing node; duplicate name occurs while trying to create another node.
| Nearby result | Different condition |
|---|---|
NS_E_NAMESPACE_EMPTY_NAME | a create or lookup operation supplied an empty node-name component. |
NS_E_NAMESPACE_NAME_TOO_LONG | a node name exceeds the namespace component length accepted by the server. |
NS_E_NAMESPACE_INDEX_TOO_LARGE | child enumeration requested an ordinal outside the current child collection. |
Technical references
Looking for a different code? Search another status or error code.