Hi ZhaoKai,

Again thank you so much for your support, we already upgraded the toolkit PowerServer to R3 version without upgraded PowerBuilder (still PowerBuilder 1666) and we installed PowerServer R3 (PB developer edition) at the server. We tested our application and it is working as expected. Also, we tested the PowerServer multi-instance feature with successful results.

Then, we asked to Appeon support for the link to download PowerServer R3 to use our licenses and they send to us this instruction: you should first download and install the GA version (PowerServer 2017 Build 1689) [support.appeon.com] and then apply  this MR #1858 [support.appeon.com]

Then, we followed these instructions and new the PowerServer multi-instance feature does not work. When you say "PowerServer multi-instance feature had been removed from PowerServer 2017" Do you mean for all versions? Why did this feature work with the PowerServer R3 PB developer edition? 
 

Best Regards,
Oscar Naranjo

Hi ZhaoKai,

Thank you so much for your support, 

Now, with the instruction that you sent to us, we are trying to install the PowerServer instances on our other websites at the development server but we got the error "Failed to find the main Appeon Server. You must install an Appeon Server before creating a new Appeon Server instance" when we executed the file instanceConfiguration.exe inside of the C:\inetpub\wwwroot\appeon\Toolkit\instance. This instance is working fine with AEM. 

In addition, when you recommended keeping PowerBuilder version as the same as the Toolkit version, you mean that we can upgrade the PowerBuilder toolkit without upgrade PowerBuilder classic, is this possible? We have the licenses of PowerBuilder 2017 and PowerServer separately and we have PowerBuilder classic applications in production compiled with PowerBuilder 2017 R1 so we cannot move to 2017 R3 for now, but our web application versions still in development so they could be deployed in new versions. 

Finally, I'm not clear if Appeon PowerServer 2017 Build 1756.00 32-bit Edition is compatible with PowerServer Toolkit 1666. 

Best Regards,
Oscar Naranjo 

Hi Oscar,

1) It is suggested to install PowerServer with the administrator user plus 'Run as Administrator', and please try to grant user 'everyone' full control permission on C:\inetpub\wwwroot.

2) Please refer to the article below to solve the issue.
https://www.appeon.com/support/documents/appeon_online_help/pb2017r3/appeon_troubleshooting_guide/ch07s02s04.html#Error13016

3) Does http connection work well? Both http and https should have the same behavior.

4) The license is per server, and you can install one PowerServer on one machine, but you can create multiple PowerServer instances. These multiple PowerServer instances use the same license.
https://www.appeon.com/support/documents/appeon_online_help/2016/installation_guide/bk01ch03s04s02.html#Appeon_Server_instance_configuration

5) For PowerServer PB edition that is included in PowerBuilder installer, the 64-bit PowerServer is installed by default on 64-bit machines. You can force it to install 32-bit PowerServer instead of the 64-bit one by editing the product.ini file in the installer package to add the following setting under [Product] node: Platform=32

You can install PowerServer 2017, and it is recommended to keep PowerBuilder version as thee same as the Toolkit version.
http://support.appeon.com/index.php?/News/NewsItem/View/107/appeon-powerserver-2017-ga-version-for-windowsunixlinux-have-been-officially-released

Regards,
ZhaoKai

Hi ZhaoKai,

I am working with David on this project. According to Chris recommendations, we installed the ASE Sybase database client on the server and more than 80% of the errors were resolved, but some weird errors persist.

The server is configured with Windows Server 12 R2, IIS version 8.5, Appeon PowerServer 2017 Build 1756.00 32-bit Edition, ASE Client Sybase 16, and an SSL certificate HTTPS. From my side, I have installed PowerBuilder 2017 version 1666 and PowerServer Toolkit 1666. 

When I run the deploy process against the server, it does not generate any errors.

Below I will try to list some errors and considerations: 

1) Appeon Enterprise Manager is generating some errors.

- When we tried to save on Application -> Performance -> Datawindow Data Cache. We got 404 error (attached AEM_ERROR1.JPG)

- When I click on Application -> Data Transfer -> Charset. We got 404 error (attached AEM_ERROR2.JPG)

2) In our application before to install the database client, we got more than 5 different error, now we only got the error 13016 - Cannot find the following embedded SQL in AppeonDB: ApplicationName = ********* and SQLKey = @@sql_1_unv_current_data_timer (attached APP_ERROR1.JPG). 

3) The SSL certificate could be generating these problems? It is important to note that the behavior of our application is different when we execute in HTTP of when we execute https, in fact, it is faster in https. Should we do tests considering these 2 different environments?

4) About the license of PowerServer, in the IIS servers, there is a hierarchy between sites (URL: www.mysite.com) and applications, when we install PowerServer it asks us to select the site where we want to install it then it creates for us several applications within the site (AEM, APPEON, etc). My question is the license is per server or per site? Is there the possibility of installing PowerServer for multiple sites on the same server?

5) For PowerBuilder R1 there is a 64bit version of PowerServer?, Could it be part of the problem? Can I install new versions of PowerServer and Toolkit PowerServer without changing the PowerBuilder version?

Best Regards, 

Oscar Naranjo 

Hi David,

If there is any deploy error? please make sure your PowerServer Toolkit version is same as PowerServer.

Please note that you cannot copy the files to the web server manually to deploy/update application.

Please refer to the following article for details:

https://support.appeon.com/index.php?/Knowledgebase/Article/View/150/0/appeon-developer-deployment-processarchitecture-and-why-users-cannot-copy-files-to-appeon-server-manually

Please try to full deploy the application from the PowerServer Toolkit, or full deploy the application, and then package it again to install the application on this server and see if the issue can be resolved.

Regards,
ZhaoKai

For #3 - you'll need the 64 bit ASE DB Client installed for the PowerServer deployed machine and - if you plan to run any PB logic on the same IIS deployed instance (ie Web Service, Assembly or EXE) - you'll need the 32bit DB client installed for ASE as well in order for those to access the ASE DB.

Hi Chris, 

I work with Davis and I am going to answer the questions for him: 

1) Any difference in the DataSource definition on your Local IIS vs Deployed IIS?

NO

2) Are you using IIS for both the App and Web server?

YES

3) Are the ASE DB Client installs the same on the Local & Deployed IIS?

NO, Local is installed & Deployed IIS not.    

4) How are you connecting to ASE from PowerServer (that is - your DB Client type)?

ASE Native Driver

5) What exactly is the "@@SQL_3_u_sscs_server" global variable?

 It is an object that is making a select against the database. 

Best Regards,

Oscar Naranjo 

Hi David;

  Can you tell us ...

1) Any difference in the DataSource definition on your Local IIS vs Deployed IIS?

2) Are you using IIS for both the App and Web server?

3) Are the ASE DB Client installs the same on the Local & Deployed IIS?

4) How are you connecting to ASE from PowerServer (that is - your DB Client type)?

5) What exactly is the "@@SQL_3_u_sscs_server" global variable?

Regards ... Chris