| Previous | Next |
| NS_E_STALE_PRESENTATION | NS_E_NAMESPACE_WRONG_TYPE |
NS_E_NAMESPACE_WRONG_PERSIST
Server-side meaning of NS_E_NAMESPACE_WRONG_PERSIST
Where the boundary sits
This result (0xC00D138A) marks a persistent child is being created beneath a transient parent. Although the visible symptom may be interrupted playback, this HRESULT is raised at an administrative or distribution checkpoint.
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 a this result 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. The decisive question is whether the live object and values match that boundary; the base AllStat description alone does not reveal the object generation, selected plug-in or lower-level failure.
Test the owning precondition
- Capture
0xC00D138A, this result, the exact API/administrative action and the first failure timestamp. - Preserve full parent path, parent persistence flag, requested child persistence flag and the configuration transaction that created both nodes.
- confirm that the object still belongs to the current WMServer, publishing-point or presentation generation.
- Perform one isolated experiment: create the persistent branch under a persistent parent or make the child transient, then reload the resulting configuration.
- Repeat the original the operation through the same protocol and service account; do not substitute a different client-side test.
- After this result, verify the expected next state and retain any later HRESULT as a separate pipeline result.
Keep the post-fix server event and object status so a later downstream HRESULT is not mistaken for recurrence of this one.
Code-specific failure anatomy
In a representative incident, the server reaches a persistent child is being created beneath a transient parent and rejects the operation before the caller can safely assume the next stage occurred. The incident record should therefore join full parent path, parent persistence flag, requested child persistence flag and the configuration transaction that created both nodes with the object generation and the exact administrative or protocol request.
A useful negative control is create the persistent branch under a persistent parent or make the child transient, then reload the resulting configuration. If that change advances the same it call, the result supports this boundary. If it remains, return to the first lower-level event instead of broadening the repair.
The tempting but misleading response is editing file permissions; persistence is a hierarchy rule, not an NTFS access check. That action does not test the distinction that matters here: wrong type concerns an existing value type, whereas it concerns the lifetime relationship between parent and child. This distinction is also why monitoring should retain the symbolic name instead of storing only a generic COM failure.
Evidence that separates this code
| Evidence | Why it matters for it |
|---|---|
| Decisive state | full parent path, parent persistence flag, requested child persistence flag and the configuration transaction that created both nodes. |
| Owning object | Record the server, publishing point, playlist, namespace node, plug-in or cache item that returned it, including its creation or restart time. |
| First lower-level result | Preserve the earliest Win32, socket, COM, parser or plug-in event before the HRESULT; later wrappers can map several causes to it. |
| Controlled comparison | Use a known-good object of the same type and vary only the precondition described as “a persistent child is being created beneath a transient parent”. |
| Security-sensitive data | Log identifiers, lengths, hashes and redacted URLs where possible; do not publish passwords, authorization files or unrestricted client data. |
Reading the second result
| Retest observation | Interpretation |
|---|---|
| The same call still returns it | The rejected precondition has not changed, or the caller is still using an old object/configuration generation. |
| The operation advances and a later code appears | The boundary was cleared. After it, diagnose the new code at its own source, parser, sink, network or client stage. |
| A new object succeeds while the retained object fails | Object lifetime or stale context is part of the incident; update lifecycle handling rather than applying a machine-wide repair. |
| Only one publishing point, playlist, cache key or plug-in fails | The evidence favors object-specific configuration or content over a server-wide outage. |
Changes that do not establish the cause
- editing file permissions; persistence is a hierarchy rule, not an NTFS access check.
- do not erase the first HRESULT by repeatedly clicking Apply; later calls can replace the thread error information and hide the component that rejected the operation.
- Do not suppress it or replace it with a generic “media server error”; retain the symbolic code and owning operation in telemetry.
Comparison with adjacent states
Primary distinction: wrong type concerns an existing value type, whereas it concerns the lifetime relationship between parent and child.
| Nearby result | Different checkpoint |
|---|---|
NS_E_NAMESPACE_WRONG_TYPE | Compare its own symbolic boundary and the first failing call; it must not be grouped automatically with it. |
NS_E_NAMESPACE_WRONG_SECURITY | Relative to it, this neighboring result belongs to another state or validation branch even when the user-visible symptom is similar. |
NS_E_NAMESPACE_NODE_CONFLICT | Use the object type and operation sequence to determine which result is authoritative. |
Technical references
Close the incident only after it clears on a current object.
Looking for a different code? Search another status or error code.