New answers tagged iis
You don't necessarily need to stop it unless you want SharePoint not to treat it like a WFE. It is that service (Microsoft SharePoint Foundation Web Application service) being enabled on the APP server that is causing SharePoint to propagate your new web application settings to IIS on the APP server though.
Actually its not related to SharePoint, its a general concept for IIS. When you reset IIS, all the cache and in-memory storage is gone (cleared).. When you first access the page, it builds the cache again which generally takes more time than the second attempt, which actually generates many items from Cache.. A concept called Warm-up Scripts are usually run ...
That happened to me too. The thing was that I already made a web application with the port number 9000. So you have to choose "Advanced settings" and set "Internal communication port range" to a new range. (For example: 8000). That solved my problem.
Top 50 recent answers are included