| Previous | Next |
| NS_E_STALE_PRESENTATION | NS_E_NAMESPACE_WRONG_TYPE |
NS_E_NAMESPACE_WRONG_PERSIST
Where the condition occurs
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 during an administrative or distribution operation.
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.
- Perform one isolated experiment: create the persistent branch under a persistent parent or make the child transient, then reload the resulting configuration.
Code-specific failure anatomy
A representative occurrence is when a persistent child is being created beneath a transient parent. Capture full parent path, parent persistence flag, requested child persistence flag and the configuration transaction that created both nodes together with the object instance and the exact administrative or protocol request.
For a useful negative control, create the persistent branch under a persistent parent or make the child transient, then reload the resulting configuration.
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.
Evidence that separates this code
| 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”. |
Changes that do not establish the cause
- editing file permissions; persistence is a hierarchy rule, not an NTFS access check.
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 condition |
|---|---|
NS_E_NAMESPACE_WRONG_TYPE | an existing node is being assigned a value with a different data type. |
NS_E_NAMESPACE_WRONG_SECURITY | an existing node is being written with a different security classification. |
NS_E_NAMESPACE_NODE_CONFLICT | the operation targets the protected root node or another structurally non-removable node. |
Technical references
Looking for a different code? Search another status or error code.