Discussion

4
Replies
203
Views
Manash_LSA Member since 2008 47 posts
Phalanx Consultancy Limited
Posted: 5 years ago
Last activity: 5 years 1 month ago
Closed

SOAP Service returning error

I am new to SOAP integration and had been working with a SOAP service. I generated the WSDL and uploaded into SOAP UI for testing. When i run the WSDL by proving some parameters in SOAP UI, there is an error throwing during run time. The error is as follows.

 

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <SOAP-ENV:Body>
      <SOAP-ENV:Fault>
         <faultcode>SOAP-ENV:Server</faultcode>
         <faultstring>Couldn't parse SOAP request envelope</faultstring>
      </SOAP-ENV:Fault>
   </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

 

WSDL is

<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:PegaRULES:SOAP:AWDPackage:LTSSI-Work-MsgCase-Scanning">
   <soapenv:Header/>
   <soapenv:Body>
      <urn:CreateNewScannedMsg soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
         <InquiryDate xsi:type="xsd:date">?</InquiryDate>
         <transactionRef xsi:type="xsd:string">?</transactionRef>
         <caseIndexDocId xsi:type="xsd:string">?</caseIndexDocId>
         <InquirerName xsi:type="xsd:string">?</InquirerName>
         <InquirerID xsi:type="xsd:string">?</InquirerID>
         <InquiryAmount xsi:type="xsd:decimal">?</InquiryAmount>
         <awdObjectKey xsi:type="xsd:string">?</awdObjectKey>
         <Currency xsi:type="xsd:string">?</Currency>
         <casetype xsi:type="xsd:string">?</casetype>
      </urn:CreateNewScannedMsg>
   </soapenv:Body>
</soapenv:Envelope>

 

I am not sure how to debug this as the error code indicates

 

The SOAPMessage object could not be processed because of a processing error, not because of a problem with the message itself.

I am using SOAP 1.1 specification and want to understand how can I debug the problem.

 

Data Integration
Moderation Team has archived post
Share this page LinkedIn