3.1.4.2 SOAP Faults

This section documents the SOAP faults specified for use by servers that implement the IMDA protocol extensions. These faults SHOULD be used by servers while processing a WS-Transfer message that uses IMDA extensions to indicate to the client that a server-side error has occurred. Most of the following faults are adopted from the WS-Management [DMTF-DSP0226] protocol, and some are from WS-Transfer [WXFR] or WS-Addressing [WSAddressing]; IMDA assigns these faults a specific meaning within the context of a WS-Transfer operation that uses the IMDA extensions.

These faults in this section represent a common set shared by all operations.

Server implementations are permitted to return additional faults beyond those described as follows. However, to maximize interoperability, implementations SHOULD make use of the following faults where applicable.

Some of the SOAP faults documented as follows specify English-language text in their fault reason. Server implementations are permitted to localize this text to other languages. Such localizations SHOULD maintain, to the extent possible, the same meaning as the English text supplied in this document.

All SOAP faults defined in this document MUST be sent as described in section 6 of [WSASB]. In the tables in the following sections, the following apply:

  • [Code] is the SOAP fault code.

  • [Subcode] is the SOAP fault subcode.

  • [Action] is the SOAP action URI for the fault.

  • [Reason] is a human-readable explanation of the error.

  • [Details] is an illustrative example of the fault detail. If not present, IMDA does not specify a fault detail for the fault.

The following table summarizes the faults (grouped by fault subcode) specified in this section.

Fault subcode

Description

wsman:AccessDenied

The server rejected the operation due to access control policies.

wsman:AlreadyExists

The identity object requested to be created already exists.

wsman:CannotProcessFilter

The identity attribute type was invalid for the dialect or specified an identity attribute that was invalid for the identity object.

wsa2004:DestinationUnreachable

The identity object specified as the target of the operation does not exist.

wsman:EncodingLimit

The client's request included too many elements.

wsa2004:EndpointUnavailable

Insufficient server-side resources to process the request.

wsman:FragmentDialectNotSupported

The operation specified a dialect not supported by the server.

wxf:InvalidRepresentation

Performing the operation would result in an invalid representation of an identity object.

wsman:SchemaValidationError

The client's request did not conform to the XML Schema or was syntactically invalid XML.

UnwillingToPerform

The server cannot perform the requested operation.