1. Dave O'BILOG
  2. PowerBuilder
  3. Monday, 28 February 2022 14:28 PM UTC

 

 

Hi,

we are in Powerbuider 2019 R3 Build 2703, Windows 10

in some particular cases, we have a system error.

I just made retrieve on datawindow and crash : ( i have tried in Powerbuilder 2021 too, same error )

 

Détecteur d'erreurs 1178631464176105859, type 1
Nom d’événement : APPCRASH
Réponse : Non disponible
ID de CAB : 0

Signature du problème :
P1 : PB190.exe
P2 : 19.2.0.2703
P3 : 6065b6d0
P4 : PBSHR.dll
P5 : 19.2.0.2703
P6 : 6065b690
P7 : 4000001f
P8 : 001451e0
P9 :
P10 :

Fichiers joints :
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE3AB.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE708.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE738.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE736.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE765.tmp.txt

 



Ces fichiers sont peut-être disponibles ici :
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_PB190.exe_e989e2eb64237e7310ef27ec2359a468a55b6b5_22f9c247_67937192-042c-4d14-b586-984a5261a0d8

Symbole d’analyse :
Nouvelle recherche de la solution : 0
ID de rapport : bd06cbde-0ce1-46c4-b550-4a1ed1d6b7a4
Statut du rapport : 268435456
Récipient avec hachage : d1031f7bb153cc6f805b57126f50b983
GUID CAB :0

 

 

any ideas ?

 

 

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 28 February 2022 15:14 PM UTC
  2. PowerBuilder
  3. # 1

Hi Dave;

  The PBSHR module is the main DLL that the PB runtime uses to broker calls to the O/S for internal API's and also for ones that the App itself defines as "External Functions". I would first suggest that you have a look at where in the App's code the Crash is coming from and once isolated, see what PowerScript / External API (or even 3rd party DLL) calls are being made. Hopefully, something will "pop out" at you as t what might be causing the crash.

  Also note that dealing with OLE and/or OCX external components can also cause PBSHR crashes as well if not executed properly.  Once you have located the area of the App that causes the crash, you can also try wrapping the code with a TRY..CATCH in order to introspect the "Exception" object for more information as to what is going on runtime wise.

Regards ... Chris

  

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 6 October 2022 18:56 PM UTC
Hi Aleš;

Like Dave, this could be DB Client Driver related. Have you tried connecting to your DBMS via a different DB driver?

Regards ... Chris
  1. Helpful
  1. Aleš Vojáček
  2. Thursday, 6 October 2022 22:08 PM UTC
I did not.

We are connecting using ODBC to MSSQL. This is old app. So I'm little scared to change DB connection which is working.

But this scary behaviour is pain of PB 20 years.

No info why it is crushing and I haave no Idea why it is falling.

PB is not bad in clicking new windows with editing DW screens, but if there is problem there is not clear "why" it is broken :-(

We have discusions about moving to C#, but there is strong opinion, that havy DB app is + fo PB to do. I have opinion that every scary think which you try to solve hours and hours and you do not have any clue why it is happening and only solution is happy workaround.

I did havy development in PB 15 years ago. Then I change employer and start using C#. Thant was hard shift. But return to PB is even harder.

:-(
  1. Helpful
  1. Chris Pollach @Appeon
  2. Thursday, 6 October 2022 23:08 PM UTC
FWIW: I was only suggesting trying a different DB client access mechanism as a "test" to try & rule out your current ODBC connectivity being the stability issue. Food for thought. ;-)
  1. Helpful 1
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.