Hi.
We have just upgraded from 2019 R2 to R3.
Most of our customers are running just as before, but for one we're having som severe issues with hang in our application.
The main difference is that they have 4K monitor and have set scailing of resolution to 125% or 150%.
Our application starts just fine, but after a short while it hangs for several minutes without responding.
After some time it responds, but very slowly.
I've done some capturing using MS Process Monitor, and our exe file is reporting pages up and down with "NAME NOT FOUND" or "PATH NOT FOUND" and the file "c:\windows\syswow64\UIAutomationcode.dll".
This file exists - triple checked it.
Also, all runtime files is updated - also pbacc.dll and pbaccessibility.dll is included.
When I log in using my Windows 10 laptop, all is good. But using 4K monitor with 125% is terrible when it comes to performance.
Is this a known issue since one of the new features i R3 is in fact support for "Microsoft Active Accessibility (MSAA) and Microsoft UI Automation" - section 508?
Do you have any similar cases in your system?
As of now, we have no other choice than to revert to R2.
br,
Bjarne Anker
Maritech Systems
Norway
[Data Window]
ACCESSIBILITY=0
It's just that they all have 4K monitors and scanling set to 125 or 150%.
So perhaps the answer is: yes, they need it.
I'll report this in a support ticket anyways so you can look into it.
Will also look into pb.ini to see if that helps.
Bjarne