Http IIS 502.5 Error after migrating from ASP.NET Core 1.0 to 1.1

Steps to reproduce

I used these official ASP.NET Articles and to upgrade my ASP.NET Core 1.0 app to 1.1. The app compiles fine but when I run the app using F5, I get the following error

The issue

Common causes of this issue:

The application process failed to start
The application process started but then stopped
The application process started but failed to listen on the configured port

NOTE: My app is on development machine(windows 10) running on default built-in IIS express. No server or migration to a different sever is involved.

Windows Event Log:

Failed to start process with commandline '"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Web Tools\ProjectSystem\VSIISExeLauncher.exe" -p "C:\Program Files\dotnet\dotnet.exe" -a "C:\DotNet2015\src\ABCTest\bin\Debug\netcoreapp1.1\ABCTest.dll" -wd "C:\DotNet2015\src\ABCTest" -wbe Global\Build30603dd4-5933-4547-8aff-af488d42458c -lse Global\Launchf9d250ad-37e9-4e5b-8375-46f63c747deb', ErrorCode = '0x80004005'.

Further technical details

EF Core version: 1.1 Operating system: Windows 10 Visual Studio version: 2015-Update 3 (with latest updates)

Other details about my project setup:

project.json File: { “userSecretsId”: “aspnet-ABCTest-6af8ade3-87ff-4468-a9ce-8bb69c696ab8”,

“dependencies”: { “Microsoft.NETCore.App”: { “version”: “1.1.0”, “type”: “platform” }, “Microsoft.EntityFrameworkCore.SqlServer”: “1.1.0”, “Microsoft.EntityFrameworkCore.Tools”: “1.1.0-preview4-final”, “Microsoft.AspNetCore.Mvc”: “1.1.0”, “Microsoft.AspNetCore.Mvc.Core”: “1.1.0”, “Microsoft.AspNetCore.Server.Kestrel”: “1.1.0”, “Microsoft.EntityFrameworkCore.SqlServer.Design”: “1.1.0”, “Microsoft.AspNetCore.Authentication.Cookies”: “1.1.0”, “Microsoft.AspNetCore.Diagnostics”: “1.1.0”, “Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore”: “1.1.0”, “Microsoft.AspNetCore.Identity”: “1.1.0”, “Microsoft.AspNetCore.Identity.EntityFrameworkCore”: “1.1.0”, “Microsoft.AspNetCore.Razor.Tools”: “1.1.0-preview4-final”, “Microsoft.AspNetCore.Server.IISIntegration”: “1.1.0”, “Microsoft.AspNetCore.Server.IISIntegration.Tools”: “1.1.0-preview4-final”, “Microsoft.AspNetCore.StaticFiles”: “1.1.0”, “Microsoft.Extensions.Configuration.EnvironmentVariables”: “1.1.0”, “Microsoft.Extensions.Configuration.Json”: “1.1.0”, “Microsoft.Extensions.Configuration.UserSecrets”: “1.1.0”, “Microsoft.Extensions.Logging”: “1.1.0”, “Microsoft.Extensions.Logging.Console”: “1.1.0”, “Microsoft.Extensions.Logging.Debug”: “1.1.0”, “Microsoft.Extensions.Options.ConfigurationExtensions”: “1.1.0”, “Microsoft.VisualStudio.Web.BrowserLink.Loader”: “14.1.0”, “Microsoft.VisualStudio.Web.CodeGeneration.Tools”: “1.1.0-preview4-final”, “Microsoft.VisualStudio.Web.CodeGenerators.Mvc”: “1.1.0-preview4-final” },

“tools”: { “BundlerMinifier.Core”: “2.0.238” },

“frameworks”: { “netcoreapp1.1”: { “imports”: [ “dotnet5.6”, “portable-net45+win8” ] } },

“buildOptions”: { “emitEntryPoint”: true, “preserveCompilationContext”: true },

“runtimeOptions”: { “configProperties”: { “System.GC.Server”: true } },

“publishOptions”: { “include”: [ “wwwroot”, “Views”, “Areas/**/Views”, “appsettings.json”, “web.config” ] },

“scripts”: { “prepublish”: [ “bower install”, “dotnet bundle” ], “postpublish”: [ “dotnet publish-iis --publish-folder %publish:OutputPath% --framework %publish:FullTargetFramework%” ] } }

[halter73]

I would also try to enable stdout/stderror logging in your web.config. That output should show you what exception is causing the process to crash.

You can probably get the same info by navigating to your project directory in a shell and doing dotnet run.

[jasoncoe2]

I have hit a very similar issue with ASP.net Core 2.0. I had copied my VS project to a new one, and i was getting this error message. After doing some research, I was able to determine that the nlog.config file was not copied into the bin > Debug > net461 folder. Once I did this, I was able to run my application. I found it by running dotnet run from the command line on my project where the csproj files live. I hope it helps any future people with this issue.