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

Server-side meaning of `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.

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.

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.
confirm that the object still belongs to the current WMServer, publishing-point or presentation generation.
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 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.

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

Code-specific failure anatomy

In a representative incident, the server reaches an existing node is being assigned a value with a different data type and rejects the operation before the caller can safely assume the next stage occurred. The incident record should therefore join node path, stored type, requested type, caller component and serialized value length with the object generation and the exact administrative or protocol request.

A useful negative control is read the existing type and write a value of that type, or deliberately replace the node in a controlled configuration migration. 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 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. 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	node path, stored type, requested type, caller component and serialized value length.
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 “an existing node is being assigned a value with a different data type”.
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

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.
Do not suppress it or replace it with a generic “media server error”; retain the symbolic code and owning operation in telemetry.

Related codes are different

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

Nearby result	Different checkpoint
`NS_E_NAMESPACE_NODE_CONFLICT`	Compare its own symbolic boundary and the first failing call; it must not be grouped automatically with it.
`NS_E_NAMESPACE_WRONG_PERSIST`	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_NOT_FOUND`	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.