What does HRESULT 0xC00D2EFA (NS_E_MMS_NOT_SUPPORTED) mean?

 
Previous Next
NS_E_FIREWALL NS_E_SERVER_ACCESSDENIED

NS_E_MMS_NOT_SUPPORTED

What NS_E_MMS_NOT_SUPPORTED means at its owning API

When this result (0xC00D2EFA) appears, the first blocked transition is the retired MMS transport cannot be used for this connection. In practice, the mms unsupported streaming checkpoint must be reconstructed from the same URL, stream, object instance and call sequence.

Protocol-preserving retest

  1. Log 0xC00D2EFA, this result, the exact operation and the first failure time during a controlled mms unsupported retest.
  2. Do not reuse a graph, session, reader or metadata object created before the relevant configuration or resource changed before closing the mms unsupported incident.
  3. Perform one isolated test: force one currently supported transport, such as WMSP over HTTP, while keeping the same publishing resource in the mms unsupported diagnostic record.
  4. Repeat through the same API and protocol path; a different player or local-copy test is useful only as a comparison, not as proof that the mms unsupported streaming checkpoint is fixed.
  5. Confirm the expected next state and retain any new HRESULT as a separate downstream result at the mms unsupported checkpoint.

What completed, and what did not

Before the mms unsupported streaming checkpoint, earlier setup may have succeeded, but the retired MMS transport cannot be used for this connection was not completed. This is why logs should preserve both the last successful call and this result.

Network and protocol evidence

CaptureWhy it matters
Owning callRecord the API method, object identity, thread or callback and timestamp for the mms unsupported streaming checkpoint.
Values to recordoriginal URL, chosen protocol, proxy mode, resolved endpoints, connection and response timing, authentication state, session identifier and first socket or protocol result when isolating the mms unsupported case.
Object instanceNote when the reader, writer, graph, URL object, streaming session or metadata provider was created; stale state can reproduce it after configuration has changed.
Comparison caseUse one known-good resource that exercises the same mms unsupported streaming checkpoint while changing only the rejected precondition.

Misleading actions

  • treating every streaming HRESULT as generic packet loss without separating DNS, connect, response and session phases while tracing the mms unsupported path.

Nearby results are not interchangeable

Nearby HRESULTHow to compare it
NS_E_NETWORK_SINK_WRITEthe streaming sink failed while writing media data to the network connection.
NS_E_FIREWALLUse object state and operation order to decide which code is authoritative when both appear in one trace at the mms unsupported checkpoint.
NS_E_SERVER_ACCESSDENIEDthe media server rejected the client authentication or authorization context.

Technical references


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