Client Internal Error in SOAP response

[Former Member]

Hi experts,

in PI 7.0 in a SOAP synchronous receiver channel, protocol HTTPS with certificate , I get this error:

<?xml version="1.0"?>

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">

<env:Body>

<env:Fault>

<faultcode>env:Client</faultcode>

<faultstring>Internal Error</faultstring>

</env:Fault>

</env:Body>

</env:Envelope>

If I cut and paste the PI message in SOAP UI it works perfectly and web service give the correct response.

I've checked DO NOT USE Soap Envelop because Envelop is created by me with XSLT mapping.

In CC I'm using SOAP Action that I retrieved from "Action" in SOAP UI.

In module I have Transform text/xml;charset=utf-8

and

soap XMBWS.NoSOAPIgnoreStatusCode true

What could be the problem?

Thanks

Fabio

[Former Member · Accepted solution]

We found the problem.

Our XI 7.0 works only with HTTP 1.0, but web service owner only manage HTTP 1.1.

Unfortunately, there is no direct solution.

Thanks to everybody.

Fabio

[justin_santhanam]

Hello Fabio,

TCPGW tool is pretty simple tool. We have to do some more debugging to find out where the actual problem is. Let us know if you have any questions in running the TCPGW tool.

I'm thinking this will give us a lead , which we can take to the next step.

- Open the aiitcpgw.jar file

- Listen Port just enter some number - 9001 (for example)

- Target hostname - Put your WS endpoint host name

- Target Port - Put 443 (because it's HTTPS)

Check your IP address (PI server IP , because you are doing the SOAP UI from PI server)

- In SOAP UI, endpoint change the host name to your IP address and Port to 9001

Test the SOAP UI and capture the Request Parameters in the tool.

(also check with the folks from target WS team to see what they received, definitely they should have received something, because you said SOAP UI calls are working)

Same thing in your PI comm.channel , instead of giving the actual host name  in the Webservice endpoint, give the IP address: Port and test the scenario.

- Now see the Request parameters in the tool, see if it's the same or missing something.

I'm sure this is hectic task, but we have to figure it out where the problem is.. This always helped me, for an example, the SOAP Ui will set some headers and it will work fine, where as when I'm sending the request from PI, the headers might not have been set, so I need to adjust the settings to set the headers (just giving you an example)...

Let us know the findings!

[Former Member]

Hi,

my questions:

1) endpoint is : https;//ivi.gatrdw.nl/iviservice

but is not possible to put "/" in target hostname

2) if  I put XI http address in endpoint it doesn't work, I get a timeout error

3) I'm through a proxy, it changes something?

Thanks!

[justin_santhanam]

https://ivi.gatrdw.nl/iviservice

Change it to https://<IPADDRESS>:9001/ivservice in SOAPUI

in the TCPGW - ivi.gatrdw.nl as host and 443 as port.

Thanks!

[Former Member]

If I use:

https://<IPADDRESS>:9001/iviservice

I get "Connection time out" ...

[former_member186851]

Fabio,

Connection time out is because of network issue.

we are facing the same now and network team is working on that.

[justin_santhanam]

Raghu,

It's not because of the network issue. Please read the thread from the start. The time out is because I asked Fabio to change the actual endpoint to pass through PI (TCPGW).

Thnx

[justin_santhanam]

Fabio,

I'm not sure if the Proxy you mentioned is playing into picture here .. Please wait for other experts opinion on this. I'm not sure how to handle the proxy in TCPGW. Sorry!!

Thanks

[justin_santhanam]

Did you check with Basis/Network guys whether there is any requirements to open up the Port from your PI system, so that it can communicate?

Thnx.

[Former Member]

Hi Justin,

I'm calling same WS from PI server with SOAPUI and it works, so I don't think this is the problem.

[justin_santhanam]

Fabio,

Just so I understand, you are saying you installed the SOAP UI on the PI Application system and calling it from there, correct? Not calling the SOAP UI from your local PC. Please confirm.

Thanks!

[Former Member]

Yes,

I have access to PI Server, I have installed SOAP UI on PI server and tested from there.

Other info: in SOAPUI I have cut and pasted xml message taken from SXMB_MONI payload, without doing any changes, and it works.

[justin_santhanam]

Hi Fabio,

Can you try using the TCPGW tool to see what actual request been sent to the target and whether the proper response has been received?

Give a try and let us know!

Note - 856597

Reference - /people/stefan.grube/blog/2007/03/29/troubleshooting-soap-http-and-mail-adapter-scenarios-with-tcpgateway

Thnx.

[Former Member]

Seems difficult to use.

I'm now in contact with a person of target system. He said to me that he can't see any WS call from our system. So in fact my request doesn't reach target system.

What it means? What is the problem?

[Former Member]

Hi everybody,

certificates seems ok, but still same message "Client Internal Error".

Any idea?

Thanks

Fabio

[former_member186851]

Hello Fabio,

check whether all the required certificates are deployed in PI.

[Harish]

Hi Fabio,

Did you imported the root and intermediate certificate as well in PI? refer the below blog for certificate chain import

regards,

Harish

[Former Member]

Hi Harish and Sritharan,

I'm checking this point that must be have done by basis.

I have 2 certificates:

1) a HTTPS certificate (transport certificate) using for setting the https connection

2) a Certificate to be trusted

I've found that the second certificate wasn't present in the MMC Trusted Root Certification Authorities.

Now I've imported it. After this import I have to restart the PI server?

The First certificate has to be present in MMC? where?

In Visual Administrator I had already imported certificates in the Keystore.

thanks,

Fabio

[former_member186851]

Helo Fabio,

Refer the below link

http://scn.sap.com/docs/DOC-42965

I guess second certifcate imported in NWA should be fine.

Yes,Better do a restart.