What does HRESULT 0xC00D1520 (NS_E_PUSH_DUPLICATE_PUBLISHING_POINT_NAME) mean?

 
Previous Next
NS_E_HEADER_MISMATCH NS_E_NO_SCRIPT_ENGINE

NS_E_PUSH_DUPLICATE_PUBLISHING_POINT_NAME

Where the condition occurs

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 during an administrative or distribution operation.

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 the trace, trace input and output independently: source selection, parsing/header creation and sink selection are separate checkpoints.

Code-specific failure anatomy

A representative occurrence is when push setup attempts to create a publishing point whose valid name is already present. Capture requested name, existing point type/path, encoder template and creation race together with the object instance and the exact administrative or protocol request.

For a useful negative control, reuse the intended existing push point or choose a unique name after enumerating the collection.

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.

Evidence that separates this code

Controlled comparisonUse 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”.

Smallest useful experiment

  1. Capture 0xC00D1520, the symbolic name, the exact API/administrative action and the first failure timestamp.
  2. Preserve requested name, existing point type/path, encoder template and creation race.

Comparison with adjacent states

Primary distinction: invalid publishing-point name fails syntax; duplicate name passes syntax but collides with an existing object.

Nearby resultDifferent condition
NS_E_DATAPATH_NO_SINKthe constructed data path has no data writer capable of consuming its packets.
NS_E_HEADER_MISMATCHa command is being applied to a different ASF/media-header generation than the component currently owns.
NS_E_INVALID_PUSH_TEMPLATEthe named template cannot supply valid settings for a push publishing point.

Changes that do not establish the cause

  • changing only capitalization without checking server name comparison.

Technical references


Looking for a different code? Search another status or error code.