| Previous | Next |
| NS_E_UNSUPPORTED_LOAD_TYPE | NS_E_INVALID_PUBLISHING_POINT_NAME |
NS_E_INVALID_PLUGIN_LOAD_TYPE_CONFIGURATION
Mechanism and scope
This result (0xC00D1454) marks plug-in registration exposes no supported activation mode. Although the visible symptom may be interrupted playback, this HRESULT is raised during an administrative or distribution operation.
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.
Reading the second result
| Controlled comparison | Use a known-good object of the same type and vary only the precondition described as “plug-in registration exposes no supported activation mode”. |
Test the owning precondition
- Capture
0xC00D1454, the symbolic name, the exact API/administrative action and the first failure timestamp. - Preserve registered load flags, CLSID server entries, bitness, plug-in class and configuration import source.
- Perform one isolated experiment: repair registration so at least one supported in-process or out-of-process mode is declared, then reload the plug-in collection.
Related codes are different
Primary distinction: unsupported load type rejects one requested mode; invalid configuration means the available-mode set is empty or contradictory.
| Nearby result | Different condition |
|---|---|
NS_E_INVALID_PUBLISHING_POINT_NAME | the proposed publishing-point name violates naming or path rules. |
NS_E_UNSUPPORTED_LOAD_TYPE | a plug-in does not implement the requested in-process or out-of-process activation mode. |
NS_E_TOO_MANY_MULTICAST_SINKS | more than one multicast data writer is being enabled for one publishing point. |
Changes that do not establish the cause
- choosing another load mode in MMC when none is actually registered.
- 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.