Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Connect SOAP does not capture error messages



Connect SOAP to the third party Service end does not capture the error messages.

Error Messages

Caused by: java.lang.IllegalArgumentException: The MessageContext does not have an associated SOAPFault.
                at com.pega.apache.axis2.util.Utils.getInboundFaultFromMessageContext(
                at com.pega.apache.axis2.description.OutInAxisOperationClient.handleResponse(
                at com.pega.apache.axis2.description.OutInAxisOperationClient.send(
                at com.pega.apache.axis2.description.OutInAxisOperationClient.executeImpl(
                at com.pega.apache.axis2.client.OperationClient.execute(
                at com.pegarules.generated.activity.ra_action_invokeaxis2_4b10dba45aa4cd1bc2f9eca0744d3db2.step14_circum0(
                at com.pegarules.generated.activity.ra_action_invokeaxis2_4b10dba45aa4cd1bc2f9eca0744d3db2.perform(


Steps to Reproduce

1. Create a Connect-SOAP to a third party service.
2. Ensure that it returns Fail messages.

Root Cause

The root cause of the problem is with the third party service that is called using Connect-SOAP which does not send the error messages in <SOAP-ENV:Fault>  tags, instead the SOAP mesage body is sent which causes the issue.


Modify the service end to send the fault response as a part of  <SOAP-ENV:Fault> tags instead of sending in the message body. 
Suggest Edit

Published October 5, 2015 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us