| Previous | Next |
| NS_E_CACHE_NOT_MODIFIED | NS_E_CANNOT_REMOVE_PLUGIN |
NS_E_CANNOT_REMOVE_PUBLISHING_POINT
Where the condition occurs
This result (0xC00D1450) marks the target is a cache/proxy publishing point whose lifecycle is managed differently from ordinary points. The most useful interpretation starts with the Windows Media Services object that returned the HRESULT.
Publishing points are stateful server objects with a type, path, name, plug-in collections and start/stop lifecycle; broadcast, on-demand, cache/proxy and push points do not expose identical methods or valid transitions. In the trace, read the point type and status from the live server object model. When diagnosing this result, a name in an old MMC view or retained COM interface can describe an earlier generation.
Code-specific failure anatomy
A representative occurrence is when the target is a cache/proxy publishing point whose lifecycle is managed differently from ordinary points. Capture publishing-point type, name, cache-proxy role, active requests and the administrative method invoked together with the object instance and the exact administrative or protocol request.
For a useful negative control, disable or reconfigure the cache/proxy role through the supported cache administration path instead of ordinary removal.
The tempting but misleading response is deleting its backing directory while the server object remains registered. That action does not test the distinction that matters here: publishing point removed means a stale object handle; this result means the live object type disallows the requested removal method.
Evidence that separates this code
| Controlled comparison | Use a known-good object of the same type and vary only the precondition described as “the target is a cache/proxy publishing point whose lifecycle is managed differently from ordinary points”. |
Smallest useful experiment
- Capture
0xC00D1450, the symbolic name, the exact API/administrative action and the first failure timestamp. - Preserve publishing-point type, name, cache-proxy role, active requests and the administrative method invoked.
- Perform one isolated experiment: disable or reconfigure the cache/proxy role through the supported cache administration path instead of ordinary removal.
Related codes are different
Primary distinction: publishing point removed means a stale object handle; this result means the live object type disallows the requested removal method.
| Nearby result | Different condition |
|---|---|
NS_E_CANNOT_REMOVE_PLUGIN | the requested removal would leave no instance of a required plug-in class. |
NS_E_PUBLISHING_POINT_STOPPED | the requested operation requires a running publishing point but the point is stopped. |
NS_E_WRONG_PUBLISHING_POINT_TYPE | a cache/proxy-only or ordinary publishing-point method is being used on the other object type. |
Changes that do not establish the cause
- deleting its backing directory while the server object remains registered.
- 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.