1. Lucia Radita
  2. PowerBuilder
  3. Tuesday, 08 October 2019

We are using Power Builder 2017R3 build 1858 for our POS application. The application runs on Windows Server 2016. We have a constant crash in a specific feature.

.Net Framework  3.5 (version 3.5.30729.4926 ) and 4.7 ( version 4.7.02558; release 461310)

In this feature a datawindow is dynamically modified having also a split column

The crash occurs before displaying the data

In Event Viewer the log data is:

//******************

Faulting application name: posisent.exe, version: 1.0.0.1, time stamp: 0x5b6318c2 => this is the name of our app.
Faulting module name: pbdwe170.dll, version: 17.2.0.1858, time stamp: 0x5b6319c8
Exception code: 0xc0000005
Fault offset: 0x00158bc3
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
Faulting package full name: %14
Faulting package-relative application ID: %15

//****************** related .Net Runtime error

Application: posisent.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 722D8BC3

//*****************

Would you have any suggestions how to address this issue?

thank you

Armeen Mazda Accepted Answer Pending Moderation
0
Votes
Undo

Hi Lucia, for this issue I recommend opening a support ticket.  But without reproducible test case Appeon support can’t help.

Comment
There are no comments made yet.
  1. Thursday, 10 October 2019
  2. PowerBuilder
  3. # 1
Lucia Radita Accepted Answer Pending Moderation
0
Votes
Undo

The problem is not as simple as it looks. Running from Debug does not give any error. In the previous version of PB (10.2) there was no problem and the feature was not changed. We just migrated the code to PB 20017R3

The window is a response type and displays data in a datawindow (DB is SQL). The datastore is changed dynamically, the select and its properties. This response window is called from different modules and the datastore is slightly different, same for the SQL syntax. If just launching the application, call the window from module A => the exe stops working  (see pic)

The other scenario: launch the application and call the same window from module B(ex)=> data is displayed, no error. Then call the the window from module A => this time is not crashing anymore.We can call it n time and will not crash. But if exit the app and return to module A calling the Window => same crash

My guess is that first time the SQL is taking some time to build the plan and data retrieval is a bit longer; after same SQL plan is used and response is fast.

After migrating to new PB version we had to add some SetRedraw (false) to improve display time although some comments are stating that is not a good practice.

 

Comment
There are no comments made yet.
  1. Thursday, 10 October 2019
  2. PowerBuilder
  3. # 2
Chris Pollach Accepted Answer Pending Moderation
0
Votes
Undo

Hi Lucia;

  If this happens consistently, I would recommend using the PB IDE's "Debugger" on the PowerScript code that is modifying the DWO's properties & behaviour. By "stepping through" your related code you should be able to locate the problematic statement.

HTH

Regards ... Chris

Comment
There are no comments made yet.
  1. Tuesday, 8 October 2019
  2. PowerBuilder
  3. # 3
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.