• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Application freezing in certain modules after migrating to PB 2019 Build 2170 from PB7

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

Resolved Application freezing in certain modules after migrating to PB 2019 Build 2170 from PB7

  1. Issue
0
Votes
Undo
  1. Ravindran Naarayanan
    Ravindran Naarayanan
  2. PowerBuilder
  3. Wednesday, 23 September 2020 10:57 AM UTC

The application freezes when opened the first time and after force closing, it works without any issues on the same module. 

From the Windows Log, got the below error message

Faulting module name: PBSHR190.dll, version: 19.0.0.2170, time stamp: 0x5e03ac9c
Exception code: 0x80000003
Fault offset: 0x00129250
Faulting process id: 0x27c4
Faulting application start time: 0x01d691965f78f61d
Faulting module path: D:\PBSHR190.dll
Report Id: b37d3dfa-fd89-11ea-83df-005056891a3a
Faulting package full name:
Faulting package-relative application ID:

Cannot find base-64 encode function
.Net Web Service Bug
Responses (1)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 23 September 2020 16:47 PM UTC
  2. PowerBuilder
  3. # 1

Hi Ravi;

  I see that your App is using the PB runtime build 2170. Please make sure that this is the same build as indicated in the PB IDE that you are using. A mismatch between these can lead to random App crashes.

Regards .. Chris

Comment
Ravindran Naarayanan
  1. Ravindran Naarayanan
  2. Thursday, 24 September 2020 06:40 AM UTC
Hi Chris,



Yes, it is the same build as the PBF IDE.



Regards,

Ravi
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 24 September 2020 14:38 PM UTC
Hi Ravi;

Thanks for confirming that the PB App and its deployed PB runtime come from the same build as the PB IDE!

If the deployment seems OK then try the MS-Windows "compatibility mode" test (RHMB on the App EXE) and see what Windows recommends. Depending on the O/S configuration, 3rd party software used (ie: like your AV), your App's ADK calls, etc - the execution process may need tweaking.

The other aspect is that the PB runtime is of the correct build *but* a DLL or two might be missing. Did you deploy the PB runtime via the PB Packager utility or manually copy the runtime DLL's across to the deployed PCs?

Regards ... Chris



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.