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

Resolved Max screen resolution for PB12 apps in Win 10?

  1. Advice
0
Votes
Undo
  1. Scott Gorke
    Scott Gorke
  2. PowerBuilder
  3. Thursday, 18 July 2019 17:54 PM UTC

Hi guys,

We have a legacy app in PB12.1 build 6639. One of our clients downloaded the latest version of the app to their test environment, and found that the app crashed randomly when running from a Citrix install on a Windows 10 machine. However, their testing found that the crashes don't happen when screen resolutions are below 1920x1024.

Is there a max screen resolution recommended for PB12 apps that nobody should exceed? What else should we check (since the client asked if something else is causing this)?

Thanks,

Scott Gorke

Query in Sybase ASE 15.7 for Powerbuilder 2017
C#: ODP - ConflictOption is not supported
Responses (4)
Ken Guo @Appeon
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 23 July 2019 08:03 AM UTC
  2. PowerBuilder
  3. # 1

Hi Scott,

When we test with the PB 12.1 and PB 2017 R3 locally, even if the resolution of the monitor is 1980*1080, we still can’t reproduce the crash issue. Here are some suggestions:
1. We suggest that you try to find out if it is related to the configuration of Citrix.
2. Or do not use Citrix, but run the application directly on the machine to see if there is a problem, which will rule out whether this problem is caused by Citrix.
3. Please verify on multiple machines to see if you can reproduce the issue and whether it is related to the resolution.
4. It is not recommended to run PB 12.1 on Windows 10, because PB 12.1 does not officially support Windows 10.
5. It is recommended to use PB 2017 R3 or PB 2019 GA as they officially support Windows 10.
6. If you create a small test case, can you reproduce the problem?
7. If you can reproduce the issue with PB 2017 R3 running locally, we suggest that you open a ticket in Appeon ticket system (https://www.appeon.com/standardsupport/) and upload your test case.

Regards,
Ken

Comment
Load more comments
Scott Gorke
  1. Scott Gorke
  2. Thursday, 1 August 2019 20:54 PM UTC
Hi guys,



The client finally sent us the Windows Event Log from the PC that crashed our app. The topmost part is below.

Furthermore, the client told us today that the crashes only happen when accessing our app via Citrix on Win 10; they do not crash on our app installed directly onto Win10, and they do not crash running the app in the Citrix server itself. Curiouser and curiouser....



Log Name: Application

Source: Application Error

Date: 01/08/2019 10:09:21 AM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: bchspctxsh27.oslerhc.org

Description:

Faulting application name: medsurg.exe, version: 1.0.0.1, time stamp: 0x4cec7a53

Faulting module name: OLEACC.dll, version: 7.2.9600.17415, time stamp: 0x54503b9b

Exception code: 0xc0000005

Fault offset: 0x00002b7d

Faulting process id: 0x2150

Faulting application start time: 0x01d54872a0fadc25

Faulting application path: C:\Program Files (x86)\Picis\Live\bin\medsurg.exe

Faulting module path: C:\Windows\SYSTEM32\OLEACC.dll

Report Id: f4ec564c-b465-11e9-8100-00505694b5e0

  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 1 August 2019 21:51 PM UTC
Hi Scott;

Looks like the app crash is happening within a MS-Windows DLL - "Oleacc.dll". This is MS's "accessibility" DLL helper for the O/S.

FYI: https://docs.microsoft.com/en-us/windows/win32/api/oleacc

HTH

Regards ... Chris
  1. Helpful
Scott Gorke
  1. Scott Gorke
  2. Friday, 23 August 2019 16:00 PM UTC
Hi Guys,



The client resolved their own issue - they were using something called "Workspace", but on a call with Citrix they were encouraged to switch to Citrix Receiver. Once done, no more crashing.



Thanks for your help and suggestions regarding this topic.

Scott
  1. Helpful
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Monday, 22 July 2019 14:37 PM UTC
  2. PowerBuilder
  3. # 2

In PowerBuilder the window size is measured in PBU which is an integer value. Integer values have a max of 32767.

Comment
Michael Kramer
  1. Michael Kramer
  2. Wednesday, 24 July 2019 09:12 AM UTC
32K equals approx. 6K - 8K pixels in width or height. Which means we probably will see PB issues on 8K screens.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 24 July 2019 20:39 PM UTC
There is no crash issue being caused by PBU and its integer value. Scott has confirmed that this is not a problem on the same high resolution when running on either Windows 10 or 7... only Citrix has this problem.



Also, Appeon engineers tested the PB Unit functions UnitsToPixels() and PixelsToUnits(), and neither function crashes even when the value is greater than 32,765. When the height and width of PB Object is set greater than 32,765 PBU, then PB will automatically change its value to a negative number.
  1. Helpful
There are no comments made yet.
David Peace (Powersoft)
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Monday, 22 July 2019 11:13 AM UTC
  2. PowerBuilder
  3. # 3

Hi Scott

That does sound more like a graphics driver issue rather than PB itsself. When it crashes what gets written into the event log and what module is failing?

Cheers

David

Comment
Scott Gorke
  1. Scott Gorke
  2. Monday, 22 July 2019 19:45 PM UTC
David, thanks for the advice. I'll have our support rep ask what gets written to the event log.
  1. Helpful
There are no comments made yet.
Michael Kramer
Michael Kramer Accepted Answer Pending Moderation
  1. Thursday, 18 July 2019 20:29 PM UTC
  2. PowerBuilder
  3. # 4

Hi Scott,

I don't recall issues with screen resolution though it is several years ago I worked with PB 12.1.

My honest guess is that your issue is affected by some incompatibility for your combo of PB 12.1 and Win10. And I'm certain there is more than just one issue since PB 12.1 is so much older than Win10.

No PB 12.x ever supported Win10. You will need PB 2017 or later to have support running on Win10.

Sorry! /Michael

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.