• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • OleCustomControl causing application crash after migrating to PB2019R3

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

Resolved OleCustomControl causing application crash after migrating to PB2019R3

  1. Issue
0
Votes
Undo
  1. Tobias Roth
    Tobias Roth
  2. PowerBuilder
  3. Thursday, 4 February 2021 18:18 PM UTC

Hi,

we have one big issue after migrating to PB2019R3.

Migrate and Fullbuild is done. The error occurs in PB2019R3 before migrating and also after migrate/fullbuild .

The application crashes after loading OleCustomControl a few times.

The following OLE controls are used:
- rmpHTML.HTMLed (nBit HTML Editor )
- GdPicturePro5.GdViewer

Does anyone have a idea?

I have found a Bugfix Entry in the Changelog, maybe this could have something to do with the bug:
(Bug ID: 5551) When executing CloseUserObject to close a user object that contains an OLE, IDE as well as the PB application both will crash.

Thanks

Last Lines of PBDebug tracing

Application error:
Name der fehlerhaften Anwendung: PB190.exe, Version: 19.2.0.2670, Zeitstempel: 0x6009628d
Name des fehlerhaften Moduls: MSVBVM60.DLL, Version: 6.0.98.48, Zeitstempel: 0x5ea8e7bc
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00002fcb
ID des fehlerhaften Prozesses: 0x%9
Startzeit der fehlerhaften Anwendung: 0x%10
Pfad der fehlerhaften Anwendung: %11
Pfad des fehlerhaften Moduls: %12
Berichtskennung: %13
Vollständiger Name des fehlerhaften Pakets: %14
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: %15

.NET Runtime:
Anwendung: PB190.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: Ausnahmecode c0000005, Ausnahmeadresse 666D2FCB
Stapel:

Windows Error Reporting: (wer-file attached)
Fehlerbucket 2296687540927880487, Typ 1
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: PB190.exe
P2: 19.2.0.2670
P3: 6009628d
P4: MSVBVM60.DLL
P5: 6.0.98.48
P6: 5ea8e7bc
P7: c0000005
P8: 00002fcb
P9:
P10:

Regards,

Tobi

Attachments (1)
Report.zip
  1. Crash
  2. OLE
PSRViewer for PB 2019
Issues calling Orca functions in 2019 R3
Responses (2)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 4 February 2021 18:49 PM UTC
  2. PowerBuilder
  3. # 1

Hi Tobias, This looks like a bug to me.  Please open a support ticket and provide your test case.  Thanks.

Comment
Tobias Roth
  1. Tobias Roth
  2. Thursday, 4 February 2021 19:00 PM UTC
Hi Armeen,



Thanks for the fast answer.

I hope the problem can be solved soon, we need the PB2019R3 features in the near future.



I made the support ticket public in case someone has the same problem:

https://www.appeon.com/standardsupport/track/view?id=6016



Regards,

Tobi
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 4 February 2021 19:29 PM UTC
Thanks. We will treat this as a high priority. An MR for PB 2019 R3 is scheduled within 90 days.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 4 February 2021 19:56 PM UTC
  2. PowerBuilder
  3. # 2

Hi Tobias;

  I had that issue a few years ago before I joined Appeon working at a PB Customer site. We upgraded the PB Version and then these OLE crashes started happening. After looking at the vendor's documentation, we also noticed that the Init() method had a few extra arguments that the PB App did not use initially and more importantly, it had a Finalize() method that the original PB Developer never called. Once we tweaked the OLE container for these proper calling alignments, the App was 100% stable. Food for thought.

Regards ... Chris

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.