.Net Core首次使用遇HTTP Error 502.5 - Process Failure问题求助

Hey there! Let’s work through this 502.5 error together—since you’re new to .NET Core and IIS, I’ll break down targeted fixes that often resolve this exact issue, building on the troubleshooting you’ve already done.

First, a quick recap to align: you’re new to .NET Core, created multiple project templates (including blank) in VS2017, builds succeed, but Edge throws a 502.5 error instead of your expected content. You’ve tried repairing the .NET Core SDK, resetting/restarting IIS, and enabling IIS settings, and regular ASP.NET projects work fine. Great job on the initial steps—let’s dive into .NET Core-specific IIS quirks.

1. Install (or repair) the .NET Core Hosting Bundle #

This is the #1 culprit for 502.5 errors. The .NET Core SDK alone isn’t enough—you need the .NET Core Hosting Bundle, which installs the ASP.NET Core Module (ANCM) that IIS uses to forward requests to your .NET Core app.

• Head to Control Panel > Programs > Programs and Features, and look for "Microsoft .NET Core Hosting Bundle" matching your SDK version (for VS2017, this is likely .NET Core 2.x or 3.x).
• If it’s missing, download the matching bundle version and run the installer. After installing, restart IIS with iisreset in Command Prompt.
• If it’s already installed, try repairing it via Programs and Features > Right-click the bundle > Repair.

2. Set your app pool to use "No Managed Code" #

.NET Core apps don’t rely on the traditional .NET CLR in IIS—using the wrong setting here will break things:

• Open IIS Manager, expand your server, and go to Application Pools.
• Find the app pool tied to your .NET Core project (it should match your project name).
• Right-click > Advanced Settings. Under "General", set ".NET CLR Version" to No Managed Code.
• Save changes and restart the app pool.

3. Enable stdout logging to see the real error #

502.5 is a generic "process failed" message—stdout logging will show you exactly what’s going wrong on app startup:

• Locate your project’s web.config file (VS2017 generates this when publishing; if running from VS, check the output directory or add it manually).
• Find the <aspNetCore> section and update it to enable logging:

  <aspNetCore processPath="dotnet" arguments=".\YourProjectName.dll" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" hostingModel="InProcess" />
  

• Create a logs folder in your app’s root directory if it doesn’t exist.
• Run the app again, then check the stdout files in the logs folder. This will reveal specific issues like missing dependencies, configuration errors, or permission problems.

4. Fix file permissions for the app pool identity #

IIS’s app pool user might not have access to your project’s files:

• Right-click your project’s output folder > Properties > Security tab.
• Click "Edit" > "Add", type IIS AppPool\YourAppPoolName (replace with your actual app pool name), and click Check Names to confirm.
• Grant this user Read & Execute, List folder contents, and Read permissions.
• Apply changes and try running the app again.

5. Switch to InProcess hosting model #

VS2017 .NET Core projects sometimes default to OutOfProcess hosting, which can cause IIS compatibility issues. Try switching to InProcess:

• Open your project’s .csproj file.
• Add or modify the <AspNetCoreHostingModel> element inside the <PropertyGroup>:

  <PropertyGroup>
    <TargetFramework>netcoreapp2.1</TargetFramework> <!-- Match your target framework -->
    <AspNetCoreHostingModel>InProcess</AspNetCoreHostingModel>
  </PropertyGroup>
  

• Rebuild the project and run it again.

Start with the Hosting Bundle check—it’s the most common fix for this error when you’re new to .NET Core and IIS. If the stdout log shows a specific error, feel free to share that detail and we can narrow it down further!

内容的提问来源于stack exchange，提问作者Winthorpe