• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerServer
  • Problem with running application with PowerServer 2022 R2

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

Resolved Problem with running application with PowerServer 2022 R2

  1. Issue
0
Votes
Undo
  1. Hannu Pikkarainen
    Hannu Pikkarainen
  2. PowerServer
  3. Monday, 24 July 2023 15:31 PM UTC

Hi,

I'm trying to deploy my first application with PowerServer 2022 R2 Build 2693. 

Deploying to IIS goes through without errors.

When I try to Run Project, I get errors:

2023-07-24 14:08:04.115 ERROR [1524] Failed to parse the app URL(http://dev.honeyplan.fi/CostGrinderDev).
2023-07-24 14:08:04.115 ERROR [1524] Failed to download the config file http://dev.honeyplan.fi:80/CostGrinderDev/apprun.json; ErrorCode: 503; Error: Application Shutting Down.
2023-07-24 14:08:04.079 INFO [1524] The app root path: C:\Users\honeyplan\AppData\Roaming\PBApps\Applications.
2023-07-24 14:08:04.079 INFO [1524] Application name: CostGrinderDev.
2023-07-24 14:08:04.079 INFO [1524] Application server port: 80.
2023-07-24 14:08:04.079 INFO [1524] Application host name: dev.honeyplan.fi.
2023-07-24 14:08:04.079 INFO [1524] Application protocol: http.
2023-07-24 14:08:04.079 INFO [1524] Application URL: http://dev.honeyplan.fi:80/CostGrinderDev.
2023-07-24 14:08:04.078 INFO [1524] The app is now being updated.

I have tried to use path localhost, same errors.

In some documentations I see that there should be also a AppeonAppPool, is this correct? I don't have it.

Also should I have NET 6.0 on IIS since in PB Web APIs Target framework is 6.0?

 

BR, Hannu

 

 

PowerServer Versioning
Problems with deploying Power Server application
Accepted Answer
Logan Liu @Appeon
Logan Liu @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 26 July 2023 07:26 AM UTC
  2. PowerServer
  3. # Permalink

Hi Hannu,

After trying to access the URL (http://dev.honeyplan.fi:80/CostGrinderDev/apprun.json) from the browser, I can see the 500.32 error.

The most common cause for this IIS related error is that the Web API is published for an incompatible processor architecture. For example,

The IIS worker process is running as a 64-bit app while the Web API was published to target 32-bit; or

The IIS worker process is running as a 32-bit app while the Web API was published to target 64-bit.

You can learn more from "HTTP Error 500.32 - Failed to load .NET Core host" error - - PowerServer 2022 R2 Help (appeon.com)

Regards, Logan

Comment
There are no comments made yet.
Responses (5)
Hannu Pikkarainen
Hannu Pikkarainen Accepted Answer Pending Moderation
  1. Thursday, 27 July 2023 16:39 PM UTC
  2. PowerServer
  3. # 1

Hi Francisco,

That file exists in several directories in local computer (same as destination server)

 

BR, Hannu

Comment
There are no comments made yet.
Hannu Pikkarainen
Hannu Pikkarainen Accepted Answer Pending Moderation
  1. Wednesday, 26 July 2023 15:36 PM UTC
  2. PowerServer
  3. # 2

Hi Francisco and Logan,

Your advices were 100% correct and helped me forward, Thank You very much.

I still have some problems that I can't figure out.

If I select Target run mode External (IIS), it fails to deploy it to IIS.

Failed to publish the installable cloud app.

 

---------- Deploy: Deploy of CostGrinderDev (15:28:10)
Checking the configuration information for the publishing...
"C:\Program Files (x86)\Appeon\Common\PSToolkit\22.0\NetBuild\NetBuild.dll" -wt:Solution -wp:SolutionDirectory="C:\Users\honeyplan\source\repos\PowerServer_Cost_allocation_test" -wp:Type="CheckVersion"
Creating executable file . . .
Inspecting Application Dependencies...
.....
Successfully execute msdeploy.exe.
Publish Succeeded.
1>Done Building Project "C:\Users\honeyplan\AppData\Local\Temp\pbappscache 22.0\ServerAPIs\ServerAPIs.csproj" (Publish target(s)).
Build succeeded.
"C:\Users\honeyplan\AppData\Local\Temp\pbappscache 22.0\ServerAPIs\ServerAPIs.csproj" (Publish target) (1) ->
(MSDeployPublish target) ->
MSDEPLOY : warning : An error was encountered when processing operation 'Create File' on 'ServerAPIs.dll'. [C:\Users\honeyplan\AppData\Local\Temp\pbappscache 22.0\ServerAPIs\ServerAPIs.csproj]
MSDEPLOY : warning : An error was encountered when processing operation 'Create File' on 'ServerAPIs.dll'. [C:\Users\honeyplan\AppData\Local\Temp\pbappscache 22.0\ServerAPIs\ServerAPIs.csproj]
2 Warning(s)
0 Error(s)
Time Elapsed 00:00:06.77
Failed to publish the installable cloud app.
---------- Finished Deploy of CostGrinderDev (15:29:06)
Error(s) occurred during the deployment. For more information, see above messages.

It creates successfully that directory, copies everything else but not that single file.

 

BR, Hannu

Comment
Load more comments
Hannu Pikkarainen
  1. Hannu Pikkarainen
  2. Friday, 28 July 2023 11:56 AM UTC
Suddenly running project in IDE mode started to work without problems. I have no idea why...

Project deployed to IIS has still the same problems.



BR, Hannu

  1. Helpful
Francisco Martinez @Appeon
  1. Francisco Martinez @Appeon
  2. Friday, 28 July 2023 15:06 PM UTC
Hi Hannu,

Have you tried running the project from IIS despite the warnings?
  1. Helpful
Hannu Pikkarainen
  1. Hannu Pikkarainen
  2. Monday, 31 July 2023 09:05 AM UTC
Hi Francisco,



Now the deploying sometimes succeeds, most of the time not. When failing, it does not copy CloudAppPublisher to IIS. But once the CloudAppPublisher has been successfully copied updates to the application itself are succesfully copied to IIS and to the client PC.



BR, Hannu
  1. Helpful
There are no comments made yet.
Hannu Pikkarainen
Hannu Pikkarainen Accepted Answer Pending Moderation
  1. Tuesday, 25 July 2023 15:04 PM UTC
  2. PowerServer
  3. # 3

Hi Francisco,

I already had .Net 6.0 installed, but I installed again. I changed the  .NET CLR version to No Managed Code. Still same errors.

Should I have the AppeonAppPool in IIS? When should it be created?

 

BR, Hannu

 

Comment
Load more comments
Hannu Pikkarainen
  1. Hannu Pikkarainen
  2. Tuesday, 25 July 2023 16:49 PM UTC
Should I create that Application Pool dedicated for the Web APIs manually by myself or should it appear automatically in some phase?
  1. Helpful
Hannu Pikkarainen
  1. Hannu Pikkarainen
  2. Tuesday, 25 July 2023 16:50 PM UTC
I have installed this : https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-aspnetcore-7.0.9-windows-hosting-bundle-installer

  1. Helpful
Francisco Martinez @Appeon
  1. Francisco Martinez @Appeon
  2. Tuesday, 25 July 2023 17:24 PM UTC
It should have been automatically created by IIS when you created the "PowerServer Site". You might have selected a different application pool when creating it. You can recreate the web site and make sure a new Application Pool is created, or just create a new application pool with its CLR Version set to No Managed Code, and then set this pool as the Web Site's app pool, either will result in the same
  1. Helpful 1
There are no comments made yet.
Francisco Martinez @Appeon
Francisco Martinez @Appeon Accepted Answer Pending Moderation
  1. Monday, 24 July 2023 15:45 PM UTC
  2. PowerServer
  3. # 4

Hi Hannu,

 

Yes, you must have the .NET Runtime installed in the server where you're deploying the Web APIs. You need to have the ASP.NET Core Hosting Bundle (which includes the .NET Runtime) to enable your IIS instance to run ASP.NET Core applications.

 

Hope this helps.

 

Regards,
Francisco

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.