The key part of this event is that it mentions the namespace http://+:80/ was successfully added. What exactly does this mean? I am not going to go into detail in this blog, but this blog explains why URL reservations are typically used. In our case we first need to list all of the registered URLs via the following command, run from an Administrative command prompt.
netsh http show urlacl
Reserved URL : http://+:80/ User: NT SERVICE\Machine Listen: Yes Delegate: No SDDL: D:(A;;GX;;;S-1-5-21-2127521184-1604012920-1887927527-67210)
Root Cause & Solution
We can see that the URL is reserved. The "+" sign means any host header, and the :80 means anything on port 80. Since there is no application path after the final "/" it reserves anything that runs on port 80. This is what is causing the 503 Service Unavailable errors, as this reservation will prevent W3SVC from obtaining the rights to listen on port 80 when it tries to start the site. Furthermore, applications that run in IIS do not need explicit reservations to run, only non-IIS applications have to reserve a URL namespace if they want to use HTTP to listen for requests. One example are WCF applications that are running on HTTP, as these are non-IIS applications that use HTTP to listen for requests. To resolve the problem for the default web site, we have to remove the reserved namespace for port 80 with the following command.
netsh http delete urlacl http://+:80/
URL reservation successfully deleted
After removing this namespace, WCF applications or other non-IIS applications running on this server may break. So a new URL reservation may be needed for those applications. The new URL reservation should point to the specific application on port 80, not the root. This will prevent the URL reservation from blocking all applications under port 80. The next question is who added the namespace in the first place? There is no real way to identify that, however the HTTPEvent 15007 in the System Event log will give a good indication of the Date and Time the reservation was made.
To summarize, if you are getting a 503 Service Unavailable that looks like the one in this blog post, and you have checked all of the items in the checklist. It is probably time to look at the URL Reservations, and make sure their are not any all inclusive registrations for the port the web site is running on. Meaning http://+:80/, a registration for http://+:80/Application_Name is OK, as it only registers the Application_Name namespace, not the entire port 80 namespace.