Minimal API service deployed to IIS does not work

Question

Minimal API service deployed to IIS does not work

Dmitriy Reznik 241

I have a minimal api service deployed to IIS using Azure DevOps pipeline. As the service does not work as expected (500 - Internal server error), I checked the IIS. I see that app settings cannot be read. IIS can see only the automatically generated web.config:
User's image

But our actual app settings are in the appsettings.json file. How can I fix this?

The same issue happens if I deploy manually, without Azure pipeline.
I cannot open failed request tracing, as well as other items on IIS for that particular website:

User's image

Answer accepted by question author

2 additional answers

Your answer

Answer 1

Lex Li 6,037

web.config is commonly used to configure IIS, so even if you are not using ASP.NET 4.x you need it when deploying ASP.NET Core bits. For example, ASP.NET Core module settings are necessary.

"I see that app settings cannot be read" is desired. IIS Manager only integrates with ASP.NET 4.x settings, no more with ASP.NET Core.

The other errors you reported indicate you didn't install ASP.NET Core module yet. Install the hosting bundle from a download page like https://dotnet.microsoft.com/en-us/download/dotnet/6.0 and you are good to go next.

Dmitriy Reznik 241 Reputation points

2023-08-31T12:11:30.65+00:00

Thank you for your answer. But I do have .NET 7 installed on the VM...
Lex Li 6,037 Reputation points

2023-08-31T16:25:45.61+00:00

Runtime, SDK, and hosting bundle are three different pieces. What you missed is the hosting bundle.

Answer 2

Bruce (SqlWork.com) 82,146 Volunteer Moderator

with min api (.net core) app, the web.config is used to configure the asp.net core hosting module, that loads and runs an asp.net core app in IIS. did you install?

https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/hosting-bundle?view=aspnetcore-7.0

Dmitriy Reznik 241 Reputation points

2023-08-31T21:22:56.95+00:00

I marked another answer, as it came earlier, but I do appreciate your response. Thank you!

Answer 3

Solace 0

This indicates that your web.config includes something that the version of IIS doesn't understand.

Try to comment out all the contents of the web.config file and ensure that the error clears, then slowly reintroduce parts to determine what is causing the problem.

Is this doesn't work, ensure that the <aspNetCore>is in the web.config file. You may need to reference if you need to install it. https://learn.microsoft.com/en-us/aspnet/core/fundamentals/servers/aspnet-core-module?tabs=aspnetcore2x

Dmitriy Reznik 241

All I have in my web.config is this:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <location path="." inheritInChildApplications="false">
    <system.webServer>
      <handlers>
        <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />
      </handlers>
      <aspNetCore processPath="dotnet" arguments=".\JdeProductDataApi.dll" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" hostingModel="inprocess" />
    </system.webServer>
  </location>
</configuration>

So I don't see what I could remove here. And <aspNetCore> is there...

Share via

Minimal API service deployed to IIS does not work

2 additional answers

Your answer