1. Clarence Chamorro
  2. PowerServer Mobile (Obsolete)
  3. Saturday, 20 April 2019 18:13 PM UTC

I have PowerServer 2017 WorkGroup running in our production Environment. 6 Apps are working Perfect.

I installed the new Powerserver 2019 in my Test Enviroment. Deploy the 6 Apps from Appeon Powerbuilder 2017. No errors in the deployment process.

I installed the new Appeon workspace in the I-phone 8. Software Version 12.2. Installed Apps from the PowerServer 2019 (Test Environment). NO issues installing them. When I did run them, they do not worked. They are working with no issues in the PowerServer 2017.

Do I have to do something else? Please any advice will be greatly appreciate.

I-Phone -> Appeon WorkSpace Build 1988.00

PowerServer 2019 Trial version, Build 1988.

Regards,

Clarence.

 

The new PowerServer 2019 is running in IIS Ver 10.0.14393.0 and Windows Server 2016.

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 23 April 2019 15:53 PM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 1

Hi Clarence;

   Before reinstalling PB .. please check your PowerServer Toolkit build in the PB IDE, as follows:

 

Regards ... Chris

Comment
  1. Clarence Chamorro
  2. Tuesday, 23 April 2019 21:34 PM UTC
AEM worked perfect.

I disable the Firewall but I am continue having the problem Error: 403.



Any other suggestion?



Regards,



Clarence
  1. Helpful
  1. Clarence Chamorro
  2. Tuesday, 23 April 2019 22:04 PM UTC
Dr Pollach I try to access the IIS via localhost and it working ok.



  1. Helpful
  1. Chris Pollach @Appeon
  2. Wednesday, 24 April 2019 15:42 PM UTC
Hi Clarence;

If you enter the AEM console ... are there messages in any of the logs that might indicate any issues with starting your mobile app(s)?

Regards ... Chris
  1. Helpful
There are no comments made yet.
Clarence Chamorro Accepted Answer Pending Moderation
  1. Sunday, 21 April 2019 19:19 PM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 2

Nevertheless I went an ran the Powerserver 64 setup under the PowerBuilder 2017 R3 installation folder.

Well after I did the set up I can not access any of my apps in my PC. The deployment works perfect. But I can not access the app. I get error 401.

Here the deployment window with no error..

I did check the rights of the root folder. It is correctly set. also it is share..

AEM runs ok, but I can not access any of the apps. I have not upgrade the workspace in my phone. I will be testing with the new Workspace tomorrow morning let you know.

How do I know if the apps are compatible or not with my workspace or with my PowerServer.

Regards,

Clarence.

Comment
  1. Armeen Mazda @Appeon
  2. Monday, 22 April 2019 16:59 PM UTC
Your configuration for this PC is set to "Local Deployment" as shown in the screenshot. If this is not your development PC but rather than separate machine/server then you must use "Remote Deployment" and configure FTP.
  1. Helpful
There are no comments made yet.
Clarence Chamorro Accepted Answer Pending Moderation
  1. Sunday, 21 April 2019 12:15 PM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 3

Please invalid my comment to your question.

Yes I did upgrade PB 2017 Build 1880. Here a picture.

Regards,

Clarence

Attachments (1)
Comment
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Sunday, 21 April 2019 01:44 AM UTC
  2. PowerServer Mobile (Obsolete)
  3. # 4

Did you update your PowerBuilder 2017 to build 1880 (including the PowerServer toolkit)?

Comment
  1. Clarence Chamorro
  2. Sunday, 21 April 2019 01:53 AM UTC
No i did not. How do I do it?

If I Do it is there a way to go back ?

  1. Helpful
  1. Armeen Mazda @Appeon
  2. Monday, 22 April 2019 16:58 PM UTC
To roll back you need to uninstall everything and reinstall. Or if you have imaged your hard drive before the upgrade maybe you can roll back to a previous image.
  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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.