Take a look at your PATH environment variable.

Hi Mike, 

I remember you submitted a ticket earlier to us, and actually we think it a great idea to provide zip files all run-time file. So we addressed it for 2017 R2 and R3. See this knowledgebase article: https://www.appeon.com/developers/get-help/knowledgebase/powerbuilder-runtime-files-2017-r3-1858-and-2017-r3-mr-1880.html. 

And today I urgently uploaded the runtime files for 2019 GA version as well. Pls. see: https://www.appeon.com/developers/get-help/knowledgebase/powerbuilder-runtime-files-2019-2082.html.

Best regards, Julie

Hey Mike, I agree to large extent.

PB runtime installs legacy style like .NET Framework: One, complex install to avoid duplicate files (to save disk space). Unfortunately this creates cross-app dependency. All apps must roll to new build at exactly the same moment in time.

Modern style deploy like you describe is also the way .NET Core installs. Side-by-side with each app (ample disk sizes these days). Complete app-to-app independence and much simpler installs (copy files and you're done).

I don't know how complex (read costly) it will be for Appeon to throw out all the install stuff that PowerSoft/Sybase/SAP created over three decades and write a new installer. Since Web API part (SnapObjects etc.) is founded on .NET Core it is only the PowerScript + DataWindow runtime that needs special attention.

This is worth discussing with Appeon at Elevate to indicate how widespread interest there is.
HTH /Michael

I don't know why appeon can't provide a zip with all run-time files in it that we can simply download, or install runtimes in a runtime directory during the PB install.  

then we can remove any dlls that don't apply (if we want to even bother with that), yet have everything possible to make sure we can easily get our installs to run.  

it wasn't as big deal to have to figure this stuff out ourselves when sybase would take 5 years to put out a new release, but with these fast release cycles figuring out the dlls' to include is very painful.  the names all look alike and they have no logic in terms of names to group the run times together.   it is rather sadistic.

I fixed the installation so it included the files atl100.dll, msvcr100.dll and msvcp100.dll, and verified that the files get installed. I still get the same error. I will study the deployment section some more, maybe I'll find something else that is missing.

Hi Gordon;

  Most likely, you could be missing the VC++ run-time DLL's. These are not packaged by the PB Packager Utility for the MSI. You would have to either install the VC++ run-time DLL's from Microsoft or manually copy these from your development environment to the deployed PC.

  Have a look in the PB2019 Help under the search keyword "deployment". Then proceed to "Deployment Techniques" => "PB Run-time Files". Note the following section ... Microsoft Files

  I would also suggest reading the "Core Run-time files" and "Additional Run-times" sections as well.

HTH

Regards ... Chris