1. Mark Del Villan
  2. PowerBuilder
  3. Friday, 24 May 2024 15:01 PM UTC

Hi,

I'm troubleshooting an issue where my PB2017-based app is crashing intermittently in a customer environment.  I'm not able to replicate the error in my dev environment.  In fact, I am not able to replicate the error in the customer's environment either, which leads me to consider that it may be user specific.  

Basically, under certain conditions, while retrieving a large series of nested datawindows, the app crashes and creates a series of dump files.  All dump files indicate: a null pointer dereference in the PBSNC170.DLL module, specifically within the PB_DB_Rout function.

The network and database seem to be working fine.  

Does anyone have any advice on how to further troubleshoot this?

Thanks for reading!

Mark

Accepted Answer
Mark Del Villan Accepted Answer Pending Moderation
  1. Tuesday, 10 September 2024 18:45 PM UTC
  2. PowerBuilder
  3. # Permalink

Just FYI, the issue I encountered ended up being due to a interaction when (a) the app is running through the Citrix Workspace Client (b) Display Scaling is enabled in Windows client and (c) PB is attempting to render a datawindow as a report. 

We are working around the issue by instructing our customers to disable display scaling when using the app.  We are also looking into various windows and citrix policy settings to see if we can make Windows + Citrix + PB play nice together regardless of how display scaling is configurated by the user.   

Comment
  1. Armeen Mazda @Appeon
  2. Tuesday, 10 September 2024 18:50 PM UTC
Thanks for sharing the solution!
  1. Helpful
There are no comments made yet.
Mark Malin Accepted Answer Pending Moderation
  1. Tuesday, 28 May 2024 08:41 AM UTC
  2. PowerBuilder
  3. # 1

Hi,

I am having similar issue. I have identified that error as System.AccessViolationException.

I am running with PB 22 R2 under Win11 OS.

Debug log

(466c.29dc): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000000 ebx=04a67c10 ecx=04cc56a8 edx=00000016 esi=18599c40 edi=04c53870
eip=747e16a3 esp=00fe8680 ebp=00fe8734 iopl=0         nv up ei pl nz na po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
pbODB!PB_DB_Rout+0x1a6e3:
747e16a3 8338ff          cmp     dword ptr [eax],0FFFFFFFFh ds:002b:00000000=????????

Looks like it tries to access 00000000 address

Comment
  1. Mark Malin
  2. Wednesday, 29 May 2024 06:15 AM UTC
Hi Chris,

Thank for the reply.

I updated my comment. I use PB 22 R2 on Win11
  1. Helpful
  1. Chris Pollach @Appeon
  2. Wednesday, 29 May 2024 14:28 PM UTC
Hi Mark;

Thanks for the updated information! I have personally not encountered a customer reported issue on this type of error. I suspect though that this is environment related (ie: type of DBMS, type of DB Client, Connection Settings used, Schema Design, etc). So it's hard to diagnose from the limited information that you supp;lied thus far.

I would like to suggest that you try & recreate a simple PB App test case and then open a Support Ticket for this anomaly - providing a test DB as well. That way if Appeon can recreate this problem, then Engineering that study why this is happening.

Regards .. Chris

PS: I would also encourage you to try PB 2022 R3 - latest build 3356 as well to see if this problem is still present.
  1. Helpful
  1. Mark Malin
  2. Thursday, 30 May 2024 06:09 AM UTC
Thank you Chris,



We are trying to identify which of the environment components might have caused it before we try and make a sample app.

Thank you for the suggestions, we will keep that in mind.
  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.