-
Roland Smith
- PowerBuilder
- Thursday, 10 August 2023 06:13 PM UTC
PowerBuilder 2022 Build 1892.
With the most recent version of our app, we switched from PB 2019 to 2022. As part of that, I switched our Internet Explorer web browser controls to the built in pbcef based webbrowser control.
End user reports the control is blank. The pbcef folder is there in the PB runtime folder we deployed. Once the end user installed InfoMaker, the control started working.
We aren't using any Appeon provided tools to install, we use InstallShield. Any idea why the control didn't work until IM was installed. Are there registry setting? The help doesn't mention any.
We install the PB Runtime to:
C:\Program Files (x86)\Appeon\Shared\Powerbuilder22_1892
This folder is in the 'App Path' entry for the exe.
Hi Roland,
The problem is because the correct runtime path is not found. When you install Informaker, runtime will be installed to this machine and its path will be written to the registry, so the application can run normally.
It seems you are using PoewrBulder runtime packager (*.msi) to distribute runtime files, please note that starting from 2019 R3 GA, the MSI file no longer sets the runtime file path in the system PATH environment variable, please refer to the article below for more details.
https://docs.appeon.com/pb2019r3/application_techniques/ch09s02.html#PowerBuilder_Runtime_Packager
You can use any of the solutions below to solve the problem:
1. Change the runtimepath in the %appname%.xml(which generated when deploy application) in the application directory to C:\Program Files (x86)\Appeon\Shared\Powerbuilder22_1892.
2. Add C:\Program Files (x86)\Appeon\Shared\Powerbuilder22_1892 to the system PATH environment variable.
3. Put all the runtime files into the application directory.
Regards,
kai
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.