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

Resolved Deploy Application to Web

  1. How-to
0
Votes
Undo
  1. CJ Lai
    CJ Lai
  2. PowerServer 2020 or older (Obsolete)
  3. Thursday, 18 June 2020 17:11 PM UTC

Hi

I have done the following to migrate an application to our company's web server to be run as a web application. By the way, the application runs as a web app on my local computer well.

- I have PowerServer (the same version as that on my local computer) installed on the web server's localhost:port#

- I can bring up the AEM by using localhost:port#/AEM

- Packaged the application in PB w/ Powerserver's toolkit 'Package' icon and chose 'Server deployment project' Type

- Copy and pasted the package folder to the web server via RDP

- Ran the Setup.exe as the admin

- Edited the Power and Web Servers to the correct port# then modified the rest accordingly.

- PowerServer deployed it successfully

BUT, when I ran the app after it's successfully done deploying, I got an error page

 

HTTP Error 403.14 - Forbidden

The Web server is configured to not list the contents of this directory....

 

Where did I do wrong?

 

Please help

Thanks!

List of compatible fonts?
PowerServer IIS Defult Doc vs Directory Browsing
Accepted Answer
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 18 June 2020 18:59 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # Permalink

Hi CJ, For sure this is an IIS config issue not Appeon product issue.  Please try these steps to see if it resolves: https://docs.appeon.com/appeon_online_help/ps2020/web_server_configuration_guide/Configuring_Windows_IIS_with_NET.html

Comment
Load more comments
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 19 June 2020 17:21 PM UTC
Try running the installation of the optional PowerServer Web Server component to the wwwroot folder. I think that will add this missing folder.
  1. Helpful
CJ Lai
  1. CJ Lai
  2. Friday, 19 June 2020 18:11 PM UTC
You are spot-on! It did restore the IISSupport folder. However, after following the configuration doc you provided, I still get the page can not be displayed error page
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Friday, 19 June 2020 19:51 PM UTC
There is some other IIS configuration issue. The document outlines specific requirements for PowerServer that by default are not enabled rather than comprehensive guide how to properly configure IIS for remote access.
  1. Helpful
There are no comments made yet.
Responses (2)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 18 June 2020 17:25 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi CJ;

  Sounds like an IIS permissions issue. When you installed the Web App to the production PowerServer, did you install it under the II's folder structure (not program files)? For example: C:\inetpub\wwwroot. If you installed it in another folder structure, then you may need to give that folder "IIS_IUSRS" security permission. The same might also be true for the "WWWROOT" folder if this is a new IIS installation.

HTH

Regards ... Chris

Comment
CJ Lai
  1. CJ Lai
  2. Thursday, 18 June 2020 17:30 PM UTC
Thank yoiu, Chris but the IIS had been installed on the server before my deployment. The IIS folder structure/folder wwwroot has the Full control granted to IIS_IUSRS.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 18 June 2020 19:35 PM UTC
Assuming then that you placed your Web App under "wwwroot" folder, then it could be a port issue. Please make sure that you use the URL: http://<your PS Server>:<port>/<AppName> to invoke the App. Also, please check your IIS console to make sure that your App is known to IIS and that it's assigned to the proper Application Pool.
  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.