1. John Raghanti
  2. PowerBuilder
  3. Wednesday, 24 July 2024 16:54 PM UTC

Hi,

I recently upgraded from PB 2022R2 build 1892 to PB 2022R3 build 3356 because my company is trying to do a PowerServer proof of concept.

I went into my normal application and anytime I try to run the application or do a full build or regenerate different objects, PB is closing with no notification, and I'm seeing logs in the Event Viewer like this:

Faulting application name: PB220.exe, version: 22.2.0.3356, time stamp: 0x66051d57
Faulting module name: PBSHR.dll, version: 22.2.0.3356, time stamp: 0x66051d0a
Exception code: 0xc0000005
Fault offset: 0x001d6780
Faulting process id: 0x15ec
Faulting application start time: 0x01dadde81c162010
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.2.0.3356\PBSHR.dll
Report Id: 096d31a9-e7e4-49dc-85d9-8c3a8ca333f3
Faulting package full name:
Faulting package-relative application ID:

I tried replacing all of my PBLs with fresh ones and getting latest on everything. That went well. However, as soon as I try to do anything, it crashes again.

Any idea what I can do to resolve this issue?

Thanks!

JR

Accepted Answer
John Raghanti Accepted Answer Pending Moderation
  1. Monday, 12 August 2024 16:23 PM UTC
  2. PowerBuilder
  3. # Permalink

Wanted to post an update to this item as we figured it out after a lot of trial and error. There actually were 2 issues.

1. There was some encoding or something going on in one of our windows that was causing the object not to regenerate. It was in an inline SQL statement. We re-wrote that statement from scratch and that fixed that window.

2. The other window was weirder, but it also dealt with inline SQL statements. It would not regenerate. If we checked it out, we got a message that there was a "compile/import failure in phase 3" with no other messaging. We went through and commented out all functions and events and the window regenerated. We then walked through each script and uncommented one by one until we found the offending script. Once we found that script, PB just crashed when we tried to save it. We didn't see anything wrong until we hit CTRL-L in the event before saving it. It pointed out that there was a syntax issue with 2 inline statements. Both of them were doing a SELECT INTO: y FROM xx_transaction, but then the where clause was referencing a different table, e.g. WHERE transaction.column = 'yaddayadda'. We fixed those SQL statements and everything was running normally again. 

It was difficult to find because all we could do was Edit Source, and that editor did not provide any messaging at all. It's a good sized window with 3 dozen controls and a lot of inherited objects. But we're up and running again!

Comment
  1. Armeen Mazda @Appeon
  2. Monday, 12 August 2024 19:01 PM UTC
Thanks for sharing the solution it will be helpful to others I'm sure! :-)
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 24 July 2024 17:26 PM UTC
  2. PowerBuilder
  3. # 1

Hi JR;

  After a PBL "refresh", did you try optimizing all your PBL's and then performing another Full build (with no errors or warnings appearing)?

Regards .. Chris

Comment
  1. John Raghanti
  2. Thursday, 25 July 2024 13:02 PM UTC
Hi Chris, I put in new PBLs and optimized all libraries. It crashed again during the full build. Same event viewer messages I was seeing before.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Thursday, 25 July 2024 15:18 PM UTC
In that case, it sounds like a possibility that there are corrupt object(s).

Unfortunately, since we do not have access to your development / deployment environments - we can only guess.
  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.