• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Stability Issues with the NativePDF / PDFlib Functionality

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

Resolved Stability Issues with the NativePDF / PDFlib Functionality

  1. Issue
0
Votes
Undo
  1. Mark Del Villan
    Mark Del Villan
  2. PowerBuilder
  3. Monday, 10 January 2022 20:48 PM UTC

Hi,

I'm just wondering if anyone else using PB 2017 R3 Build 1858 has encountered stability issues with the NativePDF / PDFlib functionality when generating documents for complex languages such as Arabic, Hebrew, or Thai.  

I'm finding that PBPDF170.DLL blows up (per the Window Event Log entry, below) about 30% of the time when generating a document in any of these languages.  The strange thing is that it isn't consistent, sometimes it blows up, sometimes it works fine.

Anyway, please do not hesitate to let me know if anything is not clear, and thanks for your time!

Mark

 

Faulting application name: test.exe, version: 1.0.0.1, time stamp: 0x5b6318c2
Faulting module name: PBPDF170.dll, version: 17.2.0.1858, time stamp: 0x5b6319d9
Exception code: 0xc0000005
Fault offset: 0x00145580
Faulting process id: 0x1324
Faulting application start time: 0x01d8065f8c73ed9d
Faulting application path: C:\dev\test.exe
Faulting module path: C:\dev\appeon170\PBPDF170.dll
Report Id: 9ea51e97-64e8-4502-803b-04ea36053d95
Faulting package full name:
Faulting package-relative application ID:

What is PBORCA license model?
Manejo de Carpetas con GIT
Accepted Answer
Mark Del Villan
Mark Del Villan Accepted Answer Pending Moderation
  1. Tuesday, 31 May 2022 19:23 PM UTC
  2. PowerBuilder
  3. # Permalink

Just following up to mention that this is documented as Bug 7846, and close out the question.

Thanks for all the help!

Comment
There are no comments made yet.
Responses (5)
Mark Del Villan
Mark Del Villan Accepted Answer Pending Moderation
  1. Thursday, 27 January 2022 18:27 PM UTC
  2. PowerBuilder
  3. # 1

Appeon support is looking into this now, but I just wanted to share the following snippet to see if anyone else can come up with some ideas for me to try.  

Chris suggested adding the Yield() at the end of the loop, but it doesn't seem to help.

 

for li_i = 1 to li_copies
    dw_report_test_ext.Retrieve()
    dw_report_test_ext.Modify ("DataWindow.Export.PDF.Method = NativePDF!")
    dw_report_test_ext.Modify ("DataWindow.Export.PDF.NativePDF.UsePrintSpec = 'Yes'")
    dw_report_test_ext.Modify ("DataWindow.Export.PDF.NativePDF.PDFStandard = '1'")
    li_return_save = dw_report_test_ext.SaveAs (sle_path.text + 'hebrew_test' + string(li_i) + '.pdf', PDF!, FALSE)
    Yield ( )
next

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 27 January 2022 19:13 PM UTC
Just to add to Mark's comment ... My test of his Test Case code crashed on 7-8 loops. After adding the Yield() command to his test case, I ran a test of 100 loops (PDF's created) without any issues.
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Friday, 28 January 2022 03:12 AM UTC
#7846 must be private, so I cannot try myself.

What about doing this right before the retrieve():

ls_dobject = dw_report_test_ext.dataobject

dw_report_test_ext.reset()

dw_report_test_ext.dataobject = ls_dobject

dw_report_test_ext.settransobject(sqlca) // not too sure if needed



If that doesn't help, what about doing the retrieve() AFTER the first 3 modify(() statements.

Just ideas,

MiguelL
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Friday, 28 January 2022 03:14 AM UTC
Beside my previous suggestion. Is it really necessary to do those 3 modifies WITHIN the loop?

If you DON't do my suggested reset of the dataobject, then you could do the 3 modifies BEFORE the for loop.

Correct me if I'm wrong.

regards.
  1. Helpful
There are no comments made yet.
Mark Del Villan
Mark Del Villan Accepted Answer Pending Moderation
  1. Tuesday, 11 January 2022 14:39 PM UTC
  2. PowerBuilder
  3. # 2

Thanks for all the QUICK responses!  I'll check out later builds and, if necessary, submit a support ticket + test case. 

Any idea when a LTS release of PB 2021 will be available?

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 11 January 2022 18:57 PM UTC
There will be no LTS version of 2021. You should use latest build of 2019 R3.
  1. Helpful 1
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 10 January 2022 21:41 PM UTC
  2. PowerBuilder
  3. # 3

Hi Mark;

   There were many, many improvements to the NativePDF feature from PB 2017R3 => 2019 => 2019R3 into 2021. Have you have a chance to try a newer PB version on this issue?

FWIW: There were Native PDF fixes as well (even for language support) in the PB 2017R3 MR build 1915.

FYI: https://docs.appeon.com/pb2017r3/release_bulletin_for_pb/Build-1915-MR-BugFixes.html

Regards ... Chris

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Tuesday, 11 January 2022 03:50 AM UTC
Hi Chris,

FYI: 1858 is the version he's using already.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 11 January 2022 04:21 AM UTC
Thanks ... I meant build 1915
  1. Helpful 1
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Monday, 10 January 2022 21:09 PM UTC
  2. PowerBuilder
  3. # 4

Please open a support ticket with test case so we can pinpoint the bug.  Also, might be worthwhile to try out PB 2021 to see if newer version of PDFLib has already resolved this issue.

Comment
Mark Del Villan
  1. Mark Del Villan
  2. Tuesday, 25 January 2022 20:39 PM UTC
Sorry for the delay but I have finally submitted the test case! (Bug 7846)



Is there any way I can change the Priority from a P3 to a P1? I tried editing the issue but it won't let me change that field.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 25 January 2022 21:37 PM UTC
I don't think you should change the priority for a couple of reasons. First, we take P3 issues seriously. P3 issues that drag on is because we can't reproduce the problem (or at least not consistently). Your issue might be such scenario, in which case even if it is classified as P1 it won't speed up fix. Secondly, P1 has very strict definition. https://www.appeon.com/appeon-standard-support-plan.html If customer classifies priority incorrectly, we will reprioritize it back down. In case this problem is more than just annoyance for you and you don't want to wait for a fix, you might want to consider to use GhostScript or other method to generate PDF.
  1. Helpful 1
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.