What does HRESULT 0xC00D13F0 (NS_E_CACHE_CANNOT_BE_CACHED) mean?

NS_E_CACHE_CANNOT_BE_CACHED

Where the condition occurs

This result (0xC00D13F0) marks origin metadata or cache policy forbids storing the requested content. The most useful interpretation starts with the Windows Media Services object that returned the HRESULT.

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.

Interpret the retest

Test the owning precondition

1. Capture 0xC00D13F0, the symbolic name, the exact API/administrative action and the first failure timestamp.
2. Preserve Cache-Control directives, expiration information, policy plug-in decision, content type and requested persistence mode.
3. Perform one isolated experiment: proxy without persistence or change the authoritative origin/cache policy when caching is intentionally allowed.

Do not merge nearby HRESULT values

Primary distinction: not modified confirms an existing cached representation; cannot be cached rejects creating or updating one.

Changes that do not establish the cause

• forcing a file into the cache directory; that bypasses version and policy metadata.

Technical references

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