SharePoint 2016, Sharepoint 2013, Sharepoint 2010, Windows Server 2012, Sql Server 2012,2014,IIS, Active Directory,User Profile Service, Managed MetaData Service, Search Service, Topology, Web Application, IIS, Site collection, List, Library, PowerShell, office web app, Windows Authentication, NTLM, Kerberos, Saml, ADFS, Active Directory Import, MIM, SharePoint 2016 Central Admin Error: Http 500 The WebSite Cannot display the Page – SharePoint

SharePoint 2016 Central Admin Error: Http 500 The WebSite Cannot display the Page

Today, I stuck in an issue where after a fresh install of the SharePoint Server 2016, I could not get Central Administration website. I get the ” the website cannot display Page” with HTTP error code 500. There is no clue from the Event Log or ULS log. I tried fiddler but no luck. finally, I come to know about a feature in IIS called “Failed Tracing Request”. As soon as I enabled it and read the XML file, I hit the root cause.2016-03-25_23h47_29

To Enable Trace Logging for Failed Requests please check this blog:Enable Trace Logging

Go to the logs file location and click on the XML file.(note: you will get this file once you enable the Failed tracing request and create the rule).2016-03-25_23h50_03

In the file it gave me the following details:

Erro Code: The process cannot access the file because another process has locked a portion of the file. (0x80070021)

ConfigExceptionInfo:\\?\C:\inetpub\wwwroot\wss\VirtualDirectories\39229\web.config ( 817) :This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault=”Deny”), or set explicitly by a location tag with overrideMode=”Deny” or the legacy allowOverride=”false”.

2016-03-25_23h48_58

From the above error, it is not clear which section is locked at the parent level.Now I open the web.config file of central admin and reach to line 817, this line tells me that Module Section is called here. Let’s check the IIS.

 

  • Open the IIS Manager
  • Click on Server in Connection Pane Then Double Click on Configuration Editor Under Management in the Feature Pane.2016-03-25_23h51_09
  • In the Configuration Editor, Click on Section Drop Down and Expand the System.webServer and select Modules.
    2016-03-25_23h51_35
  • Here is the Problem, You can See this Section is Locked(see under the Actions Pane).2016-03-25_23h52_00

Resolution.

To resolve the Issue, Please click on the Unlock Section. You will all set now.

This problem can happen with All the web application if the Module Section is locked.

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *