ASP.NET Core site not running on IIS, works fine from commandline

Question

I'm building a new web application with ASP.NET Core, and have it running nicely in debug in Visual Studio.

I've added Serilog, using the rolling file sink, and that's working nicely too, from Visual Studio.

Then I've published the app (both directly from VS, but also using AppVeyor), and I've copied it to my web-server, added a site in the IIS etc.

Now I'm getting "500 - Internal server error.".

No logs are written to the filesystem, not even the stdout files. I've added the folders, I've added write permissions for the IIS_IUSRS account and the app pool account.

Still no logs!

Trying to run the site from the commandline works just fine, and logging with Serilog works.

So this has to do with the IIS somehow? But without any logs, it's hard to know what the problem is. Any ideas?

Bonus info:

I've installed the dotnet-sdk-2.1.200-win-x64 package on the server.

The web.config file:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <system.webServer>
    <handlers>
      <add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" />
    </handlers>
    <aspNetCore processPath="dotnet" arguments=".\MySite.dll" stdoutLogEnabled="true" stdoutLogFile=".\app_data\stdout" />
  </system.webServer>
</configuration>
<!--ProjectGuid: B9DE9F34-1A9E-4D35-B6CE-74209A6CB9FA-->

Permissions on the site's root folder (same for app pool user):

app_data permissions (below are the logs and stdout folders), same for both users:

Update

I've just installed the AspNetCore.2.0.7.RuntimePackageStore_x64 and dotnet-runtime-2.0.7-win-x64 but it's still not working.

it may help you https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/development-time-iis-support?view=aspnetcore-2.0 — ArunPratap, May 30 '18 at 06:24
Last time I had this it was filesystem permission issue. Do recheck that the app pool user can definitely access the files. That’s one main case when no logs are written anywhere. — Sami Kuhmonen, May 30 '18 at 06:26
Nothing in the event log, unless I'm looking the wrong place. Where should it be? In Systems I'm just getting a warning from the IIS-APPHOSTSVC about some history folder. — Steen Tøttrup, May 30 '18 at 06:35

mark333...333...333 · Answer 1 · 2018-05-30T09:15:29.377

0

I've experienced this similar error as well, but I've found out that I need an updated Dotnet SDK Runtime Installer version 2.0.6+

You can find it here (.NET Core Runtime 2.0.6 Download Page)

Restart your server after the installation.

I hope this helps you.

edited May 30 '18 at 09:15

answered May 30 '18 at 07:28

mark333...333...333

1,270
1
11
26

I've installed both the dotnet-runtime-2.0.7-win-x64 and AspNetCore.2.0.7.RuntimePackageStore_x64 packages, still not working. I wouldn't need the SDK on a server for hosting, right? – Steen Tøttrup May 30 '18 at 08:06
If this was the problem, would the web app run from commandline on the server? – Steen Tøttrup May 30 '18 at 08:09
Try to restart your server after the installation. – mark333...333...333 May 30 '18 at 08:45
You have to create a site on IIS and in your application pool, choose "NoManagedCode" – mark333...333...333 May 30 '18 at 08:46
As I've already written in the question, I've create a site etc. – Steen Tøttrup May 30 '18 at 08:57

score 0 · Answer 2 · answered May 30 '18 at 08:58

0

It ended up being the 'Hosting Bundle Installer' I was missing, it was not enough with the other mentioned packages. Installing the latest one, 2.0.8, and restarting did the trick.

Now Serilog is also logging.

answered May 30 '18 at 08:58

Steen Tøttrup

3,755
2
22
36

That's what I'm talking about. It's part of the .NET Core Runtime :/ – mark333...333...333 May 30 '18 at 09:12

ASP.NET Core site not running on IIS, works fine from commandline

2 Answers2