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

Resolved App Compiled in R2 fails after installing R3

  1. Issue
0
Votes
Undo
  1. Shawn Davis
    Shawn Davis
  2. PowerBuilder
  3. Tuesday, 2 March 2021 20:20 PM UTC

I installed R3 a few days ago. Today I tried to run an app compiled in R2 that is installed on my DevPC like it would be on a normal client. The R2 runtime is installed. I'm getting the following error:

Faulting application name: longbow.exe, version: 1.19.1.1, time stamp: 0x5e99c389
Faulting module name: PBSHR190.dll, version: 19.1.0.2328, time stamp: 0x5e99c38d
Exception code: 0xc0000005
Fault offset: 0x000de2c8
Faulting process id: 0x2120
Faulting application start time: 0x01d70f9cabf9a6dc
Faulting application path: C:\Program Files (x86)\LongbowTech\LongbowCMS32\longbow.exe
Faulting module path: C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBSHR190.dll
Report Id: a518aa6c-22cf-4bdc-9e60-bdf94f75aa34
Faulting package full name:
Faulting package-relative application ID:

Not sure why the R3 dev install would cause this problem. Has anyone else run into this? Any advice on troubleshooting?

Thanks in advance.

 

PowerClient CloudAppInstaller is not starting the ...
RestClient and Windows Server 2012
Accepted Answer
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 2 March 2021 20:48 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Shawn;

   Both R2 & R3 and "Minor" releases and as such, cannot co-exist on the same machine. This has always been the case for PB from the early days of PowerSoft, through the Sybase & SAP releases and now into Appeon PB releases. 

   If you need to use both the R2 and R3 releases for different Apps, please either install R3 on another PC or VM where R2 does not reside.

Regards ... Chris

Comment
Shawn Davis
  1. Shawn Davis
  2. Tuesday, 2 March 2021 22:38 PM UTC
Thanks for your input. Fingers crossed. :-)
  1. Helpful
There are no comments made yet.
Responses (3)
Shawn Davis
Shawn Davis Accepted Answer Pending Moderation
  1. Tuesday, 2 March 2021 21:52 PM UTC
  2. PowerBuilder
  3. # 1

Thanks Guys,

I uninstalled the R2 Runtime and reinstalled/rebooted. The app now works. Do you think having done that will now cause my PB R3 dev environment problems? 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 2 March 2021 22:13 PM UTC
Hi Shawn;

I cannot say for certain as I have never tried that aspect in all my beta testing. I always (and still do) use separate machines for R2 vs R3. In theory though (AFAIK) the R3 installation should still be OK (my best guess).

Regards ... Chris
  1. Helpful
mike S
  1. mike S
  2. Tuesday, 2 March 2021 22:57 PM UTC
I would guess that yes, your r3 is now broken.



going forward this won't be a problem as 2019R3 and future allows different releases down to the build. Doesn't work for anything prior to 2019R3.
  1. Helpful
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Tuesday, 2 March 2021 20:39 PM UTC
  2. PowerBuilder
  3. # 2

Hi, Shawn - 

"The R2 runtime is installed"... installed where? With the app exe/pbd's? In a folder referenced in the system path? Please elaborate. If the deployed app was somehow picking up and using the runtime DLL's from your PB IDE installation, the app will not be able to locate these DLL's now that you have migrated the IDE to R3. You need to make sure the R2 runtime DLL's are deployed and are accessible with the R2 app.

This is because the names of the runtime DLL's in R3 have changed. The version # suffix has been removed (PBVM190.dll is now PBVM.dll, for example).

Regards, John

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.