1. Durai Raj
  2. PowerBuilder
  3. Tuesday, 13 December 2022 13:35 PM UTC

Hi There,

Am using power builder 2019 R3 ( version for my project. As per current PB version am using HTTP client to consume web service. before this version the web service consume happened through soap connection & there was a web service proxy configured. I believe, there is no proxy configurations required when using HTTP client method however still the old proxy configuration are present in one of my PBL file.

Am getting an error 'Cannot parse the WSDL file' when am trying to deploy the power builder application. Please advise whether any power builder component we have to import in order to resolve the issue or should i remove the old proxy configurations itself to resolve the issue.

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 13 December 2022 15:05 PM UTC
  2. PowerBuilder
  3. # 1

Hi Durai;

  The HTTPClient object class does not use or support the old SOAP WSDL language. The WSDL error that you are receiving is most likely due to some old SOAP object code still being used somewhere OR even a WSDL based DataWindow (Web Service DWO) from an older PB release that is still active in your App's code.  HTH

Regards .... Chris

There are no comments made yet.
Durai Raj Accepted Answer Pending Moderation
  1. Tuesday, 13 December 2022 15:25 PM UTC
  2. PowerBuilder
  3. # 2

Hi Chris,

Thanks for your response. Should i remove all existing soap proxy configurations to resolve the WSDL parsing issue.

Let me try and get back.


  1. Chris Pollach @Appeon
  2. Tuesday, 13 December 2022 21:39 PM UTC
Hi Durai;

Might I first suggest ...

1) Locate your "Working" PB.INI file as listed in the PB IDE's "System Options" dialogue.

2) Check this INI for the following entry ...



3) If the above entries are missing, add then to your working PB.ini & save it..

4) Restart your IDE

5) Perform a "full build" of your App from your App's "Target".

5) If no build errors, now try to build your App's EXE again (deploy).


Regards ... Chris
  1. Helpful
  1. Jesper Trebbien
  2. Friday, 21 July 2023 07:42 AM UTC
Hi Chris

In connection with migration from 2017 R3 to 2022.1900 I have encountered the problem 'Cannot parse the WSDL file'.

Adding 'GenerateWSAssembliesOnCompile=YES' and 'debug_ws_metadata=YES' in PB.INI solves the problem so that the project can be deployed without errors.

WS-Datawindow also works when I run the deployed program on my development client.

If I distribute the program to other clients datawindow retrieve returns -1.

How can it be and is there a way to make i work?

Regards Jesper

  1. Helpful
  1. Chris Pollach @Appeon
  2. Friday, 21 July 2023 14:19 PM UTC
Hi Jesper;

All support for the old SOAP based WSDL feature was removed in PB 2021

FYI: https://docs.appeon.com/pb/upgrading_pb_apps/Removes_EasySoap.html

If you still want to consume SOAP web services in PB 2022, you will need to ...

1) Use the new HTTPClient object to access the SOAP WS & it's XML

2) Use the PB built-in PBDOM feature to read the XML data stream.

FYI: https://docs.appeon.com/pb2022/troubleshooting_guide/tr_050.html


Regards .. Chris
  1. Helpful
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Saturday, 22 July 2023 05:55 AM UTC
  2. PowerBuilder
  3. # 3


For my documentation:

"Adding 'GenerateWSAssembliesOnCompile=YES' and 'debug_ws_metadata=YES' in PB.INI " ... but WHERE? Which section of the ini file?


  1. Miguel Leeuwe
  2. Saturday, 22 July 2023 13:17 PM UTC
Okay, I found the answer already on https://docs.appeon.com/pb2022/pbug/PBINI_settings.html

It's the [Data Window] section.
  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.