on 02-28-2012 6:01 PM
Hi Gurus,
Hope you are doing well. I have a Proxy to SOAP synchronous interface interacting with an external system (system outside the firewall/landscape of my company).
When I am trying to post the request message from XI, I am getting the following error.
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs
In the WSDL provided by the external application, i.e. receiver WSDL, there is no attribute/field with the name 'IncludeExceptionDetailInFaults' and there is no fault string defined.
Where is this error being thrown up? Is it a network/firewall error that XI is unable to determine?
Please provide an answer as soon as possible.
regards
Debansu
check with the external system if the request was received
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Include the namespace within SOAP BODY envelope.
Please find the similar thread
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This could be due to firewall / network related reason too. Test outside pi using XMLSPY or SOAPUI and check the response. If the response is good and it happens only in PI then you can check the WSDL URL, port etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
i think it is the problem in the WSDL provider system, because it is throwing the Error with some string".NET",
do the below steps for investigating the issue
1)try pinging the URL provided in the WSDL from internet explorer.
2)if it is successfull, try to push one message from SOAP UI to by importing that WSDL, if you get any error then it is problem in the end system.
Thank You,
Madhav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.