• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Power builder Web Service easy soap failed suddenly

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved Power builder Web Service easy soap failed suddenly

  1. Issue
0
Votes
Undo
  1. Diana S
    Diana S
  2. PowerBuilder
  3. Wednesday, 12 August 2020 09:40 AM UTC

Dear team,

 

Pls help to have a review for below issue, thanks in advance.

We have met an issue suddenly without any codes changes on servers.

We used the web service WSDL file which engine is Easy Soap to invoke another service was failed.

The below contents are error code:

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

Power Builder version: 2017 R3 build 1858

  1. PowerBuilder (Appeon)
syncrt.exe
OLE object mscomm32
Responses (2)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 12 August 2020 15:48 PM UTC
  2. PowerBuilder
  3. # 1

Adding to what Bjarne said, EasySoap is obsolete and not secure.  You need to upgrade to HTTPClient.  Here is a useful tech article:  

https://community.appeon.com/index.php/articles-blogs/tutorials-articles/2-powerbuilder/236-call-soap-web-services-using-httpclient-object

If the Web Service you are calling uses basic authentication, then this tech article will also be useful:

https://community.appeon.com/index.php/articles-blogs/tutorials-articles/2-powerbuilder/296-how-to-use-httpclient-or-restclient-to-call-an-api-with-basic-authentication

 

Comment
Diana S
  1. Diana S
  2. Thursday, 13 August 2020 09:06 AM UTC
Hi

Thanks for your reply.

We converted the PB to .net Assembly as the HTTPClient cannot been used in .net Assembly components.

It compiled failed.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 13 August 2020 14:49 PM UTC
The .NET assembly is also obsolete. Next version of .NET... Microsoft is switching to .NET Core: https://devblogs.microsoft.com/dotnet/introducing-net-5/

I don’t understand why you want to call the Web service from a .NET assembly instead of directly from PowerScript using the HTTPClient. But if that is what you want, PowerBuilder also supports this. It has PowerScript Migrator that will convert your code to C# or if you already have a .NET DLL you want to call from PowerScript you can use the .NET DLL importer,
  1. Helpful
Diana S
  1. Diana S
  2. Monday, 17 August 2020 08:53 AM UTC
Hi Armeen,



Thanks for your reply, we will investigate this.
  1. Helpful
There are no comments made yet.
Bjarne Anker
Bjarne Anker Accepted Answer Pending Moderation
  1. Wednesday, 12 August 2020 10:41 AM UTC
  2. PowerBuilder
  3. # 2

Hi.

 

Can it be because the TLS1.0 protocol is currently being disabled almost everywhere?

We had to rewrite our SOAP call to HTTPClient to bypass these errors.

 

Bjarne

Comment
Kevin Ridley
  1. Kevin Ridley
  2. Wednesday, 12 August 2020 12:15 PM UTC
Can you contact the provider and ask them if they have changed anything? It certainly seems like something changed security wise on their side. Do you have a SOAPUI or Postman test case to run? Did you compare the old vs the current WSDL?
  1. Helpful
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.