• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Powerbuilder 2017 R3 studio crashes on debug or page update migrating from pb 11.5

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

Resolved Powerbuilder 2017 R3 studio crashes on debug or page update migrating from pb 11.5

  1. How-to
0
Votes
Undo
  1. amit kurhe
    amit kurhe
  2. PowerBuilder
  3. Tuesday, 18 February 2020 00:23 AM UTC

Hi team, i am trying to migrate a PB 11.5 version code in Pb 2017 R3 version, but after migration debug the studio crashes & close down not able to figure out why its happening. Some time it crashes when i try to update any of the file of the solution from the power builder. is it any dll conflict please advise how to check the issue to make it stable so that i can check the code & debug further. thanks.   

Consuming WCF web service
Get All open windows
Responses (4)
David Peace (Powersoft)
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Friday, 21 February 2020 14:02 PM UTC
  2. PowerBuilder
  3. # 1

Hi Amit

Have you got anywhere in resolving this issue? Do you have any more information i.e. what the application is trying to do when the crash occurs. If you are debugging something specific what is that tryign to do?

With a bit more information I'm sure we can help you here.

Cheers

David

Comment
There are no comments made yet.
amit kurhe
amit kurhe Accepted Answer Pending Moderation
  1. Thursday, 20 February 2020 17:25 PM UTC
  2. PowerBuilder
  3. # 2

seeing below error on the windows log

 

Faulting application name: PB170.EXE, version: 17.2.0.1858, time stamp: 0x5b6318f9
Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2be1e
Exception code: 0xc0000005
Fault offset: 0x00001ed7
Faulting process id: 0x33ac
Faulting application start time: 0x01d5e810a63d1baa
Faulting application path: C:\Program Files\Appeon\PowerBuilder 17.0\PB170.EXE
Faulting module path: C:\windows\SYSTEM32\MSVCR100.dll
Report Id: 55d85042-641f-4c6e-8c0e-b749b05e67bf
Faulting package full name:
Faulting package-relative application ID:

Comment
amit kurhe
  1. amit kurhe
  2. Thursday, 20 February 2020 17:43 PM UTC
Faulting application name: PB170.EXE, version: 17.2.0.1858, time stamp: 0x5b6318f9

Faulting module name: PBSHR170.dll, version: 17.2.0.1858, time stamp: 0x5b6318c3

Exception code: 0xc0000005

Fault offset: 0x000a29e6

Faulting process id: 0x3424

Faulting application start time: 0x01d5e814e7ec8587

Faulting application path: C:\Program Files\Appeon\PowerBuilder 17.0\PB170.EXE

Faulting module path: C:\Program Files\Appeon\Shared\PowerBuilder\PBSHR170.dll

Report Id: b4f8a898-9191-49f8-9559-794deee77686

Faulting package full name:

Faulting package-relative application ID:
  1. Helpful
Ken Guo @Appeon
  1. Ken Guo @Appeon
  2. Friday, 21 February 2020 04:58 AM UTC
Hi Amit，



I suggest you report a bug in Appeon Support ticketing system (https://www.appeon.com/standardsupport/newbug) and provide as much information as you can, including a reproducible case, crash dump, etc.

Thanks in advance.



Regards,

Ken

  1. Helpful
There are no comments made yet.
Ken Guo @Appeon
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 18 February 2020 05:23 AM UTC
  2. PowerBuilder
  3. # 3

Hi Amit,

Except for what Chris mentioned, please let us know:


1).Do you use PBX in your application? If yes, please import the PBX again.
  For example, the steps for pbsoapclientxxx.pbx should be as follows:  Right click to select pbl->>Import PB Extension ->>pbsoapclient170.pbx (pbsoapclient170.pbx locates at C:\Program Files (x86)\Appeon\Shared\PowerBuilder).

2).Do you use PFC in your application? If yes, please use the PFC of PB 2017. Download link: https://github.com/OpenSourcePFCLibraries.

3).Please tell us more information about the error, including when the error occurs and the Windows log.

Regards，
Ken

Comment
amit kurhe
  1. amit kurhe
  2. Thursday, 20 February 2020 17:29 PM UTC
Hi Ken, thanks for the reply. i am very new to PB & i am asked to work on existing PB application which gives error when installed on Windows 10. below error in the application event log . thanks,



Faulting application name: PB170.EXE, version: 17.2.0.1858, time stamp: 0x5b6318f9

Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2be1e

Exception code: 0xc0000005

Fault offset: 0x00001ed7

Faulting process id: 0x33ac

Faulting application start time: 0x01d5e810a63d1baa

Faulting application path: C:\Program Files\Appeon\PowerBuilder 17.0\PB170.EXE

Faulting module path: C:\windows\SYSTEM32\MSVCR100.dll

Report Id: 55d85042-641f-4c6e-8c0e-b749b05e67bf

Faulting package full name:

Faulting package-relative application ID:
  1. Helpful
amit kurhe
  1. amit kurhe
  2. Thursday, 20 February 2020 17:43 PM UTC
Faulting application name: PB170.EXE, version: 17.2.0.1858, time stamp: 0x5b6318f9

Faulting module name: PBSHR170.dll, version: 17.2.0.1858, time stamp: 0x5b6318c3

Exception code: 0xc0000005

Fault offset: 0x000a29e6

Faulting process id: 0x3424

Faulting application start time: 0x01d5e814e7ec8587

Faulting application path: C:\Program Files\Appeon\PowerBuilder 17.0\PB170.EXE

Faulting module path: C:\Program Files\Appeon\Shared\PowerBuilder\PBSHR170.dll

Report Id: b4f8a898-9191-49f8-9559-794deee77686

Faulting package full name:

Faulting package-relative application ID:
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 18 February 2020 02:36 AM UTC
  2. PowerBuilder
  3. # 4

Hi Amit;

   Before you migrated, did you...

1) Optimize all your PB 11.5's PBL's?

2) Perform a Full Build ( no errors or warnings)?

3) Run the PB2017R3 "Migration Assistant" on your 11.5 App's code?

Regards ... Chris

Comment
amit kurhe
  1. amit kurhe
  2. Thursday, 20 February 2020 17:27 PM UTC
Hi Chris, thanks for the reply. do not have the PB 11.5 version so cannot tell about it but when i rebuild it gives no error. Below are the logs i see in application event log may be this will give you a hint. thanks



Faulting application name: PB170.EXE, version: 17.2.0.1858, time stamp: 0x5b6318f9

Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2be1e

Exception code: 0xc0000005

Fault offset: 0x00001ed7

Faulting process id: 0x33ac

Faulting application start time: 0x01d5e810a63d1baa

Faulting application path: C:\Program Files\Appeon\PowerBuilder 17.0\PB170.EXE

Faulting module path: C:\windows\SYSTEM32\MSVCR100.dll

Report Id: 55d85042-641f-4c6e-8c0e-b749b05e67bf

Faulting package full name:

Faulting package-relative application ID:
  1. Helpful
amit kurhe
  1. amit kurhe
  2. Thursday, 20 February 2020 17:43 PM UTC
Faulting application name: PB170.EXE, version: 17.2.0.1858, time stamp: 0x5b6318f9

Faulting module name: PBSHR170.dll, version: 17.2.0.1858, time stamp: 0x5b6318c3

Exception code: 0xc0000005

Fault offset: 0x000a29e6

Faulting process id: 0x3424

Faulting application start time: 0x01d5e814e7ec8587

Faulting application path: C:\Program Files\Appeon\PowerBuilder 17.0\PB170.EXE

Faulting module path: C:\Program Files\Appeon\Shared\PowerBuilder\PBSHR170.dll

Report Id: b4f8a898-9191-49f8-9559-794deee77686

Faulting package full name:

Faulting package-relative application ID:
  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.