CODEWITHSUNDEEP
asp.net-coreiis.net-corehttp-errorout-of-process
Hugo Debrand
Hugo Debrand

Reputation: 11

HTTP Error 502.5 - ANCM Out-Of-Process Startup Failure Application Xbap

Recently I have had this problem that comes up often but I don't understand the reason for it.

With IIS I have my web site with my api and when I call them I get an answer but I added an application to my web site and this one sends me this error.

My api are in: C:\inetpub\wwroot\V4_1\

And the Xbap application can be found in: C:\Content\AppliWindows\Xbap\

Some of the servers I use with the same files don't have this problem.

Web.config :

<?xml version="1.0" encoding="utf-8"?>
<configuration>
   <system.webServer>
    <handlers>
      <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
    </handlers>
    <aspNetCore processPath=".\Spec.Locbus.V4.Services.FrontEnd.exe" arguments="" requestTimeout="00:20:00" stdoutLogEnabled="false" forwardWindowsAuthToken="false" stdoutLogFile=".\logs\stdout">
      <environmentVariables />
    </aspNetCore>
  </system.webServer>
</configuration>
<!--ProjectGuid: 821a3cf1-7c3b-4e36-8868-69fd8b417331-->

In Windows event log I get this error but it doesn't give me any more information:

Application '/LM/W3SVC/2/ROOT/content' with physical root 'C:\content' failed to start process with commandline '.\Spec.Locbus.V4.Services.FrontEnd.exe ' with multiple retries. Failed to bind to port '7993'. First 30KB characters of captured stdout and stderr logs from multiple retries:

I know I get the same error when I try to call my api and I didn't install net.core2.2.8 but I installed it correctly and my api works.

The server I'm on is running Windows2019.

Asp.NET diagnostics seems to be good except for 2.2.8 at end of life :

System Time: 17/11/2020 15:57:29
Processor Architecture: AMD64
OS: Microsoft Windows NT 10.0.17763.0

Server Type: IIS
Scan 32 installed module(s).
ASP.NET Core module version 2 is installed for .NET Core 2.2 and above: C:\Program Files\IIS\Asp.Net Core Module\V2\aspnetcorev2.dll (13.1.20295.10).

Scan 45 registered handler(s).
Found a valid ASP.NET Core handler as { Name: aspNetCore, Path: *, State: Enabled, Module: AspNetCoreModuleV2, Entry Type: Local }.
Visual C++ runtime is detected (expected: 14.0, detected: 14.28.29325.2 built by: vcwrkspc): C:\Windows\system32\msvcp140.dll.
The application pool 'LocbusV4' is used.
Pool identity is IIS AppPool\LocbusV4
Please ensure pool identity has read access to the content folder C:\inetpub\wwwroot\V4_1.
Pool bitness is 64 bit
Scan aspNetCore section.
    "processPath": .\Spec.Locbus.V4.Services.FrontEnd.exe.
    "arguments": .
    "hostingModel": .
"runtimeTarget": .NETCoreApp,Version=v2.2/win-x64.
Runtime is Microsoft.AspNetCore.All/2.2.8.
.NET Core version 2.2.8 is end-of-life. Please upgrade to a supported version.
Runtime 2.2.8 requires ASP.NET Core module version 12.2.19109.5. Installed version 13.1.20295.10 might not be compatible.
Please refer to pages such as https://dotnet.microsoft.com/download/dotnet-core/3.1 to verify that ASP.NET Core version 13.1.20295.10 matches the runtime of the web app.

Has anyone ever had this problem and has a solution?

Thank you in advance.

Upvotes: 0

Views: 4111

Answers (1)

Hugo Debrand
Hugo Debrand

Reputation: 11

I finally succeeded in creating a second site by creating the sub-application in this one and with URL rewriting redirecting the calls intended for the application from site 1 to the site of the app.

Upvotes: 1

Related Questions