| Previous | Next |
| NS_E_HEADER_MISMATCH | NS_E_NO_SCRIPT_ENGINE |
NS_E_PUSH_DUPLICATE_PUBLISHING_POINT_NAME
Diagnosing NS_E_PUSH_DUPLICATE_PUBLISHING_POINT_NAME in Windows Media Services
Where the boundary sits
This result (0xC00D1520) marks push setup attempts to create a publishing point whose valid name is already present. Although the visible symptom may be interrupted playback, this HRESULT is raised at an administrative or distribution checkpoint.
A server distribution path connects a data source, parser, media header and one or more data sinks., push publication adds an encoder-to-server control path, while client delivery uses a separate protocol and connection state. In a this result trace, trace input and output independently: source selection, parsing/header creation and sink selection are separate checkpoints. 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 push setup attempts to create a publishing point whose valid name is already present and rejects the operation before the caller can safely assume the next stage occurred. The incident record should therefore join requested name, existing point type/path, encoder template and creation race with the object generation and the exact administrative or protocol request.
A useful negative control is reuse the intended existing push point or choose a unique name after enumerating the collection. 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 only capitalization without checking server name comparison. That action does not test the distinction that matters here: invalid publishing-point name fails syntax; duplicate name passes syntax but collides with an existing object. 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 | requested name, existing point type/path, encoder template and creation race. |
| 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 “push setup attempts to create a publishing point whose valid name is already present”. |
| 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
0xC00D1520, it, the exact API/administrative action and the first failure timestamp. - Preserve requested name, existing point type/path, encoder template and creation race.
- confirm that the object still belongs to the current WMServer, publishing-point or presentation generation.
- Perform one isolated experiment: reuse the intended existing push point or choose a unique name after enumerating the collection.
- 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.
Comparison with adjacent states
Primary distinction: invalid publishing-point name fails syntax; duplicate name passes syntax but collides with an existing object.
| Nearby result | Different checkpoint |
|---|---|
NS_E_DATAPATH_NO_SINK | Compare its own symbolic boundary and the first failing call; it must not be grouped automatically with it. |
NS_E_HEADER_MISMATCH | Relative to it, this neighboring result belongs to another state or validation branch even when the user-visible symptom is similar. |
NS_E_INVALID_PUSH_TEMPLATE | Use the object type and operation sequence to determine which result is authoritative. |
Verification outcomes
| 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 only capitalization without checking server name comparison.
- 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
- Windows Media Services 9 Series SDK
- Sending ASF Data to a Publishing Point
- Media Streaming Server Protocol Summary
- 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.