Error accessing the SOAP service activity from an external system
Hi,
Im getting the below error in the logs. Please let me know if I need to make any changes in my SOAP service/Service activity for this error to be resolved.
2016-07-26 16:36:29 TRACE received:673 - Received response [<?xml version="1.0"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/
envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.o
rg/2001/XMLSchema-instance">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Failed to retrieve Rule-Service-SOAP instance TakeSIRequests.SI.Details using access group UserAccesGroup</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>] for request [<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Bod
y><ns3:Details xmlns:ns3="http://www.unisys.com/Pega/" xmlns=""><ApplicationID>LEIDA100</ApplicationID><ApplicationType>Refugee</Application
Hi,
Im getting the below error in the logs. Please let me know if I need to make any changes in my SOAP service/Service activity for this error to be resolved.
2016-07-26 16:36:29 TRACE received:673 - Received response [<?xml version="1.0"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/
envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.o
rg/2001/XMLSchema-instance">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Failed to retrieve Rule-Service-SOAP instance TakeSIRequests.SI.Details using access group UserAccesGroup</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>] for request [<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Bod
y><ns3:Details xmlns:ns3="http://www.unisys.com/Pega/" xmlns=""><ApplicationID>LEIDA100</ApplicationID><ApplicationType>Refugee</Application
Type><Priority>High</Priority><CaseType>FAM</CaseType><SecondaryModality>true</SecondaryModality><ApplicantInformation><FamilyName>Test1</Fa
milyName><GivenName>Test2</GivenName><Gender>M</Gender><Citizenship>USA</Citizenship><MaritalStatus>M</MaritalStatus></ApplicantInformation>
</ns3:Details></SOAP-ENV:Body></SOAP-ENV:Envelope>]
2016-07-26 16:36:29 DEBUG WebServiceTemplate:771 - Received Fault message for request [SaajSoapMessage {http://www.unisys.com/Pega/}Details]
2016-07-26 16:36:29 TRACE SaajUtils:184 - SOAPElement [com.sun.xml.internal.messaging.saaj.soap.ver1_1.Fault1_1Impl] implements SAAJ 1.3
Exception in thread "main" org.springframework.ws.soap.client.SoapFaultClientException: Failed to retrieve Rule-Service-SOAP instance TakeSI
Requests.SI.Details using access group UserAccesGroup
Regards,
Rashmi
***Updated by moderator: Lochan to add Category***
Accepted Solution
Updated: 27 Jul 2016 6:47 EDT
Commonwealth Bank Group
IN
Hi All,
I debugged and found that the external system was not sending the 'SOAP action' and once this was sent, It worked fine.
Thanks for all your time.
Regards,
Rashmi
Pegasystems Inc.
US
- Could you provide an example URL that is used to call the SOAP service?
- I see that the error mentions "UserAccesGroup" where the word "Access" ends with only one "s" intead of "ss". Please verify that this name is correct.
Commonwealth Bank Group
IN
Hi Jeff,
Not just the "UserAccesGroup", I have tried with Admin and many other access groups (Changed the access group in the service package), but I still get the same error with just the access group replaced with the access group I use.
Pegasystems Inc.
US
Did you check "Specify customs SOAP action URI"?
If so, you need the Service Method Name appended to the end of the URL. Without it checked, the Pega generated URL should work.
Pegasystems Inc.
CA
Could you please confirm if the three keys of your Service SOAP rule are:
Service Package: TakeSIRequests
Customer Class: SI
Customer Method: Details
Accepted Solution
Updated: 27 Jul 2016 6:47 EDT
Commonwealth Bank Group
IN
Hi All,
I debugged and found that the external system was not sending the 'SOAP action' and once this was sent, It worked fine.
Thanks for all your time.
Regards,
Rashmi