1. Bjarne Anker
  2. PowerBuilder
  3. Thursday, 14 December 2017 14:07 PM UTC

After migrating from PB12.5 to Appeon PB 2017 (1681), our application crashes with this message in the Windows Event Viewer - application:

Faulting application name: PB170.EXE, version: 17.0.0.1681, time stamp: 0x59c46b21
Faulting module name: PBSHR170.dll, version: 17.0.0.1681, time stamp: 0x59c46aeb
Exception code: 0xc0000005
Fault offset: 0x0011991b
Faulting process id: 0x2a34
Faulting application start time: 0x01d374b952c05ffb
Faulting application path: C:\Program Files (x86)\Appeon\PowerBuilder 17.0\PB170.EXE
Faulting module path: C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBSHR170.dll
Report Id: 2f23f5e6-3cce-4e3b-8c1b-e4e61c647ea6
Faulting package full name: 
Faulting package-relative application ID: 

 

The error occurs when closing this procedure:

DECLARE wf_OppdaterBunt PROCEDURE FOR mts.spr_OppdaterBunt  
@Klient = :ai_klientnr,   
@UserID = :as_userid,   
@BuntType = :as_bunttype,   
@PeriodeDato = :ad_pdato,
@BuntNr = :al_buntnr;
execute wf_OppdaterBunt;
 
 
FETCH wf_OppdaterBunt INTO :il_feilno,:il_linjeno;

Here the application crashes:

close wf_OppdaterBunt;

This works just fine in PB12.5, so this is obviously something in Appeon PowerBuilder.

Can you read something from the event message, shown on top of this post?

 

Regards,

 

Bjarne Anker

Maritech Systems AS

Norway

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 14 December 2017 14:51 PM UTC
  2. PowerBuilder
  3. # 1

Hi Bjarne;

   From the look of it - the application is crashing while being run from the IDE and not its own EXE.

Have you tried optimizing all your App's PBL's, performed a Full Build on the App, and then restarted PB IDE before testing?

Regards .. Chris

Comment
There are no comments made yet.
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Thursday, 14 December 2017 15:52 PM UTC
  2. PowerBuilder
  3. # 2

Hi

What database transport and parameters are you using?

Comment
There are no comments made yet.
Bjarne Anker Accepted Answer Pending Moderation
  1. Friday, 15 December 2017 10:55 AM UTC
  2. PowerBuilder
  3. # 3

Hi.

 

This happens from both the IDE and EXE-file.

However, the issue is resolved by adding ",PBNewSPInvocation='yes'" at the end of SQLCA.DBPARM before connecting.

 

Regards,

Bjarne

Comment
  1. Lars Mosegaard
  2. Tuesday, 19 December 2017 22:57 PM UTC
Wish we'd know a couple of years ago when 12.6 first came out.  We couldn't move forward to 12.6 with too many closes.

  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 15 December 2017 14:58 PM UTC
  2. PowerBuilder
  3. # 4

Thanks Bjarne for posting that very helpful answer!

I cannot tell you how many times that I have encountered a flakey DB Client driver has taken down many a good PB App.

Comment
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.