• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Application Crashes in some workflow when a third party application (MModal) is running

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

Resolved Application Crashes in some workflow when a third party application (MModal) is running

  1. Issue
0
Votes
Undo
  1. Shafeer Mohamedali
    Shafeer Mohamedali
  2. PowerBuilder
  3. Tuesday, 2 March 2021 09:29 AM UTC

Hi,

We are facing an issue in PowerBuilder application which is hosted in CITRIX environment. The application crashes in some workflows frequently. This happens when another third party application (MModal) is installed in the client machine. The below are the event log details for the application crash.

 

Faulting application name: order_management.exe, version: 1.0.0.1, time stamp: 0x5c4c46f1
Faulting module name: PBSHR170.dll, version: 17.2.0.1880, time stamp: 0x5c4c46f3
Exception code: 0x4000001f
Fault offset: 0x00122f50
Faulting process id: 0xaabc
Faulting application start time: 0x01d70e5d6625519e
Faulting application path: C:\Program Files (x86)\paragon1504\order_management.exe
Faulting module path: C:\Program Files (x86)\paragon1504\PBSHR170.dll
Report Id: ce17900f-7a51-11eb-80fa-000d3a8eae3e
Faulting package full name:
Faulting package-relative application ID:

 

I am using PB version 2017 R3 Build 1880.

Appreciate your help on resolving this issue.

 

Thanks

Shafeer

Program crash on DataWindow PrintPreview?
Error using DataStore into user function
Responses (3)
Shafeer Mohamedali
Shafeer Mohamedali Accepted Answer Pending Moderation
  1. Wednesday, 10 March 2021 14:57 PM UTC
  2. PowerBuilder
  3. # 1

Hi Ken,

 

Thanks for quick response. This fix seems to be working in my scenario. is this fine if we keep the below content in any of the existing INI file instead of creating PB.ini file ?

[Data Window]
ACCESSIBILITY=0

Thanks 

Shafeer

Comment
John Fauss
  1. John Fauss
  2. Wednesday, 10 March 2021 15:40 PM UTC
This ini file has to be named pb.ini in order for the PowerBuilder Virtual Machine (PBVM) to find/use it. Also, unless you have the PB IDE installed, the pb.ini file has to reside in the same folder as the application executable. This is how it works.
  1. Helpful
Ken Guo @Appeon
  1. Ken Guo @Appeon
  2. Thursday, 11 March 2021 06:35 AM UTC
Hi Shafeer，



I am glad that it resolves your issue.

Yes, you can add the key and key value to the existing pb.ini file. However, please note that you should add this key into the [Data Window] section.



Regards,

Ken
  1. Helpful
There are no comments made yet.
Ken Guo @Appeon
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 3 March 2021 11:01 AM UTC
  2. PowerBuilder
  3. # 2

Hi Shafeer，

I suggest you add a pb.ini file in the directory where the EXE resides, this pb.ini file contains the below content:
[Data Window]
ACCESSIBILITY=0

After adding the pb.ini file, run your EXE and see if the issue still exists.

 

Regards,

Ken

 

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 2 March 2021 16:36 PM UTC
  2. PowerBuilder
  3. # 3

Hi Shafeer;

  I am not sure if this might help but you might like to try moving to the next MR (maintenance release) of  PB 2017 R3 which is build 1915 and see if that helps. I would also suggest to try using the W10 "Compatibility Mode" test and see W10 suggests running the PB App in a different O/S mode. This might avert the MModal conflict. Food for thought. 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.