1. Balaji Renganayalu
  2. PowerBuilder
  3. Wednesday, 29 June 2022 18:12 PM UTC

We are upgrading pb from 2017 R2 1769 to 2019 R3 2728. We were able to migrate, compile and build the executable. Replaced the 2017 dlls with 2019 dlls. Upon login to the executable, when opening any window the cursor spins for a while and crashes with message "App has stopped working".

FYI: It works in one of the developers machine but the same set of binaries not working with rest of the team, not sure whats the difference.

Attachments (1)
Balaji Renganayalu Accepted Answer Pending Moderation
  1. Thursday, 7 July 2022 18:53 PM UTC
  2. PowerBuilder
  3. # 1

Issue resolved after adding the below line to the pb.ini. this ini should be kept in the same folder as app binary. thanks everyone for the suggestions


[Data Window]
  1. Miguel Leeuwe
  2. Thursday, 7 July 2022 20:23 PM UTC
Thanks for sharing the solution! Please mark as resolved.
  1. Helpful
  1. Sivaprakash BKR
  2. Friday, 8 July 2022 06:30 AM UTC
Strange. So far the Accessibility settings were used to speed up the processing... Hopefully, this is the first time, we (I) hear that it solves application crash issue too.
  1. Helpful
There are no comments made yet.
Sivaprakash BKR Accepted Answer Pending Moderation
  1. Wednesday, 6 July 2022 07:31 AM UTC
  2. PowerBuilder
  3. # 2

We had a similar issue while migrating legacy PB 6.5 application to PB 2017.   By tracing every line of execution we closed down to a function call to get the currentdirectory.  We replaced that function with GetCurrentDirectory() function call, which solved the issue.  

May be something similar, that need a modification?   

Happiness Always
BKR Sivaprakash


There are no comments made yet.
Balaji Renganayalu Accepted Answer Pending Moderation
  1. Thursday, 30 June 2022 09:06 AM UTC
  2. PowerBuilder
  3. # 3

Hi Miguel,


Below is what i got from event viewer logs


Faulting application name: cpms.exe, version:, time stamp: 0x6100e416
Faulting module name: PBVM.dll, version:, time stamp: 0x6100e676
Exception code: 0xc0000005
Fault offset: 0x000c0c0d


+ System
- Provider
      [ Name] Application Error
- EventID 1000
      [ Qualifiers] 0
  Level 2
  Task 100
  Keywords 0x80000000000000
- EventData
      C:\<binary path>\Deploy\cpms.exe
      C:\<binary path>\Deploy\PBVM.dll
  1. Balaji Renganayalu
  2. Tuesday, 5 July 2022 11:33 AM UTC
its not happening from IDE, only with the app executable.
  1. Helpful
  1. Andreas Mykonios
  2. Tuesday, 5 July 2022 11:53 AM UTC
Can you ran it using /pbdebug to generate a dbg file for investigation (your exe -> cpms.exe /pbdebug)?

  1. Helpful
  1. Chris Pollach @Appeon
  2. Tuesday, 5 July 2022 17:49 PM UTC
FWIW: My guess is that the PB runtime DLLs are one thing but there are also Microsoft runtime DLLs that are required as well. All of these are all well documented in the PB Help under the "runtime" keyword search. The MS DLLs could be present on the deployment machine(s) but of an older outdated version that then also need to be replaced. HTH
  1. Helpful
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Thursday, 30 June 2022 06:14 AM UTC
  2. PowerBuilder
  3. # 4


Have you checked the windows event viewer's logs?


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.