SOAP Faults

SOAP faults reflect errors encountered when you send SOAP calls via the SOAP API to Marketing Cloud Engagement. These faults indicate that the call wasn't completed successfully and give the reason for the error.

You can review the framework for a SOAP fault via the SOAP API WSDL at https://webservice.exacttarget.com/ETFrameworkFault.xsd. The SOAP API returns error codes for Server faults and logs the appropriate error information. However, the SOAP API does not return error codes or log error information for Security and Client errors.

The Detail node appears only in Server faults. Only Server faults include an API fault structure.

The following examples include the SOAP fault, the error code, and the reason for the fault.

This general exception indicated that the server can’t process the requests because the servers are offline.

  • Server Fault
  • Code: UnexpectedError = 2
  • Server Fault
  • Code: UnexpectedError = 2
  • Server Fault
  • Code: UnexpectedError = 2

The following example indicates the user does not have the proper authorization to use the SOAP API.

  • Client Fault
  • Code: AuthorizationFailure = 11
  • Resolved by enabling web service permissions for the user

The following example indicates the user's account is in authorized to access the SOAP API.

  • Client Fault
  • Code: AuthorizationFailure = 11
  • Resolved by contacting a Account Executive and activating the SOAP API

The following example indicates the SOAP API can’t determine the SOAP action in the call. The system expects the SOAP action as an HTTP header or WS-Addressing.

  • Client Fault
  • Code: UnexpectedError = 2
  • Resolved by including appropriate SOAP header
  • Normally not an issue for requests generated in .NET or Axis framework

The following examples indicate that arequest made to objects not authorized to be processed by the allowed operation during maintenance. The system checks every request for an account in maintenance mode to see if the operation requested is flagged as always on. If the request is allowed, the system performs a second check to validate the objects being requested to be processed. If any of the objects are not allowed to be processed by an always on operation during maintenance, the system rejects the whole request and returns a fault.

Member: [{0}] is In Maintenance. The operation: [{1}] is authorized to process or queue while in maintenance however the object or objects: [{2}] are not. Please remove objects from request and try again or resubmit request once the member is out of maintenance state.

  • Client Fault
  • Code: UnsupportedObject = 8
  • Resolved by removing the objects causing the exception and resubmitting the call or waiting until maintenance is over.

The system processes only Always On requests while in maintenance. It rejects all other objects and returns an In Maintenance fault.

  • Server Fault
  • Code: InMaintenance = 9

The system can’t receive synchronous requests at the time and returns this error.

Synchronous request can’t be completed at this time due to database problems. This request was not processed.

  • Client Fault
  • Code: RemoteDBConnDetected_SyncAPICallUnsupported= 1
  • Resolved by waiting for database connection or resubmitting request asynchronously