| Previous | Next |
| NS_E_PLUGIN_ERROR_REPORTED | NS_E_PLAYLIST_PLUGIN_NOT_FOUND |
NS_E_SOURCE_PLUGIN_NOT_FOUND
Diagnosing NS_E_SOURCE_PLUGIN_NOT_FOUND in Windows Media Services
What the server is validating
This result (0xC00D157E) marks no enabled data source advertises support for the requested URL prefix or source. The code identifies a narrow server contract, so diagnosis should preserve the object generation and the first native return.
Windows Media Services selects plug-ins by class, registration, enabled state and advertised format or protocol., the server may successfully load one plug-in class while failing to find the data source, parser or script engine required by a particular request. In a this result trace, record the selected plug-in CLSID, class, load type, enabled state and custom error event. While diagnosing it, plug-in discovery and plug-in execution fail differently. 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.
Code-specific failure anatomy
In a representative incident, the server reaches no enabled data source advertises support for the requested URL prefix or source and rejects the operation before the caller can safely assume the next stage occurred. The incident record should therefore join source URL/prefix, DataSources collection, enabled flags, registration and requested access method with the object generation and the exact administrative or protocol request.
A useful negative control is enable/register the matching file, network, HTTP-download, push or custom data source and retry the same URL. If that change advances the same this result 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 changing the playlist parser; the server has not yet obtained source bytes. That action does not test the distinction that matters here: playlist plug-in not found occurs after source access when no parser accepts the playlist format. 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 | source URL/prefix, DataSources collection, enabled flags, registration and requested access method. |
| Owning object | Record the server, publishing point, playlist, namespace node, plug-in or cache item that returned this result, 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 “no enabled data source advertises support for the requested URL prefix or source”. |
| Security-sensitive data | Log identifiers, lengths, hashes and redacted URLs where possible; do not publish passwords, authorization files or unrestricted client data. |
Smallest useful experiment
- Capture
0xC00D157E, it, the exact API/administrative action and the first failure timestamp. - Preserve source URL/prefix, DataSources collection, enabled flags, registration and requested access method.
- confirm that the object still belongs to the current WMServer, publishing-point or presentation generation.
- Perform one isolated experiment: enable/register the matching file, network, HTTP-download, push or custom data source and retry the same URL.
- 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.
Keep the post-fix server event and object status so a later downstream HRESULT is not mistaken for recurrence of this one.
Related codes are different
Primary distinction: playlist plug-in not found occurs after source access when no parser accepts the playlist format.
| Nearby result | Different checkpoint |
|---|---|
NS_E_PLAYLIST_PLUGIN_NOT_FOUND | Compare its own symbolic boundary and the first failing call; it must not be grouped automatically with it. |
NS_E_PLUGIN_ERROR_REPORTED | Relative to it, this neighboring result belongs to another state or validation branch even when the user-visible symptom is similar. |
NS_E_DATA_SOURCE_ENUMERATION_NOT_SUPPORTED | Use the object type and operation sequence to determine which result is authoritative. |
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
- changing the playlist parser; the server has not yet obtained source bytes.
- do not erase the first HRESULT by repeatedly clicking Apply; later calls can replace the thread error information and hide the component that rejected the 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
- Plug-in classes in Windows Media Services
- Using Internal Events to Identify Errors
- System Media Parser Plug-ins
- 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.