Go to the server where SharePoint Central Admin is hosted, Start -> Run -> Type inetmgr -> Click OK -> Click on Server_Name -> Click Request Filtering under IIS on the Right -> Double click "Request Filtering" -> Click on HTTP Verbs->Click Allow from the top right corner and enter GET and click OK. Following are the steps to apply the same Note: If you require, future web applications not to face this issue, then the settings has to be applied to the IIS level as well. Repeat the same steps to allow other verbs POST, HEAD, CONNECT, PUT, DELETE, TRACE, OPTIONS and Central Administration started to load properly Resolution: Go to the server where SharePoint Central Admin is hosted, Start -> Run -> Type inetmgr -> Click OK -> Expand Server_Name -> Expand Sites -> Click Web Application -> Click Request Filtering under IIS on the Right -> Double click "Request Filtering" -> Click on HTTP Verbs->Click Allow from the top right corner and enter GET and click OK. Problem: SharePoint Central Admin Page diplays HTTP 404 Error after InstallationĬause: HTTP Verbs are not configured to allow in IIS
![sharepoint 2013 http 404 not found sharepoint 2013 http 404 not found](https://www.sharepoint2013hostingnews.com/wp-content/uploads/2012/12/SharePoint-2013-Hosting2.jpg)
I verified the HTTP Verbs in some of the other Farms and added the following HTTP Verbs to be processed in IIS-> Request Filtering settings in my server HTTP Verbs are the one responsible to allow or deny HTTP requests for the Web Server via Request Filtering Again as expected IIS is the culprit and got to know something new this time called "HTTP Verbs". Recently I’ve done some research on custom 404 pages in SharePoint 2010 and found out that all you need to have to create a proper 404 page are a custom HTTP Module, a Publishing Page and a custom Web Part. Having an issue with this all apps I publish after setting up the app catalogue as per the above seem to install, I can browse my App Catalogue and see them but when I click on them I get 404 page not found errors. I turned to the basics of Web sites and IIS, leaving SharePoint concepts and shifted my attention to verify IIS settings. 5 thoughts on Provisioning SharePoint App Catalog in SP 2013/2016 Dave Januat 04:22. Browse other questions tagged c sharepoint http-status-code-404 master-pages or ask. I quickly verified my log files all seems to be fine and cool. SharePoint Foundation 2013 - Master NOT FOUND. I started to wonder what screwed up in the installation which caused Central Admin site to break. If you go into IIS Manager and click on 'Sites' in the right hand pane there will be a column called bindings and a column called ID.
![sharepoint 2013 http 404 not found sharepoint 2013 http 404 not found](https://image.slidesharecdn.com/101-new-features-in-sharepoint-2013-181028203251/95/101-new-features-in-sharepoint-2013-10-638.jpg)
Guess what, it displayed a very simple page with a "HTTP 404 Error". The 404 will appear because you are hitting a different IIS web site and not the one you intended to. Installation went successful oh la la!!! but there are other worries waiting for me when I tried to access SharePoint 2010 Central Administration page. But came across with a new issue in IIS after the installation of first Application Server hosting Central Administration. I have built lot of SharePoint Farms in my project.