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

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

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

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

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

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

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.

Chris,

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