1. Jay Thangam
  2. PowerBuilder
  3. Tuesday, 28 July 2020 17:51 PM UTC

We have developed PowerBuilder Client Web Services using .NET engine to download pdf document. We didn't come across any issues in the development or even after deployment. But we are running into issues when we deployed to a PC where PowerBuilder did not installed. 

The error message says " The .NET engine is unable to start  ". Please refer below error screenshot

We are using Appeon PowerBuilder Version 2017 R2.

The deployment build includes :  

Assembly DLL , Dependent DLLs for .NET Web DLLs .


Error Screenshot:

David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Monday, 26 September 2022 13:28 PM UTC
  2. PowerBuilder
  3. # 1

I just thought that I would add to this. We have managed to get the soapconnect to work successfully using PB2019R3. We managed this by copying in the old sysbase.Powerbuilder.Webservice DLLs from PB12.5 to the same folder as the EXE.

There are four DLLs required:

I appreciate this is not supported by Appeon but while we rewite all our stuff is worth knowing that you can buy yourself sometime and still get the benefits of PB2019R3.

Happy Days


  1. Armeen Mazda @Appeon
  2. Monday, 26 September 2022 16:20 PM UTC
Very interesting workaround David! Thanks for sharing.
  1. Helpful
  1. David Peace (Powersoft)
  2. Monday, 26 September 2022 18:28 PM UTC
Yes, it allowed us to move to PB2019R3 which was really important for us. My Quality Manager was really happy becuase we didn't change much ;-)

Thanks for all the fantastic additions and we are really looking formard to the New Email feature in the road map. Will that deal with the issues of 2 factor authentication on email accounts and allow us to have automated email processes that authenticate with the new Office 365 standards?
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Monday, 26 September 2022 19:22 PM UTC
Hi David, please send this feature suggestion to product@appeon.com
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 3 August 2020 17:07 PM UTC
  2. PowerBuilder
  3. # 2

Hi Jay;

   Is your App trying to interact with .NET DLL's via the older COM interface approach?

Regards ... Chris

There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 28 July 2020 20:01 PM UTC
  2. PowerBuilder
  3. # 3

Hi Jay,

Your issue is either because required runtime DLLs of PowerBuilder are not properly installed on the machine or there is a permissions issue.  

Please be aware that the .NET features of PowerBuilder 2017 are the legacy stuff left over from Sybase days, which is deprecated in PowerBuilder 2019.

There are couple issues I see if you don't eventually move off of this.  First, the legacy SOAP client has security issues, such as does not support TLS 1.2.  Second, Microsoft is replacing .NET with .NET Core.  Third, when PowerBuilder 2017 is EOL there will no longer be tech support for this.

It would be good idea for your application roadmap that you convert your legacy Web services to REST Web APIs and .NET Core framework.  All the tools you need to do this with minimal effort is included in the PowerBuilder CloudPro subscription:

  • PowerScript Migrator: this should take care of automatically converting your existing Web services code to C# and .NET Core.
  • SnapDevelop: this will automatically create the controllers to expose the converted code as REST APIs.
  • RESTClient: requires just few lines of code to use this to call REST APIs from your PowerScript app.

Best regards,

  1. Arnd Schmidt
  2. Monday, 26 September 2022 14:30 PM UTC
  1. Helpful
  1. Chris Pollach @Appeon
  2. Monday, 26 September 2022 17:33 PM UTC
You are correct Arnd. Also, as many IT shops have disabled TLS 1.0 for security reasons. That is could be a major impediment for trying to continue to use the old SOAP features.
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Monday, 26 September 2022 17:54 PM UTC
The one in PB does not, and it has been removed from PB 2022. Please use the HTTP Client to cal SOAP Web services.
  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.