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

Error while connecting to external Service via SOAP

SA-23929

Summary



User is trying to connect to an external Service via SOAP in their PRPC 6.2 SP2 based application.

User is getting the below error while hitting the SOAP Service.
        "Connect soap error: The server did not recognize the action which it received

Error Messages



Connect soap error: The server did not recognize the action which it received

Steps to Reproduce



1. Create SOAP integration and import the wsdl files.
2. Provide all the configurations for SOAP integration.
3. Configure security profile under advanced tab.
4. Create an activity to call the connect SOAP method.

Root Cause



User was making use of customized version of InvokeAxis2 Activity. User is advised to make use the out-of-the-box version of InvokeAxis2 Activity.
After reverting to out-of-the-box version of InvokeAxis2 Activity, following error traces were seen in the logs -

                com.pega.pegarules.pub.services.ConnectorException: Couldn't create SSL connectionnull
                at com.pegarules.generated.activity.ra_action_invokeaxis2_d931516c86b13149ccc538d58f97c812.step10_circum0(ra_action_invokeaxis2_d931516c86b13149ccc538d58f97c812.java:2800)
                at com.pegarules.generated.activity.ra_action_invokeaxis2_d931516c86b13149ccc538d58f97c812.perform(ra_action_invokeaxis2_d931516c86b13149ccc538d58f97c812.java:227)
                at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3061)
                …
                com.pega.apache.axis2.AxisFault: WSDoAllSender: Empty username for specified action
                at com.pega.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:173)
                at com.pega.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64)
                at com.pega.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72)
                at com.pega.apache.axis2.engine.Phase.invoke(Phase.java:318)



User is provided HFix to resolve these errors.
 
User started getting the error “SOAP Envelope can not have children other than SOAP Header and Body” and for this issue a local change was suggested.
  

Resolution




Hotfix Details:

User is advised to install in the same order using Import wizard in PRPC 6.2 SP2.
             HFix-5311 >>> HFix-5486 >>> HFix-5650 >> HFix-5550
 
Local-change Details:
 
Open the out-of-the-box InvokeAxis2 Activity, comment the step# 8 and add the following tag as input parameter as a custom security header:


             <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" />
 

Published June 16, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

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