| Previous | Next |
| NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND | NS_E_CACHE_NOT_BROADCAST |
NS_E_CACHE_ORIGIN_SERVER_TIMEOUT
Mechanism and scope
This result (0xC00D13EE) marks the cache proxy selected an origin but did not receive the required response before its timeout. 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.
What to record before changing anything
| 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 selected an origin but did not receive the required response before its timeout”. |
Do not merge nearby HRESULT values
Primary distinction: not found occurs before a usable origin endpoint exists; timeout occurs after an endpoint was selected.
| Nearby result | Different condition |
|---|---|
NS_E_CACHE_NOT_BROADCAST | cache policy requires broadcast content but the origin metadata identifies another stream type. |
NS_E_CACHE_ORIGIN_SERVER_NOT_FOUND | the cache proxy cannot resolve or select the configured origin server. |
NS_E_CACHE_CANNOT_BE_CACHED | origin metadata or cache policy forbids Windows Media Services from storing the requested content. |
Code-specific failure anatomy
A representative occurrence is when the cache proxy selected an origin but did not receive the required response before its timeout. Capture origin address, response timing, cache key, protocol and first socket event together with the object instance and the exact administrative or protocol request.
For a useful negative control, repeat one request with the same origin while tracing connect, headers and first media bytes; fix the delayed stage rather than only extending every timeout.
The tempting but misleading response is marking stale content fresh without confirming origin state. That action does not test the distinction that matters here: not found occurs before a usable origin endpoint exists; timeout occurs after an endpoint was selected.
A controlled correction
- Capture
0xC00D13EE, the symbolic name, the exact API/administrative action and the first failure timestamp. - Preserve origin address, response timing, cache key, protocol and first socket event.
- Perform one isolated experiment: repeat one request with the same origin while tracing connect, headers and first media bytes; fix the delayed stage rather than only extending every timeout.
Changes that do not establish the cause
- marking stale content fresh without confirming origin state.
- Avoid changing the publishing point, protocol, content and plug-in set in one test; such a test cannot show which precondition cleared the code.
Technical references
Looking for a different code? Search another status or error code.