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

Resolved Building causes PB2022 R2 to crash

  1. How-to
0
Votes
Undo
  1. Brett Weaver
    Brett Weaver
  2. PowerBuilder
  3. Sunday, 10 September 2023 20:59 PM UTC

** I have just copied the code to another machine with the same version of PowerBuilder and it compile with no errors **

** It seems to be an environmental problem I guess my laptop is no longer capable of compiling this code. This may be because of corporate policy changes as well as other things of course **

Be nice if powerbuilder failed in a more friendly manner

Whether its a build, PowerClient Build and Deploy or standard build its gets past attaching to the database and is scrolling through the scripts and then PowerBuilder just terminates. No messages, no nothing, it just disappears.

The event viewer gives me:

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

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

Log Name: Application
Source: Application Error
Date: 11/09/2023 8:50:04 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: WCC-5CG2232GNQ
Description:
Faulting application name: PB220.exe, version: 22.1.0.2819, time stamp: 0x64c36da2
Faulting module name: PBSHR.dll, version: 22.1.0.2819, time stamp: 0x64c7774c
Exception code: 0xc0000005
Fault offset: 0x001cccb0
Faulting process id: 0x118c
Faulting application start time: 0x01d9e427a98d6be2
Faulting application path: C:\Program Files (x86)\Appeon\PowerBuilder 22.0\PB220.exe
Faulting module path: C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 22.1.0.2819\PBSHR.dll
Report Id: a1183b4b-7c9f-4135-a91f-d486e68b62a1
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-09-10T20:50:04.7993461Z" />
<EventRecordID>142583</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>WCC-5CG2232GNQ</Computer>
<Security />
</System>
<EventData>
<Data>PB220.exe</Data>
<Data>22.1.0.2819</Data>
<Data>64c36da2</Data>
<Data>PBSHR.dll</Data>
<Data>22.1.0.2819</Data>
<Data>64c7774c</Data>
<Data>c0000005</Data>
<Data>001cccb0</Data>
<Data>118c</Data>
<Data>01d9e427a98d6be2</Data>
<Data>C:\Program Files (x86)\Appeon\PowerBuilder 22.0\PB220.exe</Data>
<Data>C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 22.1.0.2819\PBSHR.dll</Data>
<Data>a1183b4b-7c9f-4135-a91f-d486e68b62a1</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

 

 

 

setting paperwidth for richtext v.28 stopped worki...
Picture
Accepted Answer
Brett Weaver
Brett Weaver Accepted Answer Pending Moderation
  1. Monday, 11 September 2023 03:53 AM UTC
  2. PowerBuilder
  3. # Permalink

Hi Chris

Following your advice I optimised all of the libraries and then started to go through the objects in the library where it seemed to stop. Regenerating objects (windows) would sometimes cause PowerBuilder to crash and then the next time I tried they would regenerate ok only for one that had previously regenerated ok to fail. When I did manage to regenerate all in the library at one go I thought I must have sorted it but no, it would not rebuild and failed at the same place.

I tried exporting and importing the objects but that didn't help

I then copied the application source onto a memory stick and rebuilt the application on another PC which has PB2022 R2 build 6973 on it. All went fine, no crash at all and no errors.

I am happy to provide the application source so that Appeon can determine why it crashes as its starting to worry me. Its 94MB with all the .icons and other resources. I guess I will make a formal Technical support call.

Cheers & thanks

 

Brett

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 11 September 2023 12:32 PM UTC
Hi Brett;

If it builds & deploys OK on another PC then your crashing issue sounds more environmental related than PB.

On the PC that builds OK, is it using the same OS version, Antivirus, SCM, etc software?

Regards ... Chris
  1. Helpful 2
There are no comments made yet.
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Sunday, 10 September 2023 21:23 PM UTC
  2. PowerBuilder
  3. # 1

 Hi Brett;

  I would like to suggest ...

  1. Make sure that none of your App Workspace folders, subfolders & their files are not write protected.
  2. Delete your PC App from the current web server 
  3. Optimize all your App's PBL's
  4. Using the object browser, regenerate from your top level Window, Menu & User objects all of their descendants.
  5. From the Target, perform a Full Build
  6. Close & restart your PB IDE

Now try your App's PowerClient build & deploy again.

HTH

Regards... Chris 

Comment
Brett Weaver
  1. Brett Weaver
  2. Monday, 11 September 2023 23:19 PM UTC
Failing hardware was not something I thought of... Your checklist will be valuable in the future I am sure
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 11 September 2023 15:14 PM UTC
  2. PowerBuilder
  3. # 2

Hi,

1. Maybe - id you have an SSD drive - your disk drive is failing. Run a tool like CrystalDiskInfo to check on the SMART.

2. I'm under the impression that powerbuilder somehow "caches" stuff. Sometimes I'm all day running into a problem and then after a reboot the problem suddenly simply has disappeared.

 

Edit:

As an explanation: I have 2 SSD drives, both from the brand "Crucial". The one that is 7.8 years old (256 GB) still has 85% of lifespan left. The newer one, 1.8 years old (500GB) only has 6% of lifespan left. The old (but good) drive has a LOT more writes than the new one. They'r supposed to endure like 150TB, but my bad drive has only written 30TB so far. (Switching to Samsung that's for sure).

regards

 

Comment
Load more comments
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Tuesday, 12 September 2023 16:04 PM UTC
Hi Mark,

Yes, that's how I noticed. I was using Crucial Storage Executive to check on my over provisioning. It reported the drive as near TBW limits (total bytes written) and after a firmware upgrade it shows as"Near end of life". I used CrystalDiskInfo to double check.

OpenHardwareMonitor also reports that the drive has little life left.

Both drives are MX series.

regards.
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Tuesday, 12 September 2023 16:08 PM UTC
*Correction: that was probably not a "firmware" update, but update of the Executive program (or both? can't remember). There's been lots of problems caused by buggy firmware on these drives, some causing a short lifespan. (not sure if that's just the reported lifespan or the real lifespan, but can't run any risks. Replacing with another drive. Hopefully Samsung does better).
  1. Helpful
Mark Goldsmith
  1. Mark Goldsmith
  2. Tuesday, 12 September 2023 16:44 PM UTC
Thanks for the additional info. Thankfully I've had no failures yet with Crucial but good to know. Best of luck with the Samsung drives.

Regards...Mark
  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.