| Previous | Next |
| NS_E_ADVANCEDEDIT_TOO_MANY_PICTURES | NS_E_STALE_PRESENTATION |
NS_E_REDIRECT
Server-side meaning of NS_E_REDIRECT
What the server is validating
This result (0xC00D1388) marks the server has selected another server or URL as the continuation target. The most useful interpretation starts with the Windows Media Services object that returned the HRESULT.
A Windows Media presentation has its own context and generation., redirects, updated descriptions and client reconnections can replace the active presentation while an older command still carries identifiers from the previous one. In a this result trace, correlate commands with the current presentation context; a reconnect or redirect can leave transport working while invalidating a previously captured context. 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.
A controlled correction
- Capture
0xC00D1388, this result, the exact API/administrative action and the first failure timestamp. - Preserve the redirect target, original request URL, control protocol, hop count and the response that supplied the new location.
- confirm that the object still belongs to the current WMServer, publishing-point or presentation generation.
- Perform one isolated experiment: issue one request directly to the returned target and compare its publishing-point identity with the original target.
- 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.
Success means the same operation crosses this checkpoint and produces the expected next state, not merely that the symbolic code disappears.
Code-specific failure anatomy
In a representative incident, the server reaches the server has selected another server or URL as the continuation target and rejects the operation before the caller can safely assume the next stage occurred. The incident record should therefore join the redirect target, original request URL, control protocol, hop count and the response that supplied the new location with the object generation and the exact administrative or protocol request.
A useful negative control is issue one request directly to the returned target and compare its publishing-point identity with the original target. 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 treating the result as packet loss or retrying the original URL forever. That action does not test the distinction that matters here: a redirect is a routing decision; a stale presentation means the command refers to obsolete presentation metadata. This distinction is also why monitoring should retain the symbolic name instead of storing only a generic COM failure.
What to record before changing anything
| Evidence | Why it matters for it |
|---|---|
| Decisive state | the redirect target, original request URL, control protocol, hop count and the response that supplied the new location. |
| 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 “the server has selected another server or URL as the continuation target”. |
| 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
- treating the result as packet loss or retrying the original URL forever.
- a broad reinstall is especially weak evidence here because it changes many unrelated components while leaving the rejected server precondition unexplained.
- 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: a redirect is a routing decision; a stale presentation means the command refers to obsolete presentation metadata.
| Nearby result | Different checkpoint |
|---|---|
NS_E_STALE_PRESENTATION | 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_WRONG_TYPE | Use the object type and operation sequence to determine which result is authoritative. |
Technical references
- Presentation Context
- User Context
- Media Streaming Server protocol relationships
- Microsoft HRESULT registry
Close the incident only after it clears on a current object.
Looking for a different code? Search another status or error code.