| Previous | Next |
| WS_E_ENDPOINT_UNREACHABLE | WS_E_ENDPOINT_TOO_BUSY |
WS_E_ENDPOINT_ACTION_NOT_SUPPORTED
WS_E_ENDPOINT_ACTION_NOT_SUPPORTED is a Windows Web Services API HRESULT. It means that the service endpoint rejected the requested message action or operation because it is not implemented, published, or permitted by that endpoint.
What to check for WS_E_ENDPOINT_ACTION_NOT_SUPPORTED
- Compare the requested action, SOAP action or operation name with the active service contract.
- Check client and server versions, routing rules and endpoint bindings after deployment changes.
- Do not reinterpret an unsupported action as a transport failure.
Diagnostic interpretation of WS_E_ENDPOINT_ACTION_NOT_SUPPORTED
WS_E_ENDPOINT_ACTION_NOT_SUPPORTED has the HRESULT value 0x803D0011. AllStat records the condition as “The operation was not supported by the remote endpoint.”. For WS_E_ENDPOINT_ACTION_NOT_SUPPORTED, in practice, interpret that wording at the boundary owned by the Windows component or COM interface that returned the HRESULT, rather than treating the value as a generic Windows message.
Evidence to capture for WS_E_ENDPOINT_ACTION_NOT_SUPPORTED
- Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x803D0011 value before a wrapper converts it to an exception or Boolean result.
- Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions WS_E_ENDPOINT_ACTION_NOT_SUPPORTED or the ws / endpoint / action / supported operation.
- For WS_E_ENDPOINT_ACTION_NOT_SUPPORTED, compare the failing machine with a working one at the same configuration boundary: component version, policy, registration, identity, and target resource.
Retry and recovery for WS_E_ENDPOINT_ACTION_NOT_SUPPORTED
Retry WS_E_ENDPOINT_ACTION_NOT_SUPPORTED only when the owning API documents a transient state or after the condition described as “The operation was not supported by the remote endpoint.” has changed. For WS_E_ENDPOINT_ACTION_NOT_SUPPORTED, configuration, policy, format, and authorization failures normally require correction first; an immediate loop can hide the original call site and add secondary errors.
Looking for a different code? Search another status or error code.