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

Resolved Powerserver ToolKit R3 Build 1895 compatibilty with Powerserver Build 2151

  1. Issue
0
Votes
Undo
  1. Miguel Alzate
    Miguel Alzate
  2. PowerServer 2020 or older (Obsolete)
  3. Wednesday, 6 November 2019 14:44 PM UTC

Hi, all!

I've upgraded my Powerserver ToolKit R3 to Build 1895 (on Powerbuilder 2017 R3 Build 1858 Universal Edition) in order to deploy my Web apps to be compatible with Powerserver 2019 Build 2151 (as mentioned in the release announcement). However, when trying to run the app, the following message displays:

Error code : 15056. The Appeon client library (build 1858.00) is incompatible with the PowerServer (build 2151.00). Please contact the administrator.

Why so?

Remove splash screen - Replace Icon
Deployment N Security level
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 7 November 2019 19:34 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi Miguel;

   I just test deployed my OrderEntry framework example application from both PB2019 and PB2017R3 into PS2019 and both instances execute OK with no issues.

   I just noted though that my PB2017R3 and PS toolkit within that IDE are of build 1880 and not 1895.

HTH

Regards ... Chris

Comment
Miguel Alzate
  1. Miguel Alzate
  2. Thursday, 7 November 2019 19:48 PM UTC
Hi and thanks, Chris! I'll check it over.
  1. Helpful
There are no comments made yet.
Kai Zhao @Appeon
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Thursday, 7 November 2019 01:24 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Miguel,

Are you packaging the server deployment project in Toolkit then installing it to PowerServer 2019? If yes, please make sure the PowerServer on your development machine is also upgraded to PowerServer 2019. Otherwise, please deploy the application from Toolkit to PowerServer 2019 directly.

If you have already tried deploying the application from Toolkit to PowerServer 2019 directly, please try closing all browsers and run the application again.

Regards,
ZhaoKai

Comment
Load more comments
Miguel Alzate
  1. Miguel Alzate
  2. Friday, 8 November 2019 12:18 PM UTC
Thanks a lot, Zhao. I will follow the steps and let you know any outcome.
  1. Helpful
Miguel Alzate
  1. Miguel Alzate
  2. Saturday, 28 December 2019 02:45 AM UTC
Hi, ZhaoKai,



I've done exactly the things mentioned in the links you wrote but the issue remains: although, after deploying directly to remote server, the app shows in AEM, the corresponding app folder in c:\inetpub\wwwroot is not created in the remote server (I granted full permissions to IIS users to this folder) nor the app appears in remote IIS.



What else can I do?
  1. Helpful
Kai Zhao @Appeon
  1. Kai Zhao @Appeon
  2. Monday, 30 December 2019 00:38 AM UTC
Hi,



Please specify web server root path to remote web server, for example:

\\\\192.168.168.12\c$\inetpub\wwwroot



Or please specify root path to local machine, and copy application folder to remote machine after deployed successfully.



Regards,

ZhaoKai
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 6 November 2019 17:32 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

Hi Miguel;

   The last PowerServer update was as a "Maintenance Release" to the PB2019 Universal Edition. This MR (2151) only updated the PB IDE's "PS Toolkit" and the Development PS Server to handle newer App features. Not the PB IDE itself. That will come later this year.

   For those customers still on PB2017R3 but want to utilize PS2019 build 2151, you need to apply MR 1895 to be compliant.

FYI: http://support.appeon.com/index.php?/News/NewsItem/View/144/new-mr-version-build-2151-for-appeon-powerserver-2019-for-windowsunixlinux-has-been-officially-released

HTH

Regards ... Chris

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.