| Previous | Next |
| NS_E_PUBLISHING_POINT_REMOVED | NS_E_UNSUPPORTED_LANGUAGE |
NS_E_INVALID_PUSH_PUBLISHING_POINT_START_REQUEST
What the server is validating
This result (0xC00D145B) marks an administrator tried to start a push point that must be started by an encoder push connection. Treat the symbolic name as a map to the owning Windows Media Services subsystem rather than as a request to reinstall every media component.
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.
Interpret the retest
| Controlled comparison | Use a known-good object of the same type and vary only the precondition described as “an administrator tried to start a push point that must be started by an encoder push connection”. |
Smallest useful experiment
- Capture
0xC00D145B, the symbolic name, the exact API/administrative action and the first failure timestamp. - Preserve publishing-point type, source prefix, encoder push URL, active distribution connections and attempted start caller.
- Perform one isolated experiment: start the encoder push session and let the push data source activate the point.
Comparison with adjacent states
Primary distinction: invalid push publishing point validates the target itself; it rejects who initiated the start transition.
| Nearby result | Different condition |
|---|---|
NS_E_UNSUPPORTED_LANGUAGE | the requested language identifier is not supported by the server component or content contract. |
NS_E_PUBLISHING_POINT_REMOVED | the caller still holds an object for a publishing point that has been deleted from the server collection. |
NS_E_WRONG_OS_VERSION | Windows Media Services itself is running on an unsupported Windows edition/version for that release. |
Changes that do not establish the cause
- converting the point to auto-start without considering the encoder-controlled lifecycle.
- 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.