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

Resolved Application crashes with Runtime 21.0.0.1509

  1. How-to
0
Votes
Undo
  1. Eduardo G.
    Eduardo G.
  2. PowerBuilder
  3. Thursday, 16 June 2022 15:34 PM UTC

Hello,


With PB 2019 R3 we performed the migration of our application to PB 2021 Build 1509 and performed the distribution for a small group of users.

The users are reporting us total shutdown of the application in a window and clicking on the [Search] button. This window in PB 2019 and older versions has no problem, also it has not had any modification for half a year.

After performing many tests to locate the problem we observed that:

- With Runtime 21.0.0.1509 > DOES NOT WORK.
- With Runtime 21.0.0.1506 > NOT WORKING
- With Runtime 21.0.0.0.1288 > IT WORKS

Runtime 21.0.0.0.1311 is not available for testing.

Honestly, we do not know what can generate the error in the most current Runtime.

Has it happened to anyone?
Is there a solution?
Is it a problem that we will have to wait for the next runtime?

Thanks, I look forward to your advice and help.

 

>>>>>>> NOTE <<<<<<<

For information. Running the application from the PB IDE:
- Me with only Runtime 21.0.0.1509 installed. WINDOW WORKS
- My partner with Runtime 21.0.0.1509 / 1506 / 1288. If you have runtime 1509 or 1509 selected it DOES NOT WORK but with 1288 it DOES WORK.

 

 

Powerbuilder 12.6 and MS Decom issue
Operand type clash: bigint is incompatible with da...
Responses (6)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 20 June 2022 15:46 PM UTC
  2. PowerBuilder
  3. # 1

Hi Edwardo;

    Also, try running the PB App EXE in a lower MS-Windows "Compatibility Mode".  HTH

Regards ... Chris

Comment
There are no comments made yet.
Eduardo G.
Eduardo G. Accepted Answer Pending Moderation
  1. Monday, 20 June 2022 11:46 AM UTC
  2. PowerBuilder
  3. # 2

Support ticket open:

https://www.appeon.com/standardsupport/track/view?id=8552

Comment
There are no comments made yet.
Olan Knight
Olan Knight Accepted Answer Pending Moderation
  1. Friday, 17 June 2022 14:13 PM UTC
  2. PowerBuilder
  3. # 3

Eduardo -

When you manually run the code with the setup described above:  the EXE and >>> ALL <<< DLLs in ONE folder, does it work?
If so, then you have a deployment issue.

If not, then you have a missing DLL.
In this case, put ALL of the DLLs from the development version of PB into that folder and test it again.
If it still fails, then you most likely have a problem in the code; trying to access an object that does not exist will cause this kind of failure, for example.

Comment
Eduardo G.
  1. Eduardo G.
  2. Monday, 20 June 2022 11:45 AM UTC
Thanks for your comment, but the funny thing is that with a Runtime 1288 it works and with Runtime 1509 it doesn't work.
  1. Helpful 1
There are no comments made yet.
Eduardo G.
Eduardo G. Accepted Answer Pending Moderation
  1. Friday, 17 June 2022 06:22 AM UTC
  2. PowerBuilder
  3. # 4

We are not including <application>.XML file of PB 2021.

We have a classic distribution, in one directory is .EXE, .PBD and all the runtime PB compilation executable.

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 17 June 2022 12:01 PM UTC
In that case, you'll need to look at the list of runtime files required as listed in the PB help and then compare those to the deployed App's folder vs your PB IDE's runtime folder ( file date, time & size ).
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 16 June 2022 17:54 PM UTC
  2. PowerBuilder
  3. # 5

Hi Edwardo;

  This sounds like it might be a case of mixed B runtime DLLs that are not the same as the PB App EXE was compiled for.

Are you deploying the <AppName>.XML file with your PB 2021 based App EXEs?

Regards ... Chris

Comment
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 16 June 2022 15:38 PM UTC
  2. PowerBuilder
  3. # 6

You sure you don't have mismatch of the deployed runtime DLLs and compiled version of your .EXE?  If not, please open a support ticket.

Comment
Eduardo G.
  1. Eduardo G.
  2. Friday, 17 June 2022 06:24 AM UTC
I am sorry to tell you that there is no mismatch. The creation of the installation is classic, executable, pbd and runtime in a single directory.
  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.