1. Lucia Radita
  2. PowerBuilder
  3. Tuesday, 8 October 2019 15:40 PM

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

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 18 December 2019 19:03 PM
  2. PowerBuilder
  3. # 1
0
Votes
Undo

Hi Lucia;

    Just an FYI that PB 2017 R3 MR02 was released today (build 1915). If you can, you might want to try this latest LTS build of PB 2017 and see if that helps your situation.

FYI: https://www.appeon.com/company/news/powerbuilder-2017-r3-and-infomaker-2017-r3-mr-1915-released.html

Regards ... Chris

Comment
There are no comments made yet.
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 17 December 2019 07:44 AM
  2. PowerBuilder
  3. # 2
0
Votes
Undo

Hi Lucia,

 

Due to that we can’t reproduce this issue locally, it is hard for us to find out the root cause of it for now.

Can you provide a small reproducible case for us? If yes, please go to Appeon Support Ticket system(https://www.appeon.com/standardsupport/newbug) to open a new ticket with this small case thus it can be properly received and tracked.

 

Regards,

Ken

 

Comment
Hi Ken,

We will try to build a small app to see if we encounter the same problem. I think the "context" of the application (ours is not a small one) has an impact in regard to this problem. Generally, since we migrated the application to PB 2017R3 / OS Windows Server 2016, we observed that the UI refresh is longer and we had to add SetRedraw(false) in several modules to improve display time.



Regards,

Lucia
  1. Lucia Radita
  2. Wednesday, 18 December 2019 14:51 PM
Hi Lucia,



I am very grateful that you are trying to build a small application for us. This will really help us a lot in analyzing and handling this issue!

Once you build this small app, please go to Appeon Support ticket system (https://www.appeon.com/standardsupport/newbug) to submit a bug and upload this small app.

Thanks in advance.



Regards,

Ken

  1. Ken Guo @Appeon
  2. Thursday, 19 December 2019 02:31 AM
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 16 December 2019 00:59 AM
  2. PowerBuilder
  3. # 3
0
Votes
Undo

Why would SetRedraw(false) be bad practice? We use it everywhere all the time. You just have to be careful to set it back to true before any popups like messageboxes and / or other windows opening.

 Is your executable "machine code" or interpreted (PBD?). Try PBD if not. Is the datastore present in a PBR file if not PBD used?

This might sound funny but "one thing you could try" is to make sure the exported datastore starts with "release 17;". Migration does not change the version. Best thing to do would be to edit the dw (not the source) and then just move anything a pixel to the right and then back to the left (or something similar), just to be able to "save" the datastore. This way you ensure all new attributes are present in the new format. (might not help but surely won't harm).

Also make sure there's a default printer on the PC assigned in windows.

Another thing: Does your module A maybe have another datastore with a long similar name? We have had sometimes problems of powerbuilder "confusing" one with another if that was the case. Make sure there's some difference somewhere in the let's say first 18 characters in the naming if this is applies to your module A. (I don't remember the exact amount of characters when that possible problem might occur).

Nothing else I can come up with at this moment.

Good luck.

 

Comment
There are no comments made yet.
Mohammud Daulgha Accepted Answer Pending Moderation
  1. Sunday, 15 December 2019 23:51 PM
  2. PowerBuilder
  3. # 4
0
Votes
Undo

We are experiencing the same issue in one of the production environment. As the issue does not happen in any of our development machines. Can someone share an ideas or steps to find the root cause of the issue will help to resolve the issue.

Comment
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 10 October 2019 21:46 PM
  2. PowerBuilder
  3. # 5
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.
Lucia Radita Accepted Answer Pending Moderation
  1. Thursday, 10 October 2019 20:43 PM
  2. PowerBuilder
  3. # 6
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.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 8 October 2019 15:47 PM
  2. PowerBuilder
  3. # 7
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.
  • Page :
  • 1


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