Select Page
This entry has been published on 2017-03-14 and may be out of date.

Last Updated on 2017-03-14.



You try to publish your ASP.NET Core site to another Windows server running IIS.

Error messages:

Event 1000 / IIS AspNetCore Module: Application ‘MACHINE/WEBROOT/APPHOST/DEFAULT WEB SITE’ with physical root ‘C:\inetpub\wwwroot\’ failed to start process with commandline ‘”dotnet” .\yourproject.dll’, ErrorCode = ‘0x80004005 : 80008083.

Event 1004/ IIS AspNetCore Module: Warning: Could not create stdoutLogFile \\?\C:\inetpub\wwwroot\logs\stdout_4460_201731417238.log, ErrorCode = -2147024893.


To get a better error description, first correct the 1004 error, i.e. create a directory C:\inetpub\wwwroot\logs and set write permissions.

Afterwards, reload the site and open the logfile there. In my case, it showed this error:

The specified framework ‘Microsoft.NETCore.App’, version ‘1.1.1’ was not found.

– Check application dependencies and target a framework version installed at:

C:\Program Files\dotnet\shared\Microsoft.NETCore.App

– The following versions are installed:



– Alternatively, install the framework version ‘1.1.1’.

In fact, local Visual Studio 2017 RC had been upgraded to 2017 RTM and the framework version of the project was also upgraded.

So basically, before you deploy/publish your project make sure your remote server runs exactly the same version of “.NET Core Windows Server Hosting”.

You get the latest packages here.

E.g. if your remote IIS server was already configured before you upgraded anything, simply uninstall the previous .NET Core Runtime(s) via Programs & Features, then install the latest .NET Core Runtime x.x.x, to be exact the “Windows Server Hosting (x64 & x86)” package.[:]