I ran the installation of the URL Rewrite overnight. Unfortunately, the server setup feature installation hangs from http redirect.
That's why the notorious error occurs on the web servers: 500.19 Internal Server 0x8007000d
The solution of the problem:
1) Recommendation: Url Rewrite -> web.config-> global.asax
Either one writes the URL rewrite operations directly into the global asax and not the web.config.
2) Installation via the tool Web-deploy, Assist
Reference to the article:
Server Error: HTTP Error 500.19 - Internal Server Error 0x8007000d
If this error appears on a Windows server with IIS Web server, then the URL is not installed in the server roles and features.
Or you have to reinstall the point.
Reason:
The whole rewrite block is not allowed.
This is the IIS server and its installed features
<rewrite> <rules> <!--<rule name="http to https and www" stopProcessing="true"> <match url="(.*)" /> <conditions logicalGrouping="MatchAny"> <add input="{HTTPS}" pattern="off" /> <add input="{HTTP_HOST}" pattern="www\.*" /> </conditions> <action type="Redirect" url="https://microsoft-programmierer.de{URL}" redirectType="Permanent" /> </rule>-->
</rules> </rewrite>
|
In the new IIS Server on Windows 2016, the URL Rewrite does not exist and seems to be installed.
I checked the installed features and roles, and it should be visible.
For comparison, on my Windows 2008 server
Here you can see that URL Rewrite is manageable as a tool. Only then is it allowed. Otherwise, the IIS throws the error while reading the web.Config file at runtime
0x8007000d
Reassemble the URL Rewrite
Just uninstall and reinstall the tool
For me, therefore, the feature hangs on the installation regularly
Module |
IIS Web Core |
Notification |
Unknown |
Handler |
Not yet determined |
Error Code |
0x8007000d |
Config Error |
|
Config File |
\\?\C:\_Daten\_web\CodeDocu_de\web.config |
Requested URL |
http://codedocu.de:80/ |
Physical Path |
|
Logon Method |
Not yet determined |
Logon User |
Not yet determined |
This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what causes this error.