| Previous | Next |
| NS_S_CALLPENDING | NS_S_STREAM_TRUNCATED |
NS_S_CALLABORTED
Windows Media operation was aborted by the client
NS_S_CALLABORTED is HRESULT 851969 (0x000D0001) from Windows Media. AllStat describes it as “The requested operation was aborted by the client.” The severity bit indicates a nonfailure result, but the value carries a specific condition that must not be collapsed into plain S_OK.
In the legacy Windows Media pipeline or Player state, this result means that the requested operation was aborted by the client. Acceptance depends on the returned state and outputs, not only on the cleared severity bit.
Where the status is encountered
- Windows Media source, reader, writer, or renderer callbacks; log the exact method and object state instead of interpreting the constant outside that contract.
- Windows Media Player SDK automation; log the exact method and object state instead of interpreting the constant outside that contract.
- Media graph, playlist, image, rights, or buffering state; log the exact method and object state instead of interpreting the constant outside that contract.
Because it is informational, a language binding may expose it as success and hide the symbolic distinction. Keep the original HRESULT available until the code-specific branch has run.
What must be true before accepting it
Verify that the cancellation was requested by the correct client action and partial side effects are reconciled. This check separates a legitimate it outcome from code that ignores an incomplete or altered operation.
Before retrying it, classify its effects as completed, partial, pending, cancelled, adapted, or terminal.
Evidence and telemetry
- preserve client action that requested abort.
- preserve operation identifier.
- preserve bytes or samples processed.
- preserve temporary artifacts.
- preserve object state after cancellation.
Also record ns_s_callaborted_operation, ns_s_callaborted_state_before, ns_s_callaborted_state_after, UTC time, process and thread identifiers, component version, and a correlation ID. When logging it, redact secret payloads but preserve stable identifiers and hashes needed for correlation.
Correct handling and recovery
Stop waiting for normal completion, release transient resources, and remove partial output. Restart only from a clean state when the user requests the operation again.
Retry it only when a documented input or state has changed. Do not immediately repeat it when the same stable state would produce the same informational result.
Difference from nearby results
It must be distinguished from ordinary S_OK and from failure-severity values in the same API family; its documented state changes control the next action.
The distinction around it determines whether the caller stops, waits, consumes output, or changes state.
Practical scenario
A user cancels an online media open. The application closes the network reader, clears the temporary buffer, and leaves the playlist item available for a later retry.
A regression test should reproduce it, assert the relevant outputs and state, then change only the decisive condition and verify the expected neighboring result or ordinary completion.
References
- Microsoft: Windows Media Format SDK error codes — official Microsoft material used to interpret it.
- Microsoft: Windows Media Player SDK
- Microsoft: Windows Media Player buffering event
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.