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

Resolved CloudApp Launcher Failed to Run

  1. Advice
0
Votes
Undo
  1. Danish Ahamed LiakathAli
    Danish Ahamed LiakathAli
  2. PowerBuilder
  3. Monday, 1 March 2021 20:33 PM UTC

After the Power Client build & deployment, when i run the CloudApp Launcer either from browser or manually, I am getting the below error.  I tried with my application and SalesDemo sample application. Deploying to localhost.

 

 

2021-03-01 15:06:36.027 ERROR [42740] Failed to get the app publisher from the server.
2021-03-01 15:06:36.027 ERROR [40448] Failed to download the file. URL: http://localhost:80/CloudAppPublisher/runtime/19.2.0.2670/manifest.json, Error description: HTTP error.(error code: 404).
2021-03-01 15:06:35.699 ERROR [40448] Failed to download the file. URL: http://localhost:80/CloudAppPublisher/CloudAppInstall/LauncherSetup.json, Error description: HTTP error.(error code: 404).
2021-03-01 15:06:35.561 INFO [37052] Application command line parameter:

 

After installing 2019 R3 as a Standard Edition user and later  Upgraded to CloudPro Edition.

I am little confused with Elevate Conference Video on the Automated App Deployment and the current PowerClient setup. In the video it says we need to do the PowerClient App publisher Do we still have that?

Does Appoen has any sample demo video with the new Power Client deployment process. 

 

 

 

 

  1. Deployment
  2. PowerClient
dot net wrapper
Cipher suite support in Powerbuilder 2019 R3
Who is viewing this page
Amjad Fahmawi
Responses (4)
Donald Clayton
Donald Clayton Accepted Answer Pending Moderation
  1. Monday, 11 April 2022 22:31 PM UTC
  2. PowerBuilder
  3. # 1

I found this issue recently and found that I needed to add a mime type to IIS to get the JSON to be served.  I think this is a problem a lot of folks are running into, so I'm posting our resolution for this issue:

 

If you use Microsoft Internet Information Services (IIS) as the web server and want to serve JSON, you must define the JSON MIME type for IIS  .

Procedure

  1. Open the Microsoft IIS management console.
  2. Select the local computer name.
  3. Click MIME Types.
  4. Click New or Add.
  5. In the Extension box, type .json.
  6. In the MIME Type box, type application/json.
You can validate this approach by trying to download the file in a browser:  http://localhost:80/CloudAppPublisher/runtime/19.2.0.2670/manifest.json 
 
Then, add the mime type and try again.  The telltale sign is the HTTP 404 response from the web server.
 
HTH,
 
Don Clayton
Intertech Consulting, Inc.
Attachments (1)
Capture.JPG Capture.JPG
Comment
There are no comments made yet.
Marco Meoni
Marco Meoni Accepted Answer Pending Moderation
  1. Tuesday, 2 March 2021 08:19 AM UTC
  2. PowerBuilder
  3. # 2

Hi Danish,

are you running on Windows 7 and IIS 7.5?

I reproduced your error there. The manifest.json doesn't have access rights.

If that's your environment, please upgrade to a system that is not EOL.

My 2 cents.

Best,

.m

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 2 March 2021 15:08 PM UTC
You are right Marco! His screenshot is Windows 7 dialog not Windows 10.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 2 March 2021 15:51 PM UTC
Hi Danish;

Note that starting in PB 2019 R3 and higher (aka PB 2021) - Appeon PB no longer supports W7.

Regards ... Chris
  1. Helpful
There are no comments made yet.
Danish Ahamed LiakathAli
Danish Ahamed LiakathAli Accepted Answer Pending Moderation
  1. Tuesday, 2 March 2021 00:20 AM UTC
  2. PowerBuilder
  3. # 3

I have followed the same steps for the SalesDemo App and still getting the same error. Did I missing something or need to check any other settings? 

Under the IIS Webroot folder , I do the see the CloudAppPublisher folder after I click 'Upload'  in  Deployment Tab and after Build and Deploy the project the salesdemo_asa folder created. 

 

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 2 March 2021 01:09 AM UTC
Inside the CloudAppPublisher folder to you see the Cloud App Launcher installer? If yes, then it could be IIS config issue.
  1. Helpful
Kai Zhao @Appeon
  1. Kai Zhao @Appeon
  2. Tuesday, 2 March 2021 06:59 AM UTC
Hi Danish,



There are two launcher types below for Cloud App Launcher:

Launcher without background service

Launcher with background service



Please make sure you have uploaded the launcher (on step 6 in the article below) that matches with the default startup mode on step7. It’s suggested that you select 'Default_Both_WithServiceSingle' on step 6.

https://docs.appeon.com/pb2019r3/pbug/ch07s03.html#tutorial_deploying_your_first_PowerClient_project



This issue is also possibly caused by browser cache. Please try clearing the cache or using other browsers.



Regards,

ZhaoKai

  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Monday, 1 March 2021 20:46 PM UTC
  2. PowerBuilder
  3. # 4

Hi Danish,

In the beta version this was called PowerClient App Publisher. In the final release, we renamed it to Cloud App Launcher.

Check your IIS Webroot and see that there is a folder called "CloudAppPublisher" and that in the folder is the Cloud App Launcher installer.  If it doesn't exist, you need to deploy the Cloud App Launcher to your IIS server, which is performed inside the "Deployment" tab of your PowerClient project file.  

I recommend before you deploy your own app, you first successfully complete this tutorial: https://docs.appeon.com/pb2019r3/pbug/ch07s03.html#tutorial_deploying_your_first_PowerClient_project

Best regards,
Armeen

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.