1. Bjarne Anker
  2. PowerBuilder
  3. Monday, 30 March 2020 20:31 PM UTC



We have invoked a web service for several years now, but it suddenly stoppet working from PowerBuilder last Friday.

We have not upgraded the application in over a year.

The web service is hosted in Azure and they use CloudFlare in front as an accelerator and firewall.

I can access the WSDL for the web service from Google Chrome and I've tested the service calls from SoapUI.

But it will not respond from PowerBuilder using an EasySoap proxy.

The call throws this exception:

"Error negotiating secure connection : error:00000001:lib(0):func(0):reason(1)"


I got an alternative URL pointing directly to Azure (bypassing CloudFlare), and it responds as it should.

But every IP adress needs to be added to an accept list, which sounds like is not an option when I ask the supplier of the web service.


Do you have any idea what can cause this?

Is there a workround and/or adjusment needed in CloudFlare for this?



Bjarne Anker

Maritech Systems AS


Bjarne Anker Accepted Answer Pending Moderation
  1. Monday, 30 March 2020 21:08 PM UTC
  2. PowerBuilder
  3. # 1

The funny thing is, that every time I make a change in the proxy object PowerBuilder just quits without any error.

I migrated the code from 2017 R2 to 2019 earlier today.


I know about the new HTTPClient and have used it quite a lot, but I’m not sure how to rewrite the soap calls into HTTPClient calls.

I guess I need to figure out the correct URL’s, set the correct headers and add the xml as a payload.

But this is something we need to look into sooner than later anyway.

TLS1.0 is about to be fazed out, so It looks like we don’t have any other option.



  1. Bjarne Anker
  2. Tuesday, 31 March 2020 05:47 AM UTC

Will look into it for sure. :)

Great if anyone else had similar issues and have some more examples on how to convert from Soap to HTTPClient.

  1. Helpful
  1. Kevin Ridley
  2. Tuesday, 31 March 2020 13:14 PM UTC
No issues but lots of experience. If you are successfully using SOAPUI, just view the raw request and recreate it in the HTTPClient. I've done many side projects providing working POC's for companies using HTTPClient and also Oauth/REST. Feel free to contact me via LinkedIN if you would like to go down that road.

Kevin Ridley
  1. Helpful
  1. Bjarne Anker
  2. Thursday, 2 April 2020 11:29 AM UTC
Thanks Kevin.

I will look into using a plugin in C# first.

If that fails, I will reach out. :)

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 30 March 2020 20:41 PM UTC
  2. PowerBuilder
  3. # 2

Hi Bjarne;

   Have you tried using the .NET SOAP feature instead of the older EasySOAP one?

Regards ... Chris

PS: For the long run, PB's SOAP features were replaced by the new HTTPClient object class.

There are no comments made yet.
  • Page :
  • 1

There are no replies made for this question yet.
However, you are not allowed to reply to this question.