From 40f4fc0b364bde02e19e76b152f036babe0c0c76 Mon Sep 17 00:00:00 2001 From: Justin Kotalik Date: Wed, 5 Dec 2018 14:08:14 -0800 Subject: [PATCH] Add more debug information for ANCM. (#9846) Some customer issues that people are commonly running into. --- .../host-and-deploy/iis/troubleshoot.md | 37 ++++++++++++++++++- 1 file changed, 36 insertions(+), 1 deletion(-) diff --git a/aspnetcore/host-and-deploy/iis/troubleshoot.md b/aspnetcore/host-and-deploy/iis/troubleshoot.md index 63cbfc50a2..7520d694e8 100644 --- a/aspnetcore/host-and-deploy/iis/troubleshoot.md +++ b/aspnetcore/host-and-deploy/iis/troubleshoot.md @@ -4,7 +4,7 @@ author: guardrex description: Learn how to diagnose problems with Internet Information Services (IIS) deployments of ASP.NET Core apps. ms.author: riande ms.custom: mvc -ms.date: 11/30/2018 +ms.date: 12/05/2018 uid: host-and-deploy/iis/troubleshoot --- # Troubleshoot ASP.NET Core on IIS @@ -86,6 +86,26 @@ The app starts, but an error prevents the server from fulfilling the request. This error occurs within the app's code during startup or while creating a response. The response may contain no content, or the response may appear as a *500 Internal Server Error* in the browser. The Application Event Log usually states that the app started normally. From the server's perspective, that's correct. The app did start, but it can't generate a valid response. [Run the app at a command prompt](#run-the-app-at-a-command-prompt) on the server or [enable the ASP.NET Core Module stdout log](#aspnet-core-module-stdout-log) to troubleshoot the problem. +### Failed to start application (ErrorCode '0x800700c1') + +``` +EventID: 1010 +Source: IIS AspNetCore Module V2 +Failed to start application '/LM/W3SVC/6/ROOT/', ErrorCode '0x800700c1'. +``` + +The app failed to start because the app's assembly (*.dll*) couldn't be loaded. + +This error occurs when there's a bitness mismatch between the published app and the w3wp/iisexpress process. + +Confirm that the app pool's 32-bit setting is correct: + +1. Select the app pool in IIS Manager's **Application Pools**. +1. Select **Advanced Settings** under **Edit Application Pool** in the **Actions** panel. +1. Set **Enable 32-Bit Applications**: + * If deploying a 32-bit (x86) app, set the value to `True`. + * If deploying a 64-bit (x64) app, set the value to `False`. + ### Connection reset If an error occurs after the headers are sent, it's too late for the server to send a **500 Internal Server Error** when an error occurs. This often happens when an error occurs during the serialization of complex objects for a response. This type of error appears as a *connection reset* error on the client. [Application logging](xref:fundamentals/logging/index) can help troubleshoot these types of errors. @@ -96,6 +116,21 @@ The ASP.NET Core Module is configured with a default *startupTimeLimit* of 120 s ## Troubleshoot app startup errors +### Enable the ASP.NET Core Module debug log + +Add the following handler settings to the app's *web.config* file to enable ASP.NET Core Module debug logs: + +```xml + + + + + + +``` + +Confirm that the path specified for the log exists and that the app pool's identity has write permissions to the location. + ### Application Event Log Access the Application Event Log: