topic Re: Client proxy error 500 in Application Development and Automation Discussions

Client proxy error 500

MaryM — Wed, 13 Jul 2011 07:44:04 GMT

Hi gurus!

I am very new at this - but I'm tryinf to consume a Web Service from Sap using Abap Proxy (no PI/XI).

I am able to generete the proxy, create logical port, but the connection gives me internal server error 500: GENERAL_ERROR Error duing proxy processing (PART UNKNOWN (NULL) )

In Soamanager trace I can see the payoad_response, that seems to be fine, but excripted.

My servide provider tells me to descript it.

How can that be done? Is it something of the configuration of the proxy?

As I defined my logical port usind WSDL specifications, I have in transport security:

Encryption ecpected - false

Excryption - false.

Thank you all for your help!

MaryM

Re: Client proxy error 500

Former Member — Wed, 13 Jul 2011 09:18:07 GMT

HI Mary,

Are you talking about SAP XI/PI. Than you should do post it there.

If abap proxy is it server proxy or client proxy.

If server proxy i can help you.

Re: Client proxy error 500

MaryM — Wed, 13 Jul 2011 09:33:42 GMT

Hi,

no, I don-t have PI.

Im using client Proxy.

MaryM

Re: Client proxy error 500

ZdenekSmolik — Wed, 14 Sep 2011 03:28:42 GMT

Hi MaryM,

did you find the solution for your problem? I have the exactly same one.

Thanks,

Zdenek

Re: Client proxy error 500

MaryM — Fri, 16 Sep 2011 12:26:06 GMT

Hi Zdenek,

Error 500 is almost certainly WSDL programmation fault.

At leas it was so in my case.

Regards,

MaryM

Re: Client proxy error 500

former_member416179 — Thu, 18 Jun 2015 11:48:05 GMT

did you find the solution for your problem? I have the exactly same one.

Re: Client proxy error 500

former_member416179 — Wed, 24 Jun 2015 10:12:42 GMT

I solved the issue:

My namespace can not be reached. In the picture we can see the response on "Oxygen XML" and we can see that the namespace isn't "http://www.bottomline.com/soap/branch"

I created a Consumer Service on dotnet system that call Provider Service.

After I call Consumer Service on dotnet (bridge) and I solve the problem.

Now NameSpace can be reached :

The programmer of the provide service will check why the namespace can not be reached.

Good Luck