Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

"INTERNAL">WS_ADAPTER_SYS_ERROR

Hi Experts,

I am stuck with an error in WS adapter(Message protocol: WS 1.0)

The scenario is SOAP to WS(Third party to ECC) synchronous type.

Third party system <--> BizTalk <--> PI(7.31 dual stack) <--> SAP

In SXMB_MONI the error is

    <SAP:Category>XIServer</SAP:Category>

   <SAP:Code area="INTERNAL">WS_ADAPTER_SYS_ERROR</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>System error while calling Web service adapter: Error when initializing SOAP client application: &#39;Error when initializing SOAP client application: &quot;SRT: Unexpected failure in SOAP processing occurre&quot;&#39;</SAP:Stack>

In Adapter Engine: message monitoring, the error is:

Transmitting the message using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIServer:WS_ADAPTER_SYS_ERROR::::::System error while calling Web service adapter:
Error when initializing SOAP client application: &#39;Error when initializing SOAP client application: &quot;SRT: Unexpected failure in SOAP processing occurre&quot;&#39;


and the message is getting cancelled in Adapter engine.


Is this something like PI is not receiving the response from ECC system? or something went wrong in WS adapter. I am not authorized to check the messages in ECC.


I have checked WS adapter status in SOAMANAGER, the connection is working fine. Can you suggest where do can I check the WS adapter channel status and processed message logs on WS adapter?

    

Former Member
Former Member replied

Hi All,

Thanks for your suggestions.

The issue is solved now.

What has been done:

The service binding has been regenerated in R3 system SOAMANAGER and the same has been updated in PI system RFC receiver communication channel.

The system username used in PI and Biztalk were unlocked and passwords were re-generated. Installing the SoapUI tool in client remote desktop helped in analyzing the exact issue

at the webservice receiver adapter.

BR,

Sunitha

0 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question