1. Lemuel Bacli
  2. PowerBuilder
  3. Wednesday, 23 May 2018 05:47 AM UTC

Hi,

Im trying the Appeon pb2017 r2 and i've migrated one of my pb12.5 app to this. The migration worked and now im trying to deploy it on the web. Now when im trying to use the powerserver toolkit config wizard, im stucked at Failed to Connect to Powerserver 'Local PowerServer'! Please verify that powerserver is running. On the installation, i believed it was integrated to my local IIS and i can see it on my website application. 

What could be the reason why the powerserver is not running? Do i need to activate it myself? plus, when im access the AEM in my IIS, the IE throws a 500.21 error namely: 

HTTP Error 500.21 - Internal Server Error

Handler "ExtensionlessUrlHandler-ISAPI-4.0_64bit" has a bad module "IsapiModule" in its module list

 

Im Fairly new to powebuilder and also the appeon. i hope someone could help me..

 

thanks!

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 24 May 2018 13:45 PM UTC
  2. PowerBuilder
  3. # 1

HI Lemuel;

  Have you watched the PowerServer Web & Mobile Tutorial videos?

HTH

Regards ... Chris

Comment
  1. Lemuel Bacli
  2. Friday, 25 May 2018 06:25 AM UTC
Hi Chris,



I have watched them all and now im reviewing it again if ever i have missed something. I followed every step in the video but still, when im testing my connection to my local powerserver it says

Error 2004: The Formart returned from powerserver is incorrect

Error 2012: Cannot connect to PowerServer 'localhost'



i have applied the maintenance patch for powerserver so the version of my powerserver and and powerserver toolkit has the same version. Actually ever the powerserver help and powerserver web component has the same version...



what i cant resolve and understand is the why i cant connect to my local server? does the firewall if Symantec has something to do with this? The firewall is managed by Symantec and i have to make a request to include it on the exceptions. 



I really need to make this work. Im using the trial version. Thanks

  1. Helpful
There are no comments made yet.
Mark Lee @Appeon Accepted Answer Pending Moderation
  1. Thursday, 24 May 2018 03:37 AM UTC
  2. PowerBuilder
  3. # 2

Please refer to the following link and see if can resolve your problem.

http://www.brandonmartinez.com/2014/07/02/resolve-an-http-error-500-21-in-iis/

Or you can try the below and see if it can fix the problem.

  • 1. Go to Windows Control Panel.
    2. Click on Programs.
    3. Go to Programs and Features.
    4. Select Microsoft .NET Framework 4 Extended and double-click it.
    5. Click the Repair .Net Framework.
    6. Click Finish
  • 7. You will be pompted to restart.

Regards,

Mark Lee

Comment
  1. Lemuel Bacli
  2. Friday, 25 May 2018 02:19 AM UTC
Hi Mark,



Upon Checking, all i have is .net 3.5 and 4.6.. should i download the .net 4.0?

  1. Helpful
There are no comments made yet.
Govinda Lopez @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 23 May 2018 15:23 PM UTC
  2. PowerBuilder
  3. # 3

Hi Lemuel,

 

I believe this could be caused by an improper configuration of your IIS. You might be be missing some Windows Features (see image below). You can follow the instructions on this manual to get your IIS properly configured (as well as your PowerServer).

Another thing is that PowerServer Mobile PB Edition (the one that comes included with PowerBuilder Universal Edition) is not meant for Web deployments. For that, you require another edition of PowerServer (see here).

 

I hope this helps.

 

 

Regards,

Comment
  1. Lemuel Bacli
  2. Thursday, 24 May 2018 02:29 AM UTC
Hi,



I have made this working through changing the Managed Pipeline Mode. By Default it is set to classic and i changed it to Integrated... Now I can access the AEM and still the powerserver is turned off... Does it needed to be activated first so that it would work? 

  1. Helpful
There are no comments made yet.
Marco Meoni Accepted Answer Pending Moderation
  1. Wednesday, 23 May 2018 08:03 AM UTC
  2. PowerBuilder
  3. # 4

Hi Lemuel,
The error sounds like extensions are not properly registered on your IIS box but let's do the mandatory pre-requisites checks first: 

1) Is MS IIS up and running? (i.e. open the browser and navigate to http://localhost)
2) Is PowerServer correctly installed? (i.e. navigate to http://localhost/AEM)

Best,

Marco

Comment
  1. Lemuel Bacli
  2. Thursday, 24 May 2018 02:31 AM UTC
I have not meddled with anything while the PowerBuilder 2017 R2 is installing. I just click next and choose the appropriate things to be installed so i guess i have correctly installed the PowerServer... Do i need to activate the license of PowerServer to make it running?



Another question, i can activate the trial license of my Powerserver through AEM. Im following the instruction written but still it does nothing. 

  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.