What does HRESULT 0xC00D13ED (NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND) mean?

NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND

How to investigate NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND

Where the boundary sits

NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND (0xC00D13ED) marks the cache proxy cannot resolve or select the configured origin server. For NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND, although the visible symptom may be interrupted playback, this HRESULT is raised at an administrative or distribution checkpoint.

For NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND, the cache/proxy layer first applies policy, then decides whether to serve local content, revalidate it, contact an origin server, proxy it, redirect the client or reject the request. When NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND is returned, those decisions are separate from ordinary player buffering. In a NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND trace, keep the cache key, origin validators and policy decision together. While diagnosing NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND, a cache proxy behaves both as a server to the player and as a client to the origin. For NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND, 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.

Build a reproducible incident record

Do not merge nearby HRESULT values

Primary distinction: origin timeout means a selected origin failed to answer in time; not found means selection or name resolution did not yield a usable endpoint.

Code-specific failure anatomy

In a representative NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND incident, the server reaches the cache proxy cannot resolve or select the configured origin server and rejects the operation before the caller can safely assume the next stage occurred. The incident record should therefore join origin host, DNS result, selected protocol and upstream URL with the object generation and the exact administrative or protocol request.

A useful negative control is resolve and connect to the exact origin from the cache server account and correct the origin mapping if it is wrong. If that change advances the same NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND call, the result supports this boundary. If NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND remains, return to the first lower-level event instead of broadening the repair.

The tempting but misleading response is testing only from an administrator workstation; the cache server has its own resolver and route. That action does not test the distinction that matters here: origin timeout means a selected origin failed to answer in time; not found means selection or name resolution did not yield a usable endpoint. For NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND, this distinction is also why monitoring should retain the symbolic name instead of storing only a generic COM failure.

Smallest useful experiment

1. Capture 0xC00D13ED, NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND, the exact API/administrative action and the first failure timestamp.
2. Preserve origin host, DNS result, selected protocol and upstream URL.
3. For NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND, confirm that the object still belongs to the current WMServer, publishing-point or presentation generation.
4. Perform one isolated experiment: resolve and connect to the exact origin from the cache server account and correct the origin mapping if it is wrong.
5. Repeat the original NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND operation through the same protocol and service account; do not substitute a different client-side test.
6. After NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND, verify the expected next state and retain any later HRESULT as a separate pipeline result.

For NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND, repeat the test with a newly resolved server object; a stale COM pointer can make a correct configuration appear unchanged.

Changes that do not establish the cause

• testing only from an administrator workstation; the cache server has its own resolver and route.
• For NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND, a successful ping or local file open is not sufficient proof: the failing service account and Windows Media Services object must perform the same operation.
• Do not suppress NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND or replace it with a generic “media server error”; retain the symbolic code and owning operation in telemetry.

Verification outcomes

Technical references

• Windows Media Server Cache Proxy Functionality
• Creating Cache Proxy Plug-ins
• Windows Media Services HTTP Proxy Server Interaction
• Microsoft HRESULT registry

Close the incident only after NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND clears on a current object.

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