Bug 5864

Powerbuilder crashes with one or two specific error codes. 15 January, 2021

Jaimes Aviles
11 January, 2021
Product: PowerBuilder Category: PowerBuilder Runtime
Version: 2017 R3 Build: 1915
Classification: Publishing: Public
Priority: P3
Status: Verifying Reason:
Communication Status: Waiting for Appeon
Jaimes Aviles 15 January, 2021
#10
(In reply to Ken Guo @Appeon from comment #9)

Hi Jaimes,

I understand what you mean.
The main problem now is that we can’t reproduce this issue on our side so we
can’t locate the root cause of it.
Thus we want to know whether it is related to Citrix itself, or whether it
is Citrix that is causing the issue.

Regards,
Ken
Hi Ken,
What information other than what has already been provided do you need from us in order to determine that?

Regards,
Doron
Ken Guo @Appeon 15 January, 2021
#9
Hi Jaimes,

I understand what you mean.
The main problem now is that we can’t reproduce this issue on our side so we can’t locate the root cause of it.
Thus we want to know whether it is related to Citrix itself, or whether it is Citrix that is causing the issue.

Regards,
Ken
Jaimes Aviles 14 January, 2021
#8
(In reply to Ken Guo @Appeon from comment #7)

Hi Jaimes，

I suggest you:
1. Upgrade PB to PB 2019 R2 and see if the issue still exists because
Windows Server 2019 is supported started from PB 2019 R2.
2. Use Remote Desktop Connection (mstsc.exe) to remote access your Windows
Server 2019 instead of using Citrix and then double click chartbase.exe
directly to see if the issue still exists.
3. Copy the EXE and PBD to a new Windows 10 machine and then launch it to
see if the issue is gone.

Regards,
Ken
Hi Ken,
Thank you for your suggestions.  Not clear on how #2 and #3 would apply to us, but my main question to you has to do with a move to 2019 R2.   Before we plan this move, I need to know that the issues we reported will be resolved by a move to 2019.   Otherwise, a move to 2019 although it is in our future, it is not as high on our priority list as other projects.   So, your answer seems a bit like a brush off and I need some more substance to base a decision on.

Regards,
Doron
Ken Guo @Appeon 14 January, 2021
#7
Hi Jaimes，

I suggest you:
1. Upgrade PB to PB 2019 R2 and see if the issue still exists because Windows Server 2019 is supported started from PB 2019 R2.
2. Use Remote Desktop Connection (mstsc.exe) to remote access your Windows Server 2019 instead of using Citrix and then double click chartbase.exe directly to see if the issue still exists.
3. Copy the EXE and PBD to a new Windows 10 machine and then launch it to see if the issue is gone.

Regards,
Ken
Chris Pollach @Appeon 13 January, 2021
#6
Hi Jaimes / Doron;

   Thank you for the GDI feedback, That is very weird having no GDI resources. All PB Apps should consume a minimum of 200-300 plus in my testing.

   Let's see what the main support team has to say. 

Regards ... Chris
Jaimes Aviles 13 January, 2021
#5
image.png (76KB)

(In reply to Chris Pollach @Appeon from comment #4)

Hi Jaimes / Doron;

   Thank you for that extra information that I requested.

   The mini-dump indicates that the DLL that was penalized during the error
situation was the "DataWindow Expression Evaluator" (PBDWE). This module
handles all computed columns, column expressions, etc. However, I am not
sure yet what is aggravating the issue.

   I will now transfer this ticket over to the main Support Team for their
review & feedback. Especially, their more vast experience with Citrix.

   One thing I would like to suggest is check the memory and GDI resources
allocated to each of the PB App's Citrix session. GDI resources are set via
the MS-Windows registry, as follows:

FYI: https://docs.microsoft.com/en-us/windows/win32/sysinfo/gdi-objects

Regards ... Chris

Hi Chris,
The default for GDI resources is set to 10,000.   While running the application I tested an area which builds a huge nup datawindow and watched the GDI resources for that process and they remained at 0.    Same with the other user sessions for this application on this particular server.  (see attachment)

Regards,
Doron
Chris Pollach @Appeon 13 January, 2021
#4
Hi Jaimes / Doron;

   Thank you for that extra information that I requested.

   The mini-dump indicates that the DLL that was penalized during the error situation was the "DataWindow Expression Evaluator" (PBDWE). This module handles all computed columns, column expressions, etc. However, I am not sure yet what is aggravating the issue.

   I will now transfer this ticket over to the main Support Team for their review & feedback. Especially, their more vast experience with Citrix.

   One thing I would like to suggest is check the memory and GDI resources allocated to each of the PB App's Citrix session. GDI resources are set via the MS-Windows registry, as follows:

FYI: https://docs.microsoft.com/en-us/windows/win32/sysinfo/gdi-objects

Regards ... Chris
Jaimes Aviles 12 January, 2021
#3
Hi Chris,

1) What bitness is your PB App compiled to? 
32
2) Is your PB App's EXE P-Code or M-Code? -
EXE/PBD P-Code
3) Do you get an MS-Windows "Mini-Dump" when this occurs?
Do you mean:
First Error:
Faulting application name: chartbase.exe, version: 1.0.0.1, time stamp: 0x5df05d07
Faulting module name: pbdwe170.dll, version: 17.2.0.1915, time stamp: 0x5df05f11
Exception code: 0xc0000005
Fault offset: 0x00248f9c
Faulting process id: 0xa01c
Faulting application start time: 0x01d6d30b0d844d44
Faulting application path: C:\Program Files (x86)\ChartBase\chartbase.exe
Faulting module path: C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbdwe170.dll
Report Id: b3228d7d-350f-4064-980f-aae5887b2ade
Faulting package full name: 
Faulting package-relative application ID: 

Followed by 2nd error:
Faulting application name: chartbase.exe, version: 1.0.0.1, time stamp: 0x5df05d07
Faulting module name: pbdwe170.dll, version: 17.2.0.1915, time stamp: 0x5df05f11
Exception code: 0xc000041d
Fault offset: 0x00248f9c
Faulting process id: 0xa01c
Faulting application start time: 0x01d6d30b0d844d44
Faulting application path: C:\Program Files (x86)\ChartBase\chartbase.exe
Faulting module path: C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbdwe170.dll
Report Id: 282e770f-cc22-4998-81e0-ffdada53dc82
Faulting package full name: 
Faulting package-relative application ID: 

4) Did this issue just start happening?
We have only recently moved over our Citrix environment to 2019 and started moving users to this environment.   As far as I am aware, this was happening since we moved our users over, but we started looking at these about a month ago to triage them by looking at user sessions/Foxhound reports and Citrix application error logs. 

5) Do you get this error in the IDE, in an EXE or both?
Only looking at ones generated in en EXE.  Have not tried to reproduce them in the IDE.

6) Is this error random or somewhat consistent?
Somewhat consistent.    We have between 30-40 disconnections a day and some of them produce these error codes. 
 
7) Does the crash seem to happen at the same App processing location?
Not sure I understand the question.   we have a 2019 server farm with 4 servers.   Currently about 20 users per server.   As far as I know users are spread out between our clinics.   The hardware is all in one location with redundancy and backup to another location. 

Please let me know if you need any additional information.   Also, if you can please copy me on the replies, I will get them directly.

Regerds,
Doron Eskinazi
doroneskinazi@healthpointe.net
Chris Pollach @Appeon 11 January, 2021
#2
Hi Jaimes;

  Can you tell us ...

1) What bitness is your PB App compiled to?
2) Is your PB App's EXE P-Code or M-Code?
3) Do you get an MS-Windows "Mini-Dump" when this occurs?
4) Did this issue just start happening?
5) Do you get this error in the IDE, in an EXE or both?
6) Is this error random or somewhat consistent?
7) Does the crash seem to happen at the same App processing location?


FYI: Error #5 is:  "Negative value encountered in function."

Regards ... Chris
Jaimes Aviles 11 January, 2021
#1
Appeon - Ticket 2021-01-08.docx (180KB)

*Phenomenon:
Application blows up with one or two error codes.    0005 and 041b

*Reproduce Steps:
No specific sequence identified


Remarks:
OS:
Other
Platform:
32-bit
Database Type:
SAP SQL Anywhere
Database Version:
16