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 error "Addressing Property is not present"

SA-21246

Summary



The Connect-SOAP fails occasionally in PRPC 6.3 SP1 system. The schema associated to WSDL does not require a SOAP header. The SOAP request generated by PRPC does not contain a SOAP header. When the Connect-SOAP is executed, an error occurs in the InvokeAxis2 activity.

Error Messages



**Date and time**,397 [         http-8180-7] [  STANDARD] [         myApp:01.01] (       axis2.engine.AxisEngine) ERROR A_HOST|AA.BBB.CC.DDDD|SOAP|Cancellation|Services|GetSuspendedMessages|AB2413867CEEAE3FCC39035C3693B925B|Rule-Connect-SOAP.AAAAA-BB-CCC-DDDD-a_name-.myActivity  - A required header representing a Message Addressing Property is not present
.
.
.

Steps to Reproduce



1. Set WS to false.
2. Execute a Connect-SOAP.

Root Cause



A defect in Pegasystems’ code or rules.

Resolution



Deploy HFix-26518 using the instructions given below:

1. Backup the database.
2. Follow the steps mentioned in pxReadme.txt found in HFix-6520-SAP.zip.
3. Run the following SQL scripts to delete the JARs from database.
delete from pr_engineclasses where pzjar= 'praxiom-1.2.13.jar';
delete from pr_engineclasses where pzjar= 'opensaml-2.6.1.jar';
delete from pr_engineclasses where pzjar= 'openws-2.5.1.jar';
delete from pr_engineclasses where pzjar= 'praxis2-1.6.2.jar';
delete from pr_engineclasses where pzjar = 'prneethi-3.0.2.jar';
delete from pr_engineclasses where pzjar = 'prrahas-module-1.6.2.jar';
delete from pr_engineclasses where pzjar = 'prrampart-core-1.6.2.jar';
delete from pr_engineclasses where pzjar = 'prrampart-module-1.6.2.jar';
delete from pr_engineclasses where pzjar= 'prwss4j-1.6.13.jar';
delete from pr_engineclasses where pzjar= 'prxml-sec-1.5.6.jar';
delete from pr_engineclasses where pzjar= 'prxmltooling-1.4.1.jar';
delete from pr_engineclasses where pzclass= 'praxis2-1.5.4.jar';
delete from pr_engineclasses where pzjar= 'opensaml-2.4.1.jar';
delete from pr_engineclasses where pzjar= 'openws-1.4.1.jar';
delete from pr_engineclasses where pzjar= 'praxiom-1.2.10.jar';
delete from pr_engineclasses where pzjar= 'prneethi-2.0.4.jar';
delete from pr_engineclasses where pzjar= 'prrahas-module-1.5.1.jar';
delete from pr_engineclasses where pzjar= 'prrampart-core-1.5.1.jar';
delete from pr_engineclasses where pzjar= 'prrampart-module-1.5.1.jar';
delete from pr_engineclasses where pzjar= 'prwss4j-1.5.10.jar';
delete from pr_engineclasses where pzjar= 'prxml-sec-1.4.0.jar';
delete from pr_engineclasses where pzjar= 'xmltooling-1.2.0.jar';
delete from pr_engineclasses where pzClass = 'prrampart-core-1.5.1.jar';
delete from pr_engineclasses where pzClass = 'praxiom-1.2.10.jar';
delete from pr_engineclasses where pzClass = 'prrampart-core-1.6.2.jar';

4. Commit the database.
5. Use Update Manager to upload DL-54204.zip.
6. Shutdown the server.
7. Delete the content in PegaTemp directory apart from PegaRULESIndex.
8. Delete %TOMCAT_HOME%\work\Catalina\localhost\prweb directory.
9. Delete contents in %TOMCAT_HOME%\temp.
10. Follow the steps mentioned in readme files inside HFix-6520-boot.zip, and update PRPC WAR file.
11. Run the following SQL scripts to delete the JARs from database.
delete from pr_engineclasses where pzjar= 'prrampart-core-1.5.1.jar';
delete from pr_engineclasses where pzClass = 'prrampart-core-1.5.1.jar';
delete from pr_engineclasses where pzjar = 'praxiom-1.2.10.jar';
delete from pr_engineclasses where pzClass = 'praxiom-1.2.10.jar';

12. Commit the database.
13. Restart the server.
Suggest Edit

Published March 24, 2016 - Updated October 8, 2020

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