1. CJ Lai
  2. PowerServer 2020 or older (Obsolete)
  3. Friday, 19 June 2020 18:40 PM UTC

Hi

I am in the mid of configuring PowerServer Application Deployment -> Server Settings and stuck on the Power Server settings.

After I put in the Server Name and Port Number for HTTP and Test it, it errored out. 

"Failed to connect to PowerServer 'Profile Name'! Pleaseverify that the settings are correct...."

 

I have 2x checked the Server Name (I used IP) and port# many times. For the life of me, I can't figure out where went wrong.

 

Should I enable Directory Browsing? Should I assign a Default Document? If so, how?

 

Accepted Answer
CJ Lai Accepted Answer Pending Moderation
  1. Monday, 22 June 2020 18:53 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # Permalink

I had to reverse what I was suggested to follow -> https://bit.ly/2Ym89UQ (ps. some file locations in that article are Different from what's on my PC but I was able to locate them at the end)

Now I can see <IPAddress>:portnumber/AEM page and the app is working fine.

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 19 June 2020 19:05 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi CJ;

  No, Directory Browsing is not normally turned ON as its a security feature that is better left OFF.

  Does IIS respond in the web browser with a simple:  http://<ipaddress>:port   URL?

In my case ... http://localhost:80 or  http://129.168.1.2:80

Regards ... Chris

Comment
  1. CJ Lai
  2. Friday, 19 June 2020 19:49 PM UTC
I still can't open the default page even when ON the server itself.
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Friday, 19 June 2020 19:50 PM UTC
Can you access http://ipaddress:port/aem using a Web browser. The IP address would be your remote server and the Web browser needs to be on your own machine where PowerBuilder is installed.

If you cannot access the AEM page through your Web browser, then your IIS is not configured correctly and that is why it is failing.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Friday, 19 June 2020 19:52 PM UTC
Yes, a Ping is not the same as an HTTP request as the block could be from a network segment, firewall to firewall and/or port setting not letting you through. Try the local browser on the IIS machine. If that works, then you know that its probably either a networking, firewall or proxy issue.
  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.