| Previous | Next |
| NS_E_WMPOCX_NO_ACTIVE_CORE | NS_E_WMPOCX_NO_REMOTE_WINDOW |
NS_E_WMPOCX_NOT_RUNNING_REMOTELY
How to classify this WMP result
The symbolic result NS_E_WMPOCX_NOT_RUNNING_REMOTELY narrows 0xC00D0FD3 to the ActiveX control not running remotely condition: a remote-only operation was requested while the control is running in local mode. Keep the ActiveX control not running remotely boundary visible when a later dialog reduces it to a general media error.
An additional test is to record GetServiceType/isRemote and the method requiring remote mode; that evidence is more useful than reinstalling the Player or changing several unrelated settings at once.
What succeeds before this failure
Two rules frame this diagnosis. First, a local ActiveX control, a remoted control and the full-mode Player can share playback services while still having different window, docking and lifetime states. In this case, cross-apartment callbacks require valid marshaled interfaces; a working playback engine does not prove that the host still owns a usable event or error interface.
Representative case: The host assumes full-mode Player integration although it returned Local from GetServiceType.
State worth preserving
Capture state before Player cleanup:
- What to verify: record GetServiceType/isRemote and the method requiring remote mode.
- Artifact: GIT cookie or marshaled event-interface generation.
- State: shutdown order for host window, control, playback engine and plug-ins.
- Object identity: host process and control version, uiMode and remote/local service type.
- Underlying evidence: COM apartment type and thread that created the control.
- Correlation: IWMPRemoteMediaServices result and isRemote/docked state.
Reproduce without destroying evidence
- Use this deciding observation for this condition: record GetServiceType/isRemote and the method requiring remote mode.
- Apply the smallest supported remedy for this condition: enable supported remoting or choose the local-mode equivalent.
Related HRESULTs with different meanings
| Result | Different condition |
|---|---|
NS_E_WMPOCX_NO_ACTIVE_CORE | The ActiveX method/property was called before a usable Player core was activated |
NS_E_WMPOCX_ERRORMANAGERNOTAVAILABLE | The embedded ActiveX control cannot expose its automation error manager to the host |
NS_E_WMPOCX_NO_REMOTE_CORE | The ActiveX control cannot attach to remote Player services and falls back to local services |
Recovery at the right layer
The targeted correction for this condition is to enable supported remoting or choose the local-mode equivalent. Keep the original failing input until the same operation succeeds after one controlled change.
- Avoid reusing an interface pointer directly on another COM apartment; it can destroy the artifact or state needed to explain this result.
- Avoid destroying the host window before recording control state and the first callback failure; that can replace the original HRESULT with a secondary failure from another layer.
How to know the repair is real
Technical references
- Player control guide — documentation for this HRESULT.
- Remoting the Windows Media Player control — normative or platform material relevant to this HRESULT.
- Using skins with the control — API or format context.
- IGlobalInterfaceTable interface
Looking for a different code? Search another status or error code.