Have you tried disabling accessibility in your PB.INI

ACCESSIBILITY=0

Hi Sebastien;

  Did you install the "Microsoft Visual C++ 2010 x86 Redistributable" software on your Citrix environment?

Regards .... Chris

PS: "Microsoft Visual C++ 2010 x64 Redistributable" if you are deploying 64bit PB App EXEs.

Hi Sebastien,

1. I just need you to confirm again that you have modified the pb.ini file under the same directory where your exe resides.  

If not, please add a pb.ini file to the directory where the EXE resides and this file should contain the following content.

Then run it again and see if it works well. 

[Data Window]

ACCESSIBILITY=0

You can refer to the following link for details about how to set the ACCESSIBILITY feature:

https://www.appeon.com/developers/get-help/knowledgebase/powerbuilder-datawindow-hangs-temporarily-after-retrieve.html  

2. Since I can't reproduce your issue locally, I can only provide some troubleshooting steps for you.

One customer of ours had the application crashing issue in Citrix previously and they solved the issue by the solution in the links below. So I suggest you try it and see if the issue is gone.

https://support.citrix.com/article/CTX107825

https://support.citrix.com/article/CTX232495

3. Is your application a 64-bit application? If you deploy it as a 32-bit application, can you still reproduce it (I just want to confirm whether it is related to the platform)?

If the issue persists after doing the above, I suggest you report this problem to our ticket system: https://www.appeon.com/standardsupport/newbug so that it can be properly received and tracked. Please also provide a sample PB test case (with PBT / PBL) when you submit it to the ticket system. Thanks in advance.

Regards,

Have a look at https://community.appeon.com/index.php/qna/q-a/error-r6025-in-pb2019r2-beta

There might be a useful link there.

regards.

We are having the same issue in the debugger. Weirdly one person gets it every time in this one spot. I have had it happen in other parts of the app but never where this person gets it.

He has found that if he visits the Instance Variables pane, clicking one of the buttons that advance the code causes the error to happen.