| Previous | Next |
| NS_S_TRACK_ALREADY_DOWNLOADED | NS_S_DRM_LICENSE_ACQUIRED |
NS_S_PUBLISHING_POINT_STARTED_WITH_FAILED_SINKS
Publishing point started but some data-writer sinks failed
NS_S_PUBLISHING_POINT_STARTED_WITH_FAILED_SINKS is HRESULT 857369 (0x000D1519) from Windows Media. AllStat describes it as “The publishing point successfully started, but one or more of the requested data writer plug-ins failed.” In the Windows Media Player, Windows Media Format, DRM, or Media Foundation state machine, the value reports a nonfailure state that must not be collapsed into plain S_OK.
This result is actionable completion information and may require waiting, reconciliation, fallback, or user disclosure.
Where the status is encountered
- Windows Media Player library, playlist, store, or UI plug-in callbacks; capture the exact API, object, and phase because the same numeric success severity does not define the state by itself.
- Windows Media Format source, writer, DRM, publishing-point, or installation operations;
- Media Foundation topology activation and remote-component setup;
Keep it attached to the operation that returned it. Interpreting it outside that API contract can turn a normal continuation or partial result into an incorrect retry or false completion.
What must be true before accepting it
Verify that the publishing point can serve safely without the failed sinks and every lost output path is identified. Validation of it keeps a success-severity result from becoming a broader promise than the API made.
Also confirm that returned outputs belong to the current operation generation and were not inherited from an earlier attempt.
Correct handling and recovery
Keep the publishing point online only if policy allows degraded operation, alert on each failed sink, and retry or replace sinks independently. Do not report full redundancy.
Continuation after it within the documented state machine is different from restarting the entire operation.
Difference from nearby results
A fully successful start has all requested sinks; this status means the core point is running with partial output capability.
The neighboring result changes whether output is final, more work remains, or fallback is required.
Practical scenario
A live publishing point starts streaming but its archive writer cannot open storage. Streaming remains available while operators repair archiving and mark the event as degraded.
References
- Microsoft: Windows Media Format SDK error and success codes
- Microsoft: Windows Media Player SDK
- Microsoft: Media Foundation SDK
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.