Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved PB2022 R3 Runtime Breaking PB2021 Application

  1. Issue
0
Votes
Undo
  1. Justin Perticone
    Justin Perticone
  2. PowerBuilder
  3. Friday, 12 April 2024 13:23 PM UTC

Hello,

Just yesterday I installed the PowerBuilder 2022 R3 3289 Runtime on one of our servers and found it broke one of our PowerBuilder 2021 applications.  We have the PowerBuilder 2021 Standard Runtime installed on the same server.  No issues found with applications using versions prior to PowerBuilder 2021.  The install was purely 2022 R3 3289 runtime only.  Uninstalling the runtime allowed our PB2021 app to run successfully again.  

Any idea why the install interfered with our PB2021 app?

Thank you!

Justin

Attachments (2)
2017 and 2021 Runtimes.PNG 2017 and 2021 Runtimes.PNG
2022 Runtime.PNG 2022 Runtime.PNG
  1. Installation
  2. PowerBuilder Runtime
How to create a new column dynamically in a datawi...
Scripting in WebBrowser control
Accepted Answer
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 15 April 2024 18:58 PM UTC
  2. PowerBuilder
  3. # Permalink
FYI: Both 2021, 2022 & 2022 R3 app EXE's should be deployed with an <AppName>.XML file that points the EXE to where the PB runtime is located that it needs to use. You should no longer be using the System Path to locate the runtime. If you are depending on the System Path, then that would explain your runtime stability issues.
Comment
There are no comments made yet.
Responses (4)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Friday, 12 April 2024 17:40 PM UTC
  2. PowerBuilder
  3. # 1

Did you migrate the app to 2022 and redeploy the executables?

Comment
Justin Perticone
  1. Justin Perticone
  2. Friday, 12 April 2024 18:36 PM UTC
I migrated one application to 2022 (was 2017) and redeployed that executable along with the PBD files. I also installed the PB2022 R3 runtime only on the server at that same time. Some of our existing PB2021 applications then began to fail. We are aware of one PB2021 app that was still able to run successfully. The 2022 app and remaining 2017 apps were all able to run fine.
  1. Helpful
There are no comments made yet.
mike S
mike S Accepted Answer Pending Moderation
  1. Friday, 12 April 2024 15:46 PM UTC
  2. PowerBuilder
  3. # 2

you need to check the paths and runtime setups.  you have something setup wrong.

Comment
Load more comments
Justin Perticone
  1. Justin Perticone
  2. Monday, 15 April 2024 17:12 PM UTC
These responses should prove helpful! Thank you Chris and Mike. Hoping the team and I find the time to work on this later this week.
  1. Helpful
Justin Perticone
  1. Justin Perticone
  2. Monday, 15 April 2024 18:58 PM UTC
After some review I was able to do this afternoon, I believe this is our issue. The XML files for our PB2021 apps are not specifying a valid path to the 2021 runtime. They work when the PB22 runtime is not installed, but all but one broke after the PB22 runtime install. I'm not sure why the one app continued to run just fine. It will take time to work with these app owners, but it seems very likely that's our issue. I'm going to mark as resolved for now. Thanks again for the input!
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 16 April 2024 19:10 PM UTC
Hi Justin;

Super glad that the XML suggestion pointed you forward to a solution. :-)

Regards .. Chris

  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.