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,
Armeen

Hi Jay;

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

Regards ... Chris

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

David