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

Resolved Defect PSR file causes Powerbuilder to crash

  1. Issue
0
Votes
Undo
  1. Stefan Malkwitz
    Stefan Malkwitz
  2. PowerBuilder
  3. Thursday, 1 July 2021 13:22 PM UTC

Defect PSR file causes Powerbuilder to crash

Hi Everyone,

we have a defect PSR file that causes Powerbuilder to crash everytime i try to edit it

How ro reproduce this:

1. Open the File "d_view_vlge_000000000001005451.psr" with Powerbuilder
2. go to Design
3. Right click any nested reports. For Example "nest_auftkpf_lfv"
4. click Modify Report ...

 

Crash Message:

[Window Title]
Appeon PowerBuilder 2019 R3

[Main Instruction]
Appeon PowerBuilder 2019 R3 funktioniert nicht mehr

[Content]
Windows kann online nach einer Lösung für das Problem suchen.

[^] Problemdetails ausblenden [Online nach einer Lösung suchen und das Programm schließen] [Programm schließen]

Problemsignatur:
Problemereignisname: APPCRASH
Anwendungsname: PB190.EXE
Anwendungsversion: 19.2.0.2670
Anwendungszeitstempel: 6009628d
Fehlermodulname: KERNELBASE.dll
Fehlermodulversion: 6.3.9600.19724
Fehlermodulzeitstempel: 5ec50c3e
Ausnahmecode: c0000005
Ausnahmeoffset: 000156e8
Betriebsystemversion: 6.3.9600.2.0.0.272.7
Gebietsschema-ID: 1031
Zusatzinformation 1: 0655
Zusatzinformation 2: 06550e0d4dd8c9232938178ff0703e29
Zusatzinformation 3: fdb5
Zusatzinformation 4: fdb5d0dc0fd5f677ddd972efe469a1a4

Lesen Sie unsere Datenschutzbestimmungen online:
http://go.microsoft.com/fwlink/?linkid=280262

Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen Sie unsere Datenschutzbestimmungen offline:
C:\Windows\system32\de-DE\erofflps.txt

 

 

Anyone get the same results, or is this just us?
Any idea how to fix this?

beste regards Stefan

Attachments (2)
d_view_vlge_000000000001005451.zip
crash.png crash.png
Powerclient signing questions
datawindow expression -> parent reference
Accepted Answer
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 1 July 2021 13:37 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Stephan;

   You cannot edit a PSR file. It's a proprietary format. You can recreate it and view it in a DW Control though.

  Note1: Any DW Object or PSR file name that you assign to a DW Control' "DataObject" property cannot exceed 32 characters. This is true for all Appeon PB versions in including PB2021 beta. Exceeding this rule will cause App crashes.

Note2: Note1 also applies to child DWO's.

Note3: PSR files contain DWO source. As such, they are release dependant. Assigning a PSR to a DC with the PB runtime not the same as the PSR was created in could cause App crashes.

HTH

Regards ... Chris

Comment
There are no comments made yet.
Responses (3)
Gregory Rusak
Gregory Rusak Accepted Answer Pending Moderation
  1. Friday, 6 August 2021 22:37 PM UTC
  2. PowerBuilder
  3. # 1

Hello Chris,

I just happened across this post of yours and was surprised to read about the 32 character limit of a datawindow object name assigned to a datawindow control.

We have a number of cases where we assign an object that is greater than 32 characters to a datastore dataobject as follows:

lds_charting_scans_and_attachments_list = CREATE n_aumcon_ds

lds_charting_scans_and_attachments_list.DataObject = 'd_charting_scans_and_attachments_list'

IF lds_charting_scans_and_attachments_list.of_SetTransObject(sqlca) < 0 THEN

PopulateError(100, 'of_SetTransObject failed')

ROLLBACK USING sqlca;

DESTROY lds_charting_scans_and_attachments_list

gnv_app.of_app_error()

RETURN FAILURE

END IF

and we don't experience any crashes.

So does the same apply to datastores ?

Comment
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Friday, 2 July 2021 06:18 AM UTC
  2. PowerBuilder
  3. # 2

Hi,

When I open the psr file with powerbuilder, I'm getting this error:

---------------------------
Preview - d:\_wizsource\powerbuilder2019\vector\vector3\test\test app\d_view_vlge_000000000001005451.psr
---------------------------
Load of the nested report nest_nachs4auft failed.
---------------------------
OK   
---------------------------

 

So I said, let me delete it and see if that one is the culprit. When deleting it, all others also seem to fail.
It does not blow up though! I'm just getting blablabla... failed ... messages.

What operating system are you running this on? I'm asking because I've seen a lot of "Ausnahmecode: c0000005" errors on Windows 2012

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.