1. Josh Bahr
  2. PowerBuilder
  3. Tuesday, 24 October 2023 13:49 PM UTC


We have a PowerBuilder program (2019 R3 Build that is having some random, unexplained issues in a VMWare Horizon hosted environment. The issue is that the end user can go about their normal workflows, and at random, their session locks up and they need to force log themselves out of Horizon and back in. The curious part is, when they log back in, they are able to continue on with their same session. So our program isn't crashing or locking up itself. This is happening across many, separate VMWare Horizon environments.

We have worked on this issue for some time with no success so far in finding root cause. Our logging indicates our software is not locking up itself, as our logs continue on as if nothing happened. 

One theory we have is that this could be related to printer calls Powerbuilder makes as you load DataWindows, which may be subsequently causing a lockup issue with Horizon. 

I was curious about some PB.INI settings we found related to Citrix, and if they could apply to our situation. 

This is the first one we are looking into trying. Does anyone have more information on exactly what this setting is doing? And whether or not it could help in another VM environment that is not Citrix?



Whether the programs compiled by PowerBuilder obtain the "default" printer(s) of Windows in real time instead of getting a copy of the "default" printer(s) when the application starts as before.

1 = For handling "default" printer(s) in Citrix environment

0 = For not handling "default" printer(s) in Citrix environment

Note: This key is supported starting from version 2019 R3 and works on Windows 10 and later.

This setting also caught our eye, and I have the same questions for it: 

[Data Window]


0 = Disable both MSAA and Microsoft UI Automation (and can resolve several reported bugs of later PowerBuilder versions that run slowly, particularly on Citrix and similar).

1 = Enable both

2 = Enable Microsoft UI Automation only

3 = Enable MSAA only

This page has more information.

If anyone has experienced a similar issue like this I am also open to any general advice or steps that could be tried further. 

Happy to provide additional info as needed.

Thank you!


Andreas Mykonios Accepted Answer Pending Moderation
  1. Tuesday, 24 October 2023 14:01 PM UTC
  2. PowerBuilder
  3. # 1



For the first one, take a look at the following conversation: Citrix=1 (appeon.com).

For the second, when Accessibility is set 0 then no accessibility functionality will be available in the datawindow. Datawindow is a very complex object, and enabling that feature may have big impact in performance of your application. So it is suggested to have this setting turned off when possible (you have no users with disabilities using your application).

By the way, I haven't done any test using VMware Horizon.


  1. John Fauss
  2. Tuesday, 24 October 2023 14:13 PM UTC
That depends on what version of PB you are using, as the default value for this setting was changed not too long ago to disable accessibility. It's always a good idea to mention in your questions the version/release/build of PB you are using.
  1. Helpful 1
  1. Andreas Mykonios
  2. Tuesday, 24 October 2023 14:28 PM UTC
John is right. Accessibility is disabled by default in PB 2022 R1 and R2.

  1. Helpful 1
  1. Josh Bahr
  2. Tuesday, 24 October 2023 15:58 PM UTC
Ah yeah I should have included. We are on 2019 R3 Build
  1. Helpful
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.