| Previous | Next |
| NS_E_PLAYLIST_TOO_MANY_NESTED_PLAYLISTS | NS_E_PLAYLIST_END_RECEDING |
NS_E_PLAYLIST_SHUTDOWN
NS_E_PLAYLIST_SHUTDOWN: owning object, evidence and recovery
What the server is validating
This result (0xC00D14BC) marks the in-memory playlist object has already been shut down. The code identifies a narrow server contract, so diagnosis should preserve the object generation and the first native return.
The WMS playlist parser turns WSX/SMIL or another supported source into an in-memory playlist for a client., entry identity, nesting, current direction and shutdown state matter independently of whether the referenced media file exists. In a this result trace, save the parser-visible playlist after redirects or dynamic generation. While diagnosing it, the server acts on the resolved document and in-memory entry identities, not necessarily the text the operator first opened. 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.
Reading the second result
| Retest observation | Interpretation |
|---|---|
| The same call still returns this result | 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 this result, 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. |
Code-specific failure anatomy
In a representative incident, the server reaches the in-memory playlist object has already been shut down and rejects the operation before the caller can safely assume the next stage occurred. The incident record should therefore join shutdown event, client disconnect, publishing-point stop, object generation and late command callback with the object generation and the exact administrative or protocol request.
A useful negative control is cancel late work and obtain a new playlist object for a new client/presentation. 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 reviving the old COM object after server shutdown. That action does not test the distinction that matters here: end receding describes directional traversal reaching the boundary, while shutdown invalidates the whole object. This distinction is also why monitoring should retain the symbolic name instead of storing only a generic COM failure.
Build a reproducible incident record
| Evidence | Why it matters for it |
|---|---|
| Decisive state | shutdown event, client disconnect, publishing-point stop, object generation and late command callback. |
| 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 in-memory playlist object has already been shut down”. |
| Security-sensitive data | Log identifiers, lengths, hashes and redacted URLs where possible; do not publish passwords, authorization files or unrestricted client data. |
A controlled correction
- Capture
0xC00D14BC, it, the exact API/administrative action and the first failure timestamp. - Preserve shutdown event, client disconnect, publishing-point stop, object generation and late command callback.
- confirm that the object still belongs to the current WMServer, publishing-point or presentation generation.
- Perform one isolated experiment: cancel late work and obtain a new playlist object for a new client/presentation.
- Repeat the original the operation through the same protocol and service account; do not substitute a different client-side test.
- After it, 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.
Related codes are different
Primary distinction: end receding describes directional traversal reaching the boundary, while shutdown invalidates the whole object.
| Nearby result | Different checkpoint |
|---|---|
NS_E_PLAYLIST_END_RECEDING | Compare its own symbolic boundary and the first failing call; it must not be grouped automatically with it. |
NS_E_PLAYLIST_TOO_MANY_NESTED_PLAYLISTS | Relative to it, this neighboring result belongs to another state or validation branch even when the user-visible symptom is similar. |
NS_I_PLAYLIST_CHANGE_RECEDING | Use the object type and operation sequence to determine which result is authoritative. |
Changes that do not establish the cause
- reviving the old COM object after server shutdown.
- 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.
Technical references
- Server-Side Playlists
- System Playlist Parser Plug-ins
- Programming Playlists
- 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.