Questions? Feedback?powered byOlark live chat software
Bug 3267

Invalid Reference in PBDWE170.DLL (17.2.0.1858) 10 September, 2019

Tyler Cruse
29 August, 2019
Product: PowerBuilder Category: DataWindow
Version: 2017 R3 Publishing: Public
Status: Analyzing Priority: P3
Classification: Resolution:
Chris Pollach 10 September, 2019
Hi Tyler;

  Thank you for confirmation!

  I cannot say what your issue is without a simple test case that replicates this crash. However as you already stated, this only happens maybe once a week. So it would be (I would imagine) extremely had for you and Appeon to replicate.

  I see that you are using the "srvany" product for running your PB App as an O/S Service. I wonder if this could be your issue?

Regards ... Chris
Tyler Cruse 10 September, 2019
No timer events involved.  The processes are entered into DW with next time to process column and the DW is polled row by row in a loop
Chris Pollach 30 August, 2019
Hi Tyler;
  
   Does your PB App use Timers (ie: Timing object to Window timer) and/or the IDLE timer? If so, what is happening when these events fire?

Regards ... Chris
Chris Pollach 30 August, 2019
Email from customer (Tyler) ...

-------------------------------------------------------------

Thanks I will check the items that you reference.
However, at this point none of these conditions come to mind.
Since each of these operations happen often, usually with only 100-200 ms wait between the polls, the expression/computed column condition seems unlikely.
Also, the “crash” seems  happen during idle activity times, e.g. nothing to dispense, nothing to print,  nothing to import, nothing to export, no backup required ….  It appears that the DW controls would be returning 0 rows during this time.
  
There are DBERROR and ERROR events in every case, and have in other cases been shown to work correctly.

Nice to see that you are still active in the PB world, been a lot of years since the 12.5.x time frame.
Chris Pollach 29 August, 2019
Hi Tyler;

  The "pbdwe170" module is the Data Window Expression evaluator. Typically when we see this type of random error, the cause is either:

a) Missing DW object
   Could be caused by a Destroy or DC/DS.Dataobject = "" command
b) Dynamic change to the DWO's properties. Especially an "expression", in a Modify() command.
c) Bad data causing a computed column or expression error.

In the above cases, the DW Control or DataStore "container" should catch the above errors if the App has the ERRROR and DBERROR events coded around the DC/DS controls.

Regards ... Chris
Tyler Cruse 29 August, 2019
*Phenomenon:
Application has no UI running as windows service (srvany).  Failure happens about once a week.
Application is basically in a "poll loop" checking for work to perform based on DB contents.  Failure does not occur at any regular time or usage level,

*Reproduce Steps:
Can supply code and sample database on request.  

Remarks:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: appservice.exe
P2: 3.5.0.10
P3: 5c4c50b1
P4: pbdwe170.dll
P5: 17.2.0.1858
P6: 5b55f84d
P7: c0000005
P8: 00000000002a9fe7
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_appservice.exe_2dcacdd77494fefe1afb83268041aa49d1251a2c_729ba3ec_0619fdab

Analysis symbol: 
Rechecking for solution: 0
Report Id: 8f5ce43b-c4f8-4c0f-a772-6c5a63892781
Report Status: 4


Faulting application name: appservice.exe, version: 3.5.0.10, time stamp: 0x5c4c50b1
Faulting module name: pbdwe170.dll, version: 17.2.0.1858, time stamp: 0x5b55f84d
Exception code: 0xc0000005
Fault offset: 0x00000000002a9fe7
Faulting process id: 0xb94
Faulting application start time: 0x01d5585be0cb293f
Faulting application path: C:\Program Files (x86)\Talyst\AutoPharmServer\appservice.exe
Faulting module path: C:\Program Files (x86)\Appeon\Shared\PowerBuilder\x64\pbdwe170.dll
Report Id: 8f5ce43b-c4f8-4c0f-a772-6c5a63892781
Faulting package full name: 
Faulting package-relative application ID: 



Application: appservice.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 000000006D2F9FE7
Stack:


Fault bucket 2176118087599235456, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: appservice.exe
P2: 3.5.0.10
P3: 5c4c50b1
P4: pbdwe170.dll
P5: 17.2.0.1858
P6: 5b55f84d
P7: c0000005
P8: 00000000002a9fe7
P9: 
P10:
OS:
Windows Server 2016 
Platform:
64-bit 
Database Type:
Microsoft SQL Server 
Database Version:
2016