HRESULT 0xC00D138B (NS_E_NAMESPACE_WRONG

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

It is not possible to store a value in a namespace node that has a different value type.%0

Previous	Next
NS_E_NAMESPACE_WRONG_PERSIST	NS_E_NAMESPACE_NODE_CONFLICT

NS_E_NAMESPACE_WRONG_TYPE

What the server is validating

This result (0xC00D138B) marks an existing node is being assigned a value with a different data type. The most useful interpretation starts with the Windows Media Services object that returned the HRESULT.

Smallest useful experiment

Capture 0xC00D138B, this result, the exact API/administrative action and the first failure timestamp.
Preserve node path, stored type, requested type, caller component and serialized value length.
Perform one isolated experiment: read the existing type and write a value of that type, or deliberately replace the node in a controlled configuration migration.

Repeat the test with a newly resolved server object; a stale COM pointer can make a correct configuration appear unchanged.

Code-specific failure anatomy

A representative occurrence is when an existing node is being assigned a value with a different data type. Capture node path, stored type, requested type, caller component and serialized value length together with the object instance and the exact administrative or protocol request.

For a useful negative control, read the existing type and write a value of that type, or deliberately replace the node in a controlled configuration migration.

The tempting but misleading response is stringifying every value; the consumer may require the original numeric, Boolean or interface type. That action does not test the distinction that matters here: wrong security rejects a security classification mismatch rather than a value-type mismatch.

Evidence that separates this code

Controlled comparison

Use a known-good object of the same type and vary only the precondition described as “an existing node is being assigned a value with a different data type”.

Changes that do not establish the cause

stringifying every value; the consumer may require the original numeric, Boolean or interface type.
a successful ping or local file open is not sufficient proof: the failing service account and Windows Media Services object must perform the same operation.

Related codes are different

Primary distinction: wrong security rejects a security classification mismatch rather than a value-type mismatch.

Nearby result	Different condition
`NS_E_NAMESPACE_NODE_CONFLICT`	the operation targets the protected root node or another structurally non-removable node.
`NS_E_NAMESPACE_WRONG_PERSIST`	a persistent child is being created beneath a transient parent.
`NS_E_NAMESPACE_NODE_NOT_FOUND`	the requested configuration node is absent in the active namespace generation.

Technical references

Looking for a different code? Search another status or error code.