• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • PowerBuilder 2022 crash when opening DataWindow Object

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

Resolved PowerBuilder 2022 crash when opening DataWindow Object

  1. Issue
0
Votes
Undo
  1. Timothy Beck
    Timothy Beck
  2. PowerBuilder
  3. Wednesday, 12 October 2022 22:27 PM UTC

I've converted an application from PB 2021 to PB 2022.  The application was originally written in PB 2017, then converted to PB 2019, then PB 2021.  When opening the DataWindow, PB 2022 crashes without error message.  The same is true when creating a new DW, after selecting the DW type.

I've uninstalled PowerBuilder and reinstalled it without resolving the issue.

Any suggestions?

Tim

  1. DataWindow
  2. PowerBuilder (Appeon)
Autoscript with PB2022
GetAdaptersAddresses - anyone have this coded for...
Responses (8)
Timothy Beck
Timothy Beck Accepted Answer Pending Moderation
  1. Wednesday, 12 October 2022 22:48 PM UTC
  2. PowerBuilder
  3. # 1

OS Version: Windows 11 Pro 22H2 22621.521

PB Version: 2022 Build 1878

More detail from the event viewer:

Faulting application name: PB220.exe, version: 22.0.0.1878, time stamp: 0x6308a9b4
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000041d
Fault offset: 0xe3866349
Faulting process id: 0x0x5630
Faulting application start time: 0x0x1D8DE8B9CFAFB21
Faulting application path: C:\Program Files (x86)\Appeon\PowerBuilder 22.0\PB220.exe
Faulting module path: unknown
Report Id: fec51065-57d6-488b-9b3e-91155ee4660c
Faulting package full name:
Faulting package-relative application ID:

 

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

Problem signature:
P1: PB220.exe
P2: 22.0.0.1878
P3: 6308a9b4
P4: StackHash_fee9
P5: 0.0.0.0
P6: 00000000
P7: c0000005
P8: PCH_9F_FROM_ntdll+0x00076ACC
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.cf00b544-4465-4a73-b287-496f05a56366.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.8f9e5a52-721b-47ce-b71e-ab9c824060c1.tmp.WERInternalMetadata.xml
WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20221002_1_EC_0_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c534a28e-567b-4d0b-9d81-ecc61b0090b0.tmp.etl
WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4371b15a-8951-44cc-80b3-1b2790978f23.tmp.etl
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e21d7f8c-49a4-46b2-8875-cdc72a9fd30c.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.142f658f-f4c2-4099-8d44-743740aad1b5.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b5c06f36-60fb-4319-9650-5fca6dd4c7c9.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_PB220.exe_24ba331d1831fb9f92792be74f96b3876ddd9_378d23ce_42e85338-bbf6-4ff0-b675-cb5a72a349b4

Analysis symbol:
Rechecking for solution: 0
Report Id: 015d534b-98cc-4d73-a102-312c9fbb7ce6
Report Status: 268435456
Hashed bucket: 98f31d2e7bd90496759ed486e055421f
Cab Guid: 0

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 12 October 2022 22:59 PM UTC
  2. PowerBuilder
  3. # 2

Hi Tim:

  I suspect it might be because the DW Painter's layout is corrupt in some way that is now causing the instability.

  Please try this procedure ...

  1. Close the PB IDE
  2. Run RegEdit utility
  3. Navigate to ... HKEY_CURRENT_USER\Software\Sybase\Powerbuilder\22.0\Layout\Default
  4. Delete the Datawindow string entry
  5. Restart PB IDE and try opening the datawindow painter again.

HTH

Regards .... Chris

Comment
Timothy Beck
  1. Timothy Beck
  2. Wednesday, 12 October 2022 23:04 PM UTC
Chris,



I thought of that, but there's no Layout folder under PowerBuilder 22.0. I tried adding it, same result.



Tim
  1. Helpful
There are no comments made yet.
Timothy Beck
Timothy Beck Accepted Answer Pending Moderation
  1. Wednesday, 12 October 2022 23:46 PM UTC
  2. PowerBuilder
  3. # 3

Update:

I tried reimporting the 2021 version of the application and PB 2022 crashed on migration.  I did the same thing with the 2019 version.  Same results.

Tim

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 13 October 2022 18:27 PM UTC
Hi Tim;

Investigating this aspect a bit further I found a revelation. Newer PB IDE's do NOT create these registry entries *until*, you alter the layout in the PB2022's IDE after you initially install the PB product. It's only after you modify a layout or even afterwards from there restore the painter's layout default - that these registry entries are then present. That was new to me as older IDE's used to create these registry entries upon installation. Well... you learn something new every day - LOL!

So having no registry entries for these painter layouts is not a problem right after an installation. It just means that your PB2022 IDE layouts are running as the "Installation Defaults". ;-)

Thus, I am surmising that your stability issue is not layout related. Nor, can I explain this weird IDE crashing behaviour. Other than you seem to be on the latest W11 O/.S version 22H2 that was just released. All of PB2022's GA testing (AFAIK) was done on 21H2 - so that might be something to look at from our Engineering team perspective (just a guess on my part).

I would now suggest that you create a Support Ticket for this issue in order to get our Engineering team involved for a resolution.

Regards ... Chris
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 13 October 2022 00:30 AM UTC
  2. PowerBuilder
  3. # 4

Hi Tim;

  That is the problem. Here is my registry settings (the registry path exists for me) ...

 

  Also, I see that  you are on the new 22H2 build of W11. I wonder if this is the issue!!!!!!!!!!!!!

 

Regards ... Chris

Comment
Timothy Beck
  1. Timothy Beck
  2. Thursday, 13 October 2022 09:15 AM UTC
Chris,



It could be the new build of W11. I doubt it's the registry setting as I've added the keys in to the registry and the same problem exists.



Tim
  1. Helpful
There are no comments made yet.
Berka Frenfert
Berka Frenfert Accepted Answer Pending Moderation
  1. Thursday, 13 October 2022 07:22 AM UTC
  2. PowerBuilder
  3. # 5

I think your app crashes when it goes for db connections. You can change it in settings.

In Datawindow Options there is checkbox "Retrieve on preview"

Uncheck that

 

Try that.

Comment
Timothy Beck
  1. Timothy Beck
  2. Thursday, 13 October 2022 09:13 AM UTC
Hi Berka!



I thought of that, so I made sure I'm connected before I attempt to open the painter. Also, if I try to create a new datawindow, PB crashes. Finally, it crashes when migrating, whether I'm connected to a database or not.



Tim
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 13 October 2022 18:29 PM UTC
Hi Tim;

Did you select the PB Demo DB in the IDE's DB Profile painter & then try to build a new DWO using that DB connection?

Regards ... Chris
  1. Helpful
There are no comments made yet.
Ken Guo @Appeon
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Friday, 14 October 2022 02:40 AM UTC
  2. PowerBuilder
  3. # 6

Hi Tim,

 

I suggest you check the directory where your PBL/PBT files are located and see if it contains PB2019/PB2021 PB Runtime Files(*.dll). If yes, please remove PB2019/PB2021 PB Runtime Files(*.dll) and verify if the problem is solved.

 

 Regards,

Ken

 

Comment
Timothy Beck
  1. Timothy Beck
  2. Wednesday, 19 October 2022 11:44 AM UTC
Ken,



That solved it! Thanks!



Tim
  1. Helpful
Ken Guo @Appeon
  1. Ken Guo @Appeon
  2. Thursday, 20 October 2022 03:04 AM UTC
Thanks for your feedback!
  1. Helpful
There are no comments made yet.
Simone Olianti
Simone Olianti Accepted Answer Pending Moderation
  1. Friday, 14 October 2022 11:06 AM UTC
  2. PowerBuilder
  3. # 7

i had a similar issue in the past.
pb ide was crashing during migration or even a full build. In my case it was a corrupted .pbl

to solve this  i've just exported all the pbl objects, created a new .pbl from scratch and imported back the objects inside the new file. After this the migration completed successfully

Comment
There are no comments made yet.
Raymond Longoria
Raymond Longoria Accepted Answer Pending Moderation
  1. Friday, 27 January 2023 22:21 PM UTC
  2. PowerBuilder
  3. # 8

Chris,

I had the exact same issue and your solution worked. Thanks!

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 27 January 2023 23:58 PM UTC
That's awesome Raymond! :-)
  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.