| Previous | Next |
| NS_E_CACHE_ARCHIVE_CONFLICT | NS_E_CACHE_ORIGIN_SERVER_TIMEOUT |
NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND
Where the condition occurs
This result (0xC00D13ED) marks the cache proxy cannot resolve or select the configured origin server. Although the visible symptom may be interrupted playback, this HRESULT is raised during an administrative or distribution operation.
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; those decisions are separate from ordinary player buffering. In the trace, keep the cache key, origin validators and policy decision together. When diagnosing this result, a cache proxy behaves both as a server to the player and as a client to the origin.
Build a reproducible incident record
| First lower-level result | Preserve the earliest Win32, socket, COM, parser or plug-in event before the HRESULT; later wrappers can map several causes to this result. |
| Controlled comparison | Use a known-good object of the same type and vary only the precondition described as “the cache proxy cannot resolve or select the configured origin server”. |
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.
| Nearby result | Different condition |
|---|---|
NS_E_CACHE_ORIGIN_SERVER_TIMEOUT | the cache proxy selected an origin but did not receive the required response before its timeout. |
NS_E_CACHE_ARCHIVE_CONFLICT | a cache download/archive operation overlaps another incompatible operation for the same content. |
NS_E_CACHE_NOT_BROADCAST | cache policy requires broadcast content but the origin metadata identifies another stream type. |
Code-specific failure anatomy
A representative occurrence is when the cache proxy cannot resolve or select the configured origin server. Capture origin host, DNS result, selected protocol and upstream URL together with the object instance and the exact administrative or protocol request.
For a useful negative control, resolve and connect to the exact origin from the cache server account and correct the origin mapping if it is wrong.
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.
Smallest useful experiment
- Capture
0xC00D13ED, the symbolic name, the exact API/administrative action and the first failure timestamp. - Preserve origin host, DNS result, selected protocol and upstream URL.
- 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.
Changes that do not establish the cause
- testing only from an administrator workstation; the cache server has its own resolver and route.
- 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.
Technical references
Looking for a different code? Search another status or error code.