CODEWITHSUNDEEP
asp.netiisweb-applicationsweb-configinternal-server-error
David
David

Reputation: 4047

ASP.NET: HTTP Error 500.19 – Internal Server Error 0x8007000d

I am replicating web application deployment and found several issues related to HTTP Error 500.19. My machine is running Windows 7 while the working development is using Windows 8. We're developing our Web Application using Visual Studio 2010.

First, I got error code 0x80070021, similar as posted here. I update my web.config according to the accepted answer and then I got following error code (which is similar as posted here).

HTTP Error 500.19 - Internal Server Error
Error Code 0x8007000d
Config Source -1: 0:

I have read the symptoms definition in Microsoft support page and cause of the error is:

This problem occurs because the ApplicationHost.config file or the Web.config file contains a malformed XML element.

and the solution is

Delete the malformed XML element from the ApplicationHost.config file or from the Web.config file.

However, the web.config that I used is working perfectly in the original development environment.

Here is what I have checked and tried so far:

  1. Install ASP.NET by calling aspnet_regiis -i
  2. Set my application to use different application pool (ASP.NET v4.0, .NET v4, etc)
  3. ApplicationHost.config file is still using default from Windows 7.

This is part of my Web.Config

<system.webServer>
    <section name="handlers" overrideModeDefault="Allow" /> 
    <section name="modules" allowDefinition="MachineToApplication" overrideModeDefault="Allow" />
    <validation validateIntegratedModeConfiguration="false" />
    <modules runAllManagedModulesForAllRequests="true">
    </modules>
    <handlers>
        <remove name="UrlRoutingHandler" />
        <add name="ReportViewerWebControlHandler" preCondition="integratedMode" verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
    </handlers>
    <urlCompression doStaticCompression="true" doDynamicCompression="false"></urlCompression>
    <directoryBrowse enabled="true" />
    <defaultDocument>
        <files>
            <add value="Logon.aspx" />
        </files>
    </defaultDocument>
</system.webServer>

I have read similar/duplicates/closed posts (around 13) posts in stackoverflow, tried all except the answer related to Ajax (is it related) and still have no clue on what the error is.

Does anyone one how to fix this error? (And if possible, a comprehensive lists of things need to be checked so we can reduce similar posts like this).

Upvotes: 176

Views: 306493

Answers (24)

barbatron
barbatron

Reputation: 133

For me it was having an unsupported configuration element in the config file:

<applicationInitialization doAppInitAfterRestart="true">
  <add initializationPage="/" />
</applicationInitialization>

Upvotes: 5

Sabbir Hassan
Sabbir Hassan

Reputation: 185

I understand that this error can occur because of many different reasons. In my case it was because I uninstalled WSUS service from Server Roles and the whole IIS went down. After doing a bit of research I found that uninstalling WSUS removes a few dlls which are used to do http compression. Since those dlls were missing and the IIS was still looking for them I did a reset using the following command in CMD:

appcmd set config -section:system.webServer/httpCompression /-[name='xpress']

Bingo! The problem is sorted now. Don't forget to run it as an administrator. You might also need to do "iisreset" as well. Just in case.

Upvotes: 1

Ahmadreza Farrokhnejad
Ahmadreza Farrokhnejad

Reputation: 2390

I turned on .NET Framework 3.5 and 4.5 Advance Service in Control Panel -> Programs and Features -> Turn Windows features on or off, and it worked for me.

Upvotes: 2

persi man
persi man

Reputation: 99

First download dotnet-hosting-3.0.0-preview5-19227-01-win (.Net Core 3) or dotnetcore 2 hasting windows

https://download.visualstudio.microsoft.com/download/pr/5bed16f2-fd1a-4027-bee3-3d6a1b5844cc/dd22ca2820fadb57fd5378e1763d27cd/dotnet-hosting-3.1.4-win.exe

Any .NET Core 3.1 application would need this.

Second install it as Administrator

Open cmd as administrator, type iisreset, press enter

So refresh your localhost app

Upvotes: 9

Adrian Carr
Adrian Carr

Reputation: 3133

When trying to set up a .NET Core website I got this error, and tried everything else I could find with no luck, including checking the web.config file, IIS_IUSRS permissions, IIS URL rewrite module, etc. In the end, I installed DotNetCore.1.0.0-WindowsHosting.exe from this page: https://www.microsoft.com/net/download and it started working right away.

Specific link to download: https://go.microsoft.com/fwlink/?LinkId=817246

Upvotes: 48

VivekDev
VivekDev

Reputation: 25349

For .NET Core apps, you can include the needed module by installing the .NET Core Runtime Hosting Bundle. This worked for me.

This screenshot is from when .NET 5 was the current version, but the webpage layout is the same for every version of .NET, if you need help finding the specific link for a given version of .NET:

dotnet hosting installer exe

You can find downloads for other versions of .NET here.

Upvotes: 68

yikekas
yikekas

Reputation: 147

in my case, I have url rewrite rules in web.config, installing the rewrite module solved my problem

Upvotes: 0

Weazy
Weazy

Reputation: 25

In my case helped install the AspNetCoreModuleV2. I installed this from chocolatey

Because I opened my web.config and see using of this module:

<add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModuleV2" resourceType="Unspecified" />

Upvotes: 1

Sergey Kraev
Sergey Kraev

Reputation: 148

For me the problem was a missing CORS module in IIS. Install it from here.

Upvotes: 0

Hesham Yemen
Hesham Yemen

Reputation: 854

Please follow these steps to install and configure .NET 7.0 on Windows:

Go to https://dotnet.microsoft.com/en-us/download/dotnet/7.0

  1. Install Windows Hosting Bundle .
  2. Close IIS and then reopen it.
  3. Click on the server node in IIS.
  4. Go to Modules.
  5. If the installation is correct, you should see "AspNetCoreModuleV2" listed.

Upvotes: 0

marlar
marlar

Reputation: 4136

I had the exact same error. It turned out that it was caused by something completely different, though. It was missing write permissions in a cache folder. But IIS reported error 0x8007000d which is wildly confusing.

Upvotes: 0

Hadiro Tafoua
Hadiro Tafoua

Reputation: 19

follow the procedure chronologically or it might fail due to missing or errors in redirecting.

  1. install Runtime bundle e.g.. dotnet-sdk-7.0....

2.turn asp services on and internet services"Turn Windows features on or off" to enable IIS

3.install web hosting bundle iis 7.0 e.g dotnet-hosting-7.0.2...

this worked for me

Upvotes: -1

brian bentancourt
brian bentancourt

Reputation: 146

In my case, i have installed dotnet hosting but error change to HTTP Error 503. The service is unavailable, but after install windows update KB2999226 and dotnet sdk, its work!

Upvotes: 0

Bodkins
Bodkins

Reputation: 51

For me I had a web.config file in one my root folders, this config file was for the live server so removing it allowed the site to run on the dev server.

So check for any web.config files in folders too.

Upvotes: 0

Agustin Berbegall
Agustin Berbegall

Reputation: 85

Reinstalling ASP.NET Core Runtime - Windows Hosting Bundle Installer made the trick for me... I belive the "ASP.NET Core Module" was missing.

Upvotes: 0

Khalid
Khalid

Reputation: 371

I have the same problem when I was trying to publish asp.net core 5.0 web app on my local IIS and the solution was to add the following inside System.webserver tag in my web.config file

<applicationInitialization doAppInitAfterRestart="true">
  <add initializationPage="/" />
</applicationInitialization>

Upvotes: 0

Ned
Ned

Reputation: 1207

Installing ASP.NET Core Runtime Hosting Bundle solved the issue for me. Source: 500.19 Internal Server Error (0x8007000d)

Upvotes: 10

IAmCoder
IAmCoder

Reputation: 3442

A repair of the DotNetCore hosting bundle did the trick for me. :/

Upvotes: 6

Tomas Kubes
Tomas Kubes

Reputation: 25098

Error 0x8007000d means URL rewriting module (referenced in web.config) is missing or proper version is not installed.

Just install URL rewriting module via web platform installer.

I recommend to check all dependencies from web.config and install them.

Upvotes: 367

Chris Halcrow
Chris Halcrow

Reputation: 31940

Install URL rewriting:

UPDATE - this is now available here (and works with IIS 7-10):

https://www.iis.net/downloads/microsoft/url-rewrite

Ensure you have the following set to 'Allowed' for your IIS server:

enter image description here

Upvotes: 28

aherocalledFrog
aherocalledFrog

Reputation: 861

I had this problem with a brand new web service. Solved it by adding read-only access for Everyone on Properties->Security for the folder that the service was in.

Upvotes: 0

Jeff Moretti
Jeff Moretti

Reputation: 683

For me, it was all about setting up my web server to use the latest-and-greatest tech to support my ASP.NET 5 application!

The following URL gave me all the tips I needed:

https://docs.asp.net/en/1.0.0-rc1/publishing/iis-with-msdeploy.html

Hope this helps :)

Upvotes: -2

max
max

Reputation: 10444

In my case, because I had reinstalled iis, I needed to register iis with dot net 4 using this command:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i

Upvotes: 25

David
David

Reputation: 4047

Problem solved. Here are the steps that I tried:

  • Enable the 32-bit application in IIS -> Application pool -> Advanced settings
  • Copy System.EnterpriseServices.dll and System.EnterpriseServices.Wrapper.dll from C:\Windows\Microsoft.NET\Framework\v2.0.50727 to the application bin folder
  • Do comments/uncomments to sections on the web.config and found that problem related to the referenced DLL.

The config that I commented the previous one that I added:

<section name="handlers" overrideModeDefault="Allow" /> 
<section name="modules" allowDefinition="MachineToApplication" overrideModeDefault="Allow"/>
  • Add the required FasterFlect.DLL used by Combres.DLL v2.1.0.0 to the application bin folder (shall download the full zip from Combres codeplex, because the required fasterflect DLL V2.0.3732.24338 cannot be found in fasterflect codeplex) and other DLLs. For convinience, use the full Combres.DLL (1,3MB)
  • Check that the DLL versions and public key tokens are configured correctly in web.config using tool, e.g. .NET Reflector

Upvotes: 1

Related Questions