Web Farm with IIS10 Servers | Content Server: HTTP Error 500.0 - ASP.NET Core IIS hosting failure (in-process)

Question

Web Farm with IIS10 Servers | Content Server: HTTP Error 500.0 - ASP.NET Core IIS hosting failure (in-process)

Nasheayahu 40

My goal was to put all ASP.NET core content on a Content Server and found "Build a Web Farm with IIS Servers" learning document showing how to do this, but I've ran into a problem. I'm running 5 KVM Windows 2019 Essential VMs (ARR, Content, Certificate, Web1, Web2) Servers.

Testing the Blazor App on Web1 I get the,

Browser: HTTP Error 500.0 - ASP.NET Core IIS hosting failure (in-process)

and viewing the Windows Logs | Application

Failed to start application '/LM/W3SVC/1/ROOT', ErrorCode '0x8007023e'.
Application '\CONTENTSERVER\wwwroot\kohanyim' failed to start. Exception message: Unexpected exception: status: Access is denied.: "\CONTENTSERVER\wwwroot\kohanyim\dotnet.exe"

I thought this would have taking care of that:

cd %windir%\Microsoft.NET\Framework64\v4.0.30319
caspol -m -ag 1. -url file://CONTENTSERVER/wwwroot/kohanyim/* FullTrust

So, how do I correct this?

UPDATE: web.conf

<configuration>
  <location path="." inheritInChildApplications="false">
    <system.webServer>
      <handlers>
        <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
      </handlers>
      <aspNetCore processPath="dotnet" arguments=".\BlazorAppKohanyim.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" hostingModel="inprocess" />
    </system.webServer>
  </location>
</configuration>

Lex Li 6,037 Reputation points

2023-10-31T03:11:43.1966667+00:00

The error message indicates something wrong in web.config, so you need to edit the question to include its contents. The call to caspol is irrelevant, as ASP.NET Core isn't ASP.NET 4.x.
Anonymous

2023-10-31T08:49:58.82+00:00

Could you tell me how do you set up the file server? (Such as the OS and relevant protocol ). When troubleshooting with the "Access denied“ error, you could use "process monitor". It will capture every file access event with user and the target file details. https://learn.microsoft.com/en-us/sysinternals/downloads/procmon . I suggest you check if the user is the right one which have proper permission. Another thing you could try is set the IIS application pool identify to "Local Machine" to see if it works.
Nasheayahu 40 Reputation points

2023-10-31T16:23:31.25+00:00

@Lex Li (Microsoft) the web.conf has been added...

Its a Windows 2019 Server Essential cloned from my ARR Windows 2019 Server with the II10 removed, made no additional changes and all the dependencies remaining:

I'm using the same inetpub folder, but published the app to:

here is the dotnet information:

I was able to run the app on this server in a browser:

Okay, I will read the link and make the suggested changes and get back with you.....
Nasheayahu 40 Reputation points

2023-10-31T16:35:44.11+00:00
What app do I run?

file:///run/media/Downloads/Procmon.exe

file:///run/media/Downloads/Procmon64.exe

file:///run/media/Downloads/Procmon64a.exe

Cancel this posting, anyone of them worked.....
Nasheayahu 40 Reputation points

2023-10-31T18:33:37.4733333+00:00
In Addition:

On the Web1,2 Servers I configured:

Advance Settings

and Shared Configuration

and on the Web1 Server as the administrator I can not browse the app, but on the Content Server I execute dotnet apt.dll successfully.

Also this is the VS published net7.0 folder

and the Publisher folder content copied to the Web1 Shared folder:
Anonymous

2023-11-02T08:14:39.01+00:00

Procmon for 32bit. Procmon64 for 64bit system. Procmon64A for AMD CPU. Genereally we use Procmon64. You could to find the access error event from capturing.
Anonymous

2023-11-02T08:34:59.59+00:00

You could try run Procmon on both local server and content server the capture the event.

Your answer

Lex Li 6,037 Reputation points

2023-10-31T03:11:43.1966667+00:00

The error message indicates something wrong in web.config, so you need to edit the question to include its contents. The call to caspol is irrelevant, as ASP.NET Core isn't ASP.NET 4.x.
Anonymous

2023-10-31T08:49:58.82+00:00

Could you tell me how do you set up the file server? (Such as the OS and relevant protocol ). When troubleshooting with the "Access denied“ error, you could use "process monitor". It will capture every file access event with user and the target file details. https://learn.microsoft.com/en-us/sysinternals/downloads/procmon . I suggest you check if the user is the right one which have proper permission. Another thing you could try is set the IIS application pool identify to "Local Machine" to see if it works.
Nasheayahu 40 Reputation points

2023-10-31T16:23:31.25+00:00

@Lex Li (Microsoft) the web.conf has been added...

Its a Windows 2019 Server Essential cloned from my ARR Windows 2019 Server with the II10 removed, made no additional changes and all the dependencies remaining:

I'm using the same inetpub folder, but published the app to:

here is the dotnet information:

I was able to run the app on this server in a browser:

Okay, I will read the link and make the suggested changes and get back with you.....
Nasheayahu 40 Reputation points

2023-10-31T16:35:44.11+00:00

What app do I run?

file:///run/media/Downloads/Procmon.exe

file:///run/media/Downloads/Procmon64.exe

file:///run/media/Downloads/Procmon64a.exe

Cancel this posting, anyone of them worked.....
Nasheayahu 40 Reputation points

2023-10-31T18:33:37.4733333+00:00

In Addition:

On the Web1,2 Servers I configured:

Advance Settings

and Shared Configuration

and on the Web1 Server as the administrator I can not browse the app, but on the Content Server I execute dotnet apt.dll successfully.

Also this is the VS published net7.0 folder

and the Publisher folder content copied to the Web1 Shared folder:
Anonymous

2023-11-02T08:14:39.01+00:00

Procmon for 32bit. Procmon64 for 64bit system. Procmon64A for AMD CPU. Genereally we use Procmon64. You could to find the access error event from capturing.
Anonymous

2023-11-02T08:34:59.59+00:00

You could try run Procmon on both local server and content server the capture the event.

Share via

Web Farm with IIS10 Servers | Content Server: HTTP Error 500.0 - ASP.NET Core IIS hosting failure (in-process)

Your answer