1. Hannu Pikkarainen
  2. PowerServer
  3. Monday, 3 July 2023 10:02 AM UTC

Hi,

I'm using PB 2022R2 and setting up my first Power Server application and I run into several problems. Test environment is running in a single Windows 2019 server on Azure, SQL2019 SQL Express and IIS running on it.

If I use the private IP of the server 20.126.47.45 or it's name it can't connect, but if I use "localhost", it can validate connection.

When I deploy the project new folders are created and files within them

When I try to open installation on Chrome, it fails.

If I try it with IP-address, it thinks it is not safe to open it.

If I open the index.html manually from Explorer, it opens without problem. When I click the Dowload the Launcher, I get warning this might be dangerous (PROBLEM!) but I can open it and installation of CloudAppLaunchert succeeds, it is installed to users AppData/Roaming directory.

It also installs some of needed application files, but not the executable and ini files so the application can't be started.

 

All advices appreciated.

BR, Hannu

 

Accepted Answer
Francisco Martinez @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 4 July 2023 14:33 PM UTC
  2. PowerServer
  3. # Permalink

Hi Hannu,

 

Make sure that the PC has the ASP.NET Core Hosting Bundle installed, it's required for IIS to run ASP.NET Core applications.

 

Regards,
Francisco

Comment
  1. Logan Liu @Appeon
  2. Thursday, 6 July 2023 01:34 AM UTC
You will need to install the Web Deploy supporting tool on the Server if you want to deploy the PowerServer project to the remote IIS server from the PowerBuilder IDE. Refer to: https://docs.appeon.com/ps2022r2/Installing_Web_Deploy2.html

Regards, Logan
  1. Helpful
There are no comments made yet.
Hannu Pikkarainen Accepted Answer Pending Moderation
  1. Monday, 31 July 2023 09:29 AM UTC
  2. PowerServer
  3. # 1

Hi,

 

Actually this problem still exists.

If I deploy to local machine and use Configure IIS connection, server=localhost, Validate connection gives Success. But if I use server's name or IP, it fails.

On IIS's log I get :

#Software: Microsoft Internet Information Services 10.0
#Version: 1.0
#Date: 2023-07-31 06:15:14
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) cs(Referer) sc-status sc-substatus sc-win32-status time-taken
2023-07-31 06:15:14 fe80::ea8f:8706:adde:447d%28 HEAD /msdeploy.axd site=PowerServer%20Site 8172 - fe80::ea8f:8706:adde:447d%28 - - 404 7 0 1673

Same behavior when I try to deploys to production server.

Web deploy 4.0 is installed and Web Management Service is running on both machines.

BR, Hannu

 

 

Comment
  1. Francisco Martinez @Appeon
  2. Monday, 31 July 2023 14:44 PM UTC
The error suggests the computer is not accessible from where you're trying to deploy. Can you access this site through its IP address on the browser?

Is the Web Deploy port open on the server?
  1. Helpful
There are no comments made yet.
Hannu Pikkarainen Accepted Answer Pending Moderation
  1. Monday, 24 July 2023 14:16 PM UTC
  2. PowerServer
  3. # 2

Thanks Francisco, that was exactly what it needed.

BR, Hannu

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 3 July 2023 12:18 PM UTC
  2. PowerServer
  3. # 3

Hi Hannu;

  Before getting caught in all the runtime issues of using Azure, I would strongly suggest that you first get everything working on your local development PC running either W10 or W11. 

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.
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.