HTTP 오류 500.19 및 오류 코드 : 0x80070021

HTTP 오류 500.19 및 오류 코드 : 0x80070021

---

Visual Studio 2013에 의한 간단한 webAPI 빌드가 있습니다. VS13에서 실행할 때 잘 작동하지만 로컬 IIS에서 프로젝트를 복사하면 다음 오류가 발생합니다.

HTTP 오류 500.19-내부 서버 오류 페이지의 관련 구성 데이터가 유효하지 않아 요청한 페이지에 액세스 할 수 없습니다.

자세한 오류 정보 :

모듈 IIS 웹 코어

알림 BeginRequest

처리기 가 아직 결정되지 않았습니다

오류 코드 0x80070021

구성 오류이 구성 섹션은이 경로에서 사용할 수 없습니다. 이것은 섹션이 부모 수준에서 잠겨있을 때 발생합니다. 잠금은 기본적으로 (overrideModeDefault = "Deny"), overrideMode = "Deny"또는 레거시 allowOverride = "false"를 사용하여 위치 태그에 의해 명시 적으로 설정됩니다.

구성 파일 \? \ C : \ inetpub \ wwwroot \ APITeslin \ web.config

구성 소스 :

36:   <system.webServer>  
37:     <handlers>  
38:       <remove name="ExtensionlessUrlHandler-Integrated-4.0" />

---

정확히 같은 오류가 발생 하여이 질문에 왔습니다. @SpaceBison 댓글에서 언급 한 바와 같이,이 대답은 솔루션에 대해 설명 - https://stackoverflow.com/a/12867753/404099 . 나는 너무 늦게 발견했고 몇 단계를 놓쳤다. 이것이 나를 위해 일한 것입니다.

Windows Server 2012, IIS 8.5 . 다른 버전에서도 작동합니다.

• 서버 관리자로 이동하여 역할 및 기능 추가를 클릭하십시오.
• 역할 섹션에서 다음을 선택하십시오. 웹 서버
  • 보안 하위 섹션에서 모든 항목을 선택합니다 (다이제스트, IP 제한 및 URL 인증은 사용하지 않았으므로 제외)
  • 응용 프로그램 개발에서 .NET Extensibility 4.5, ASP.NET 4.5 및 두 ISAPI 항목을 선택하십시오.
• 기능 섹션에서 NET 3.5, .NET 4.5, ASP.NET 4.5를 선택하십시오.
• 웹 서버 섹션에서 웹 서버 (모두), 관리 도구 (IIS 관리 콘솔 및 관리 서비스), Windows 인증 (이 중 하나를 사용하는 경우)을 선택하십시오.

---

빈 ASP.NET 응용 프로그램에서 WCF 서비스를 호스팅하려고 할 때이 오류가 발생했습니다. 전체 솔루션은 Windows 8.1에서 실행되는 IIS 8.5에서 .NET 4.5 플랫폼을 사용하고있었습니다. 문제는

1. "Windows 기능 켜기 또는 끄기"를 엽니 다.
2. ASP.NET 4.5 고급 서비스에서 WCF 섹션으로 이동
3. HTTP 활성화를 확인하십시오.

4. 시스템을 다시 시작하라는 메시지가 표시됩니다.

   

HTTP 500.19를 수정해야합니다!

11-FEB-2016 편집 Windows 10 Pro, IIS 10에서 문제가 발생했습니다. 이번에는 HTTP 404.0이었습니다. 수정 사항은 여전히 ​​동일합니다. Windows 기능-> .NET Framework 4.6 고급 서비스-> WCF 서비스-> HTTP 활성화에서 "HTTP 활성화"를 켜십시오.

---

나도 같은 문제를 겪었지만 IIS와 Google로 여러 시간 동안 뇌우를 겪은 후. 해결책을 찾았습니다. 이 오류는 IIS에서 일부 설정이 비활성화되어 있기 때문 applicationHost.config입니다.

해결해야 할 단계는 다음과 같습니다.

1. 이동 C:\Windows\System32\inetsrv\config\applicationHost.config및 메모장에서 열려

2. 존재하는 다음 키 값을 변경하십시오.

   • <section name="handlers" overrideModeDefault="Deny" /> 이 값을 "거부"에서 "허용"으로 변경

   • <section name="modules" allowDefinition="MachineToApplication" overrideModeDefault="Deny" /> 이 값을 "거부"에서 "허용"으로 변경

그것은 나를 위해 일했다.

---

해당 컴퓨터에서 IIS를 처음 실행하는 경우 ASP.NET IIS 등록 도구 (aspnet_regiis.exe)를 실행해야합니다.

Here's how to do that: If you're using .net framework v4, open command prompt as an administrator, and change directory to your .net framework base folder using:

CD C:\Windows\Microsoft.NET\Framework\v4.0.30319

or, if you're using a 64 bit computer, use:

CD C:\Windows\Microsoft.NET\Framework64\v4.0.30319

when you've successfully navigated to the appropriate directory, execute the ASP.NET IIS registration tool using:

aspnet_regiis -i

If you're using a different .NET framework version, simply replace v4.0.30319 with the appropriate folder name.

Hope this helps.

---

I solved this by doing the following:

WebServer(ISS)->WebServer->Application Development
add .NET Extensibility 3.5
add .NET Extensibility 4.5
add ASP.NET 4.5
add ISAPI Extensions
add ISAPI Filters

---

On Windows 8.1, IIS 8.5 the solution for me was to register 4.5 from the control panel:

Programs and Features > Turn Windows features on or off > Information Information Services > World Wide Web Services > Application Development Features > Select ASP.NET 4.5

Click OK.

---

As the error idnicates - "This happens when the section is locked at a parent level". To unlock the section you can use appcmd.exe and execute the following command:

%windir%\system32\inetsrv\appcmd.exe unlock config -section:system.webServer/handlers -commitpath:apphost

For more information on about section locking and what a parent configuration context is refer to IIS documentation.

---

In my case, there were rules for IIS URL Rewrite module but I didn't have that module installed. You should check your web.config if there are any modules included but not installed.

---

In our case, we struggled with this error for quite some days. It turns out that in control panel, programs, turn windows features on or off.

We selected Internet Information Services, world wide web services, Application development features and there we check the set of features associated with our development environment. For example: ASP.NET 4.6. .NET Extensibility 4.6, etc.

It works!

---

Try unlocking the relevant IIS (7.5) configuration settings at server level, as follows:

1. Open IIS Manager
2. Select the server in the Connections pane
3. Open Configuration Editor in the main pane
4. In the Sections drop down, select the section to unlock, e.g. system.webServer > defaultPath
5. Click Unlock Attribute in the right pane
6. Repeat for any other settings which you need to unlock
7. Restart IIS (optional) - Select the server in the Conncetions pane, click Restart in the Actions pane

---

Your web.config describes that you're using forms authentication - make sure you enable forms authentication and disable anonymous authentication in IIS under the Authentication menu, for the website that is running in IIS.

---

Please <staticContent /> line and erased it from the web.config.

---

Well, we're using Amazon Web Services and so we are looking to use scripts and programs to get through this problem. So I have been on the hunt for a command line tool. So first I tried the trick of running

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

but because I'm running a cloud based Windows Server 2012 it complained

This option is not supported on this version of the operating system. Administrators should instead install/uninstall ASP.NET 4.5 with IIS8 using the "Turn Windows Features On/Off" dialog, the Server Manager management tool, or the dism.exe command line tool. For more details please see http://go.microsoft.com/fwlink/?LinkID=216771.

and I Googled and found the official Microsoft Support Page KB2736284. So there is a command line tool dism.exe. So I tried the following

dism /online /enable-feature /featurename:IIS-ASPNET45

but it complained and gave a list of featurenames to try, so I tried them one by one and I tested my WebAPI webpage after each and it worked after the bottom one in the list.

dism /online /enable-feature /featurename:IIS-ApplicationDevelopment
dism /online /enable-feature /featurename:IIS-ISAPIFilter 
dism /online /enable-feature /featurename:IIS-ISAPIExtensions 
dism /online /enable-feature /featurename:IIS-NetFxExtensibility45 

And so now I can browse to my WebAPI site and see the API information. That should help a few people. [However, I am not out of the woods totally myself yet and I cannot reach the website from outside the box. Still working on it.]

Also, I did some earlier steps following other people responses. I can confirm that the following Feature Delegation needs to be change (though I'd like to find a command line tool for these).

In Feature delegation

Change 
'Handler Mappings' from Read Only to Read/Write

Change 
'Modules' from Read Only to Read/Write

Change 
'SSL Settings' from Read Only to Read/Write

---

For .NET Core apps on Windows Server (in my case 2012 with IIS 10) it worked after install .NET Core Windows Server Hosting bundle (link).

---

Check if IIS server installed the URL rewrite feature.
If it is not installed then make sure your web.config file don't have the URL rewrite related configuration

<!-- Make sure don't have below config, if server have not installed url rewrite feature. -->
<rewrite>
  <rules>
    <rule name="Fail bad requests">
      <match url=".*"/> ...

Some time we copied the config from legacy server and straight away deploy to brand new server, then we may encounter such kind of 500 issue.

---

It works and save my time. Try it HTTP Error 500.19 – Internal Server Error – 0x80070021 (IIS 8.5)

---

I fixed with removed anonymousAuthentication.
Just comment in your web config IIS

<security>          
    <!--
    <authentication>
        <anonymousAuthentication userName=""/>
    </authentication>
    -->
</security> 

---

The solution that worked for me was to delete my current Web.config and add a new one. That solved the problem for me

참고URL : https://stackoverflow.com/questions/20048486/http-error-500-19-and-error-code-0x80070021